Author Topic: Cannot forward port  (Read 12236 times)

0 Members and 1 Guest are viewing this topic.

cracky bigdoo

  • Guest
Cannot forward port
« on: August 14, 2009, 06:07:49 PM »
Hi,

It seems that I'm having trouble forwarding my port for uTorrent. I'm completely new to this and have no clue at what I'm doing. Here is the error message:


Router: D-Link - WBR-1310 (D-Link v2 Firmware)
Loading Commands...
Number Of Port Forwards To Send To Router (1)
Running Commands...

(Current -  1/1)
Adding uTorrent (TCP/UDP) For Ports 35506-35506 To 192.168.0.136()

Running Script From Database For Selected Router
-----------------------------------------------------------------------
Step 01. nav_first_only("")

!ERROR! (Navigating to http://192.168.0.1/)
This Entry Will be Skipped.
Please Check your Router Info And Try Again.
-----------------------------------------------------------------------
Access Denied(-2147024891) (http://admin:@192.168.0.1/)
-----------------------------------------------------------------------

Finished Adding uTorrent


-------------------DONE! (All Commands Finished)-------------------



I'm also having WMI issues, here is the report:

20934 21:08:01 (0) ** WMIDiag v2.0 started on Friday, August 14, 2009 at 21:04.
20935 21:08:01 (0) **
20936 21:08:01 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
20937 21:08:01 (0) **
20938 21:08:01 (0) ** This script is not supported under any Microsoft standard support program or service.
20939 21:08:01 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
20940 21:08:01 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
20941 21:08:01 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
20942 21:08:01 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
20943 21:08:01 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
20944 21:08:01 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
20945 21:08:01 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
20946 21:08:01 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
20947 21:08:01 (0) ** of the possibility of such damages.
20948 21:08:01 (0) **
20949 21:08:01 (0) **
20950 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20951 21:08:01 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
20952 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20953 21:08:01 (0) **
20954 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20955 21:08:01 (0) ** Windows XP - Service pack 2 - 32-bit (2600) - User 'HOME-A91A01EB81\MR. BIGGLESWORTH' on computer 'HOME-A91A01EB81'.
20956 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20957 21:08:01 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
20958 21:08:01 (0) ** INFO: => 3 incorrect shutdown(s) detected on:
20959 21:08:01 (0) **          - Shutdown on 10 August 2009 13:41:51 (GMT+4).
20960 21:08:01 (0) **          - Shutdown on 13 August 2009 18:46:02 (GMT+4).
20961 21:08:01 (0) **          - Shutdown on 14 August 2009 13:05:14 (GMT+4).
20962 21:08:01 (0) **
20963 21:08:01 (0) ** System drive: ... C: (Disk #0 Partition #0).
20964 21:08:01 (0) ** Drive type: ... IDE (HDT722525DLA380).
20965 21:08:01 (0) ** There are no missing WMI system files: .............................................................................. OK.
20966 21:08:01 (0) ** There are no missing WMI repository files: .......................................................................... OK.
20967 21:08:01 (0) ** WMI repository state: ............................................................................................... NOT TESTED.
20968 21:08:01 (0) ** BEFORE running WMIDiag:
20969 21:08:01 (0) ** The WMI repository has a size of: ................................................................................... 21 MB.
20970 21:08:01 (0) ** - Disk free space on 'C:': .......................................................................................... 110475 MB.
20971 21:08:01 (0) **   - INDEX.BTR,                     1572864 bytes,      8/14/2009 8:53:32 PM
20972 21:08:01 (0) **   - INDEX.MAP,                     804 bytes,          8/14/2009 9:02:00 PM
20973 21:08:01 (0) **   - MAPPING.VER,                   4 bytes,            8/14/2009 9:02:00 PM
20974 21:08:01 (0) **   - MAPPING1.MAP,                  10552 bytes,        8/14/2009 9:02:00 PM
20975 21:08:01 (0) **   - MAPPING2.MAP,                  10552 bytes,        8/14/2009 8:55:33 PM
20976 21:08:01 (0) **   - OBJECTS.DATA,                  19898368 bytes,     8/14/2009 8:53:32 PM
20977 21:08:01 (0) **   - OBJECTS.MAP,                   9760 bytes,         8/14/2009 9:02:00 PM
20978 21:08:01 (0) ** AFTER running WMIDiag:
20979 21:08:01 (0) ** The WMI repository has a size of: ................................................................................... 21 MB.
20980 21:08:01 (0) ** - Disk free space on 'C:': .......................................................................................... 110465 MB.
20981 21:08:01 (0) **   - INDEX.BTR,                     1572864 bytes,      8/14/2009 8:53:32 PM
20982 21:08:01 (0) **   - INDEX.MAP,                     804 bytes,          8/14/2009 9:02:00 PM
20983 21:08:01 (0) **   - MAPPING.VER,                   4 bytes,            8/14/2009 9:02:00 PM
20984 21:08:01 (0) **   - MAPPING1.MAP,                  10552 bytes,        8/14/2009 9:02:00 PM
20985 21:08:01 (0) **   - MAPPING2.MAP,                  10552 bytes,        8/14/2009 8:55:33 PM
20986 21:08:01 (0) **   - OBJECTS.DATA,                  19898368 bytes,     8/14/2009 8:53:32 PM
20987 21:08:01 (0) **   - OBJECTS.MAP,                   9760 bytes,         8/14/2009 9:02:00 PM
20988 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20989 21:08:01 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
20990 21:08:01 (0) ** Windows Firewall Profile: ........................................................................................... STANDARD.
20991 21:08:01 (0) ** Windows Firewall 'RemoteAdmin' status: .............................................................................. DISABLED.
20992 21:08:01 (0) ** => This will prevent any WMI remote connectivity to this machine.
20993 21:08:01 (0) **    - You can adjust the configuration by executing the following command:
20994 21:08:01 (0) **    i.e. 'NETSH.EXE FIREWALL SET SERVICE REMOTEADMIN ENABLE SUBNET'
20995 21:08:01 (0) **
20996 21:08:01 (0) ** Windows Firewall application exception for 'UNSECAPP.EXE': .......................................................... MISSING.
20997 21:08:01 (0) ** => This will prevent any script and MMC application asynchronous callbacks to this machine.
20998 21:08:01 (0) **    - You can adjust the configuration by executing the following command:
20999 21:08:01 (0) **    i.e. 'NETSH.EXE FIREWALL SET ALLOWEDPROGRAM C:\WINDOWS\SYSTEM32\WBEM\UNSECAPP.EXE WMICALLBACKS ENABLE'
21000 21:08:01 (0) **
21001 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21002 21:08:01 (0) ** DCOM Status: ... OK.
21003 21:08:01 (0) ** WMI registry setup: ................................................................................................. OK.
21004 21:08:01 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
21005 21:08:01 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
21006 21:08:01 (0) ** - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Automatic')
21007 21:08:01 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
21008 21:08:01 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
21009 21:08:01 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
21010 21:08:01 (0) **          this can prevent the service/application to work as expected.
21011 21:08:01 (0) **
21012 21:08:01 (0) ** RPCSS service: ... OK (Already started).
21013 21:08:01 (0) ** WINMGMT service: ... OK (Already started).
21014 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21015 21:08:01 (0) ** WMI service DCOM setup: ............................................................................................. OK.
21016 21:08:01 (0) ** WMI components DCOM registrations: .................................................................................. OK.
21017 21:08:01 (0) ** WMI ProgID registrations: ........................................................................................... OK.
21018 21:08:01 (2) !! WARNING: WMI provider DCOM registrations missing for the following provider(s): ..................................... 1 WARNING(S)!
21019 21:08:01 (0) ** - ROOT/NAP, NAP_ClientProvider ({C330DE32-29C7-4CF2-9807-74BCB5486A37}) (i.e. WMI Class 'NAP_SystemHealthAgent')
21020 21:08:01 (0) **   Provider DLL: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
21021 21:08:01 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
21022 21:08:01 (0) **    while the DCOM registration is wrong or missing. This can be due to:
21023 21:08:01 (0) **    - a de-installation of the software.
21024 21:08:01 (0) **    - a deletion of some registry key data.
21025 21:08:01 (0) **    - a registry corruption.
21026 21:08:01 (0) ** => You can correct the DCOM configuration by:
21027 21:08:01 (0) **    - Executing the 'REGSVR32.EXE <Provider.DLL>' command.
21028 21:08:01 (0) **    Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
21029 21:08:01 (0) **          (This list can be built on a similar and working WMI Windows installation)
21030 21:08:01 (0) **          The following command line must be used:
21031 21:08:01 (0) **          i.e. 'WMIDiag CorrelateClassAndProvider'
21032 21:08:01 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
21033 21:08:01 (0) **          may not solve the problem as the DLL supporting the WMI class(es)
21034 21:08:01 (0) **          can be located in a different folder.
21035 21:08:01 (0) **          You must refer to the class name to determine the software delivering the related DLL.
21036 21:08:01 (0) ** => If the software has been de-installed intentionally, then this information must be
21037 21:08:01 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
21038 21:08:01 (0) **    the provider registration data.
21039 21:08:01 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\NAP path __Win32Provider Where Name='NAP_ClientProvider' DELETE'
21040 21:08:01 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,
21041 21:08:01 (0) **    the namespace and ALL its content can be ENTIRELY deleted.
21042 21:08:01 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='NAP' DELETE'
21043 21:08:01 (0) **    - Re-installing the software.
21044 21:08:01 (0) **
21045 21:08:01 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
21046 21:08:01 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
21047 21:08:01 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
21048 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21049 21:08:01 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
21050 21:08:01 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
21051 21:08:01 (0) **        - REMOVED ACE:
21052 21:08:01 (0) **          ACEType:  &h0
21053 21:08:01 (0) **                    ACCESS_ALLOWED_ACE_TYPE
21054 21:08:01 (0) **          ACEFlags: &h0
21055 21:08:01 (0) **          ACEMask:  &h1F
21056 21:08:01 (0) **                    DCOM_RIGHT_EXECUTE
21057 21:08:01 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
21058 21:08:01 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
21059 21:08:01 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
21060 21:08:01 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
21061 21:08:01 (0) **
21062 21:08:01 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
21063 21:08:01 (0) **    Removing default security will cause some operations to fail!
21064 21:08:01 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
21065 21:08:01 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
21066 21:08:01 (0) **
21067 21:08:01 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
21068 21:08:01 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
21069 21:08:01 (0) **        - REMOVED ACE:
21070 21:08:01 (0) **          ACEType:  &h0
21071 21:08:01 (0) **                    ACCESS_ALLOWED_ACE_TYPE
21072 21:08:01 (0) **          ACEFlags: &h0
21073 21:08:01 (0) **          ACEMask:  &hB
21074 21:08:01 (0) **                    DCOM_RIGHT_EXECUTE
21075 21:08:01 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
21076 21:08:01 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
21077 21:08:01 (0) **
21078 21:08:01 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
21079 21:08:01 (0) **    Removing default security will cause some operations to fail!
21080 21:08:01 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
21081 21:08:01 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
21082 21:08:01 (0) **
21083 21:08:01 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
21084 21:08:01 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
21085 21:08:01 (0) **        - REMOVED ACE:
21086 21:08:01 (0) **          ACEType:  &h0
21087 21:08:01 (0) **                    ACCESS_ALLOWED_ACE_TYPE
21088 21:08:01 (0) **          ACEFlags: &h0
21089 21:08:01 (0) **          ACEMask:  &hB
21090 21:08:01 (0) **                    DCOM_RIGHT_EXECUTE
21091 21:08:01 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
21092 21:08:01 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
21093 21:08:01 (0) **
21094 21:08:01 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
21095 21:08:01 (0) **    Removing default security will cause some operations to fail!
21096 21:08:01 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
21097 21:08:01 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
21098 21:08:01 (0) **
21099 21:08:01 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
21100 21:08:01 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
21101 21:08:01 (0) **        - ACTUAL ACE:
21102 21:08:01 (0) **          ACEType:  &h0
21103 21:08:01 (0) **                    ACCESS_ALLOWED_ACE_TYPE
21104 21:08:01 (0) **          ACEFlags: &h2
21105 21:08:01 (0) **                    CONTAINER_INHERIT_ACE
21106 21:08:01 (0) **          ACEMask:  &h1
21107 21:08:01 (0) **                    WBEM_ENABLE
21108 21:08:01 (0) **        - EXPECTED ACE:
21109 21:08:01 (0) **          ACEType:  &h0
21110 21:08:01 (0) **                    ACCESS_ALLOWED_ACE_TYPE
21111 21:08:01 (0) **          ACEFlags: &h12
21112 21:08:01 (0) **                    CONTAINER_INHERIT_ACE
21113 21:08:01 (0) **                    INHERITED_ACE
21114 21:08:01 (0) **          ACEMask:  &h13
21115 21:08:01 (0) **                    WBEM_ENABLE
21116 21:08:01 (0) **                    WBEM_METHOD_EXECUTE
21117 21:08:01 (0) **                    WBEM_WRITE_PROVIDER
21118 21:08:01 (0) **
21119 21:08:01 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
21120 21:08:01 (0) **    This will cause some operations to fail!
21121 21:08:01 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
21122 21:08:01 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
21123 21:08:01 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
21124 21:08:01 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
21125 21:08:01 (0) **       A specific WMI application can always require a security setup different
21126 21:08:01 (0) **       than the WMI security defaults.
21127 21:08:01 (0) **
21128 21:08:01 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
21129 21:08:01 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
21130 21:08:01 (0) **        - ACTUAL ACE:
21131 21:08:01 (0) **          ACEType:  &h0
21132 21:08:01 (0) **                    ACCESS_ALLOWED_ACE_TYPE
21133 21:08:01 (0) **          ACEFlags: &h2
21134 21:08:01 (0) **                    CONTAINER_INHERIT_ACE
21135 21:08:01 (0) **          ACEMask:  &h1
21136 21:08:01 (0) **                    WBEM_ENABLE
21137 21:08:01 (0) **        - EXPECTED ACE:
21138 21:08:01 (0) **          ACEType:  &h0
21139 21:08:01 (0) **                    ACCESS_ALLOWED_ACE_TYPE
21140 21:08:01 (0) **          ACEFlags: &h12
21141 21:08:01 (0) **                    CONTAINER_INHERIT_ACE
21142 21:08:01 (0) **                    INHERITED_ACE
21143 21:08:01 (0) **          ACEMask:  &h13
21144 21:08:01 (0) **                    WBEM_ENABLE
21145 21:08:01 (0) **                    WBEM_METHOD_EXECUTE
21146 21:08:01 (0) **                    WBEM_WRITE_PROVIDER
21147 21:08:01 (0) **
21148 21:08:01 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
21149 21:08:01 (0) **    This will cause some operations to fail!
21150 21:08:01 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
21151 21:08:01 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
21152 21:08:01 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
21153 21:08:01 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
21154 21:08:01 (0) **       A specific WMI application can always require a security setup different
21155 21:08:01 (0) **       than the WMI security defaults.
21156 21:08:01 (0) **
21157 21:08:01 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
21158 21:08:01 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
21159 21:08:01 (0) **        - REMOVED ACE:
21160 21:08:01 (0) **          ACEType:  &h0
21161 21:08:01 (0) **                    ACCESS_ALLOWED_ACE_TYPE
21162 21:08:01 (0) **          ACEFlags: &h12
21163 21:08:01 (0) **                    CONTAINER_INHERIT_ACE
21164 21:08:01 (0) **                    INHERITED_ACE
21165 21:08:01 (0) **          ACEMask:  &h13
21166 21:08:01 (0) **                    WBEM_ENABLE
21167 21:08:01 (0) **                    WBEM_METHOD_EXECUTE
21168 21:08:01 (0) **                    WBEM_WRITE_PROVIDER
21169 21:08:01 (0) **
21170 21:08:01 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
21171 21:08:01 (0) **    Removing default security will cause some operations to fail!
21172 21:08:01 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
21173 21:08:01 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
21174 21:08:01 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
21175 21:08:01 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
21176 21:08:01 (0) **       A specific WMI application can always require a security setup different
21177 21:08:01 (0) **       than the WMI security defaults.
21178 21:08:01 (0) **
21179 21:08:01 (0) **
21180 21:08:01 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
21181 21:08:01 (0) ** DCOM security error(s) detected: .................................................................................... 3.
21182 21:08:01 (0) ** WMI security warning(s) detected: ................................................................................... 0.
21183 21:08:01 (0) ** WMI security error(s) detected: ..................................................................................... 3.
21184 21:08:01 (0) **
21185 21:08:01 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
21186 21:08:01 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
21187 21:08:01 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
21188 21:08:01 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
21189 21:08:01 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
21190 21:08:01 (0) **   'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
21191 21:08:01 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
21192 21:08:01 (0) **   'select * from MSFT_SCMEventLogEvent'
21193 21:08:01 (0) **
21194 21:08:01 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
21195 21:08:01 (0) ** WMI ADAP status: ... OK.
21196 21:08:01 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
21197 21:08:01 (0) ** - ROOT/SERVICEMODEL.
21198 21:08:01 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
21199 21:08:01 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
21200 21:08:01 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
21201 21:08:01 (0) **    i.e. 'WMIC.EXE /NODE:"HOME-A91A01EB81" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
21202 21:08:01 (0) **
21203 21:08:01 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
21204 21:08:01 (0) ** WMI CONNECTIONS: ... OK.
21205 21:08:01 (0) ** WMI GET operations: ................................................................................................. OK.
21206 21:08:01 (0) ** WMI MOF representations: ............................................................................................ OK.
21207 21:08:01 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
21208 21:08:01 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
21209 21:08:01 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
21210 21:08:01 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
21211 21:08:01 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
21212 21:08:01 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
21213 21:08:01 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
21214 21:08:01 (0) ** WMI static instances retrieved: ..................................................................................... 731.
21215 21:08:01 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
21216 21:08:01 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
21217 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21218 21:08:01 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
21219 21:08:01 (0) **   DCOM: ... 14.
21220 21:08:01 (0) **   WINMGMT: ... 0.
21221 21:08:01 (0) **   WMIADAPTER: ... 0.
21222 21:08:01 (0) ** => Verify the WMIDiag LOG at line #20486 for more details.
21223 21:08:01 (0) **
21224 21:08:01 (0) ** # of additional Event Log events AFTER WMIDiag execution:
21225 21:08:01 (0) **   DCOM: ... 0.
21226 21:08:01 (0) **   WINMGMT: ... 0.
21227 21:08:01 (0) **   WMIADAPTER: ... 0.
21228 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21229 21:08:01 (0) ** WMI Registry key setup: ............................................................................................. OK.
21230 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21231 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21232 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21233 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21234 21:08:01 (0) **
21235 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21236 21:08:01 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
21237 21:08:01 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
21238 21:08:01 (0) **
21239 21:08:01 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\MR. BIGGLESWORTH\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.SP2.32_HOME-A91A01EB81_2009.08.14_21.04.51.LOG' for details.
21240 21:08:01 (0) **
21241 21:08:01 (0) ** WMIDiag v2.0 ended on Friday, August 14, 2009 at 21:08 (W:69 E:16 S:1).




Thanks for your time, I really appreciate it.
« Last Edit: August 14, 2009, 06:09:46 PM by cracky bigdoo »

PcWinTech.com Forums

Cannot forward port
« on: August 14, 2009, 06:07:49 PM »

Offline Shane

  • Top Geek, err uh Dog.
  • PcWinTech Administrator
  • PcWinTech Guru
  • *******
  • Join Date: Jul 2008
  • Posts: 16,846
  • Location: USA
  • Karma: 523
  • "Knowledge should be shared not hidden."
Re: Cannot forward port
« Reply #1 on: August 14, 2009, 07:56:31 PM »
alright lets get started :-)

first the script is failing because you got this error Access Denied(-2147024891) (http://admin:@192.168.0.1/)
Which means it doesn't like your username and password for the router. Remove the username and password from the program, then turn off silent mode under the advanced menu. This will make the program ask for the log in info when you try to update the router.

On your WMI looking at the log it shows you are on still service pack 2 for XP, I strongly recommend getting service pack 3 installed :-)

Shane
(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

cracky bigdoo

  • Guest
Re: Cannot forward port
« Reply #2 on: August 14, 2009, 08:42:12 PM »
Hi Shane,

I did what you said and this log was produced - what do we do from here?

Router: D-Link - WBR-1310 (D-Link v2 Firmware)
Loading Commands...
Number Of Port Forwards To Send To Router (1)
Running Commands...

(Current -  1/1)
Adding uTorrent (TCP/UDP) For Ports 35506-35506 To 192.168.0.136()

Running Script From Database For Selected Router
-----------------------------------------------------------------------
Step 01. nav_first_only("")
(Successful) (http://192.168.0.1/)
Step 02. set_username("login_name")
(Failed - Object Not Found)
Step 03. set_password("login_pass")
(Failed - Object Not Found)
Step 04. click_button_first_only("Login")
(Failed - Object Not Found)
Step 05. nav_first_only("adv_portforward.htm")
(Successful) (http://192.168.0.1/adv_portforward.htm)
Step 06. check_if_name_exists("")
Step 07. set_name_array("1|2|3|4|5|6|7|8|9|10")
(Successful)
Step 08. set_name_to_check("name,0")
(Successful) (Current Name From Name Array name2)
Step 09. set_checkbox("enable,0")
(Successful)
Step 10. set_name("name,0")
(Successful)
Step 11. set_ip("ip,0")
(Successful)
Step 12. set_start_port("public_port,0")
(Successful)
Step 13. set_stop_port("private_port,0")
(Successful)
Step 14. set_type_choices("TCP|UDP|Any")
Step 15. set_combobox("protocol,0")
(Successful)
Step 16. click_button_last_only("Save Settings")
(Successful)
-----------------------------------------------------------------------

Finished Adding uTorrent


-------------------DONE! (All Commands Finished)-------------------
thanks
« Last Edit: August 14, 2009, 08:45:05 PM by cracky bigdoo »

Offline Shane

  • Top Geek, err uh Dog.
  • PcWinTech Administrator
  • PcWinTech Guru
  • *******
  • Join Date: Jul 2008
  • Posts: 16,846
  • Location: USA
  • Karma: 523
  • "Knowledge should be shared not hidden."
Re: Cannot forward port
« Reply #3 on: August 14, 2009, 08:44:32 PM »
The script shows it should have worked, did you see the page update?

Shane
(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

cracky bigdoo

  • Guest
Re: Cannot forward port
« Reply #4 on: August 14, 2009, 08:47:50 PM »
Hello again,

It says 35506 is offline and cannot be reached. What to do now?

Offline Shane

  • Top Geek, err uh Dog.
  • PcWinTech Administrator
  • PcWinTech Guru
  • *******
  • Join Date: Jul 2008
  • Posts: 16,846
  • Location: USA
  • Karma: 523
  • "Knowledge should be shared not hidden."
Re: Cannot forward port
« Reply #5 on: August 14, 2009, 09:07:00 PM »
Make sure to give this a good read
http://www.pcwintech.com/common-problems-fixes-port-forwarding

When ever I help people and find fixes for their port forwarding problems I update that page.

Let me know how it goes.

Shane
(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com

cracky bigdoo

  • Guest
Re: Cannot forward port
« Reply #6 on: August 16, 2009, 09:39:52 PM »
Hi Shane,

Everything is fine. The port was forwarded after all, I just needed to reset the router! It's great to have blazing fast torrents again (somehow the port became unforwarded). I'm averaging over 400 kb/s once again. Thank you for your nifty product and your time. Best wishes.
« Last Edit: August 16, 2009, 10:00:44 PM by cracky bigdoo »

PcWinTech.com Forums

Re: Cannot forward port
« Reply #6 on: August 16, 2009, 09:39:52 PM »