Strict Standards: Non-static method Settings::setHostName() should not be called statically in C:\website\www.networksteve.com\windows\_lib\AutoConfig.php on line 20

Strict Standards: Non-static method Settings::addHostAlias() should not be called statically in C:\website\www.networksteve.com\windows\_lib\AutoConfig.php on line 22

Strict Standards: Non-static method Settings::setSiteRoot() should not be called statically in C:\website\www.networksteve.com\windows\_lib\AutoConfig.php on line 28

Strict Standards: Non-static method Settings::setDsn() should not be called statically in C:\website\www.networksteve.com\windows\_site\Config.php on line 16

Strict Standards: Non-static method Settings::setTitle() should not be called statically in C:\website\www.networksteve.com\windows\_site\Config.php on line 19

Strict Standards: Non-static method Settings::setDescription() should not be called statically in C:\website\www.networksteve.com\windows\_site\Config.php on line 20

Strict Standards: Non-static method Settings::setSiteRoot() should not be called statically in C:\website\www.networksteve.com\windows\_site\Config.php on line 24

Strict Standards: Non-static method Settings::setShowDeleted() should not be called statically in C:\website\www.networksteve.com\windows\_site\Config.php on line 31

Strict Standards: Non-static method Settings::setRecentTopicsDuration() should not be called statically in C:\website\www.networksteve.com\windows\_site\Config.php on line 36

Strict Standards: Non-static method Settings::test() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Init.php on line 28

Strict Standards: Non-static method Skin::test() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Init.php on line 29

Strict Standards: Non-static method Settings::getSkin() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Skin.php on line 102

Strict Standards: Non-static method Settings::getSiteRoot() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Init.php on line 32

Strict Standards: Non-static method Settings::getDsn() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Init.php on line 35

Strict Standards: Non-static method Form::field() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Init.php on line 39

Strict Standards: Non-static method Form::fieldExists() should not be called statically, assuming $this from incompatible context in C:\website\www.networksteve.com\windows\_lib\Entity\User.php on line 92

Strict Standards: Non-static method Form::fieldExists() should not be called statically in C:\website\www.networksteve.com\windows\topic.php on line 15

Strict Standards: Non-static method Form::field() should not be called statically in C:\website\www.networksteve.com\windows\topic.php on line 17

Strict Standards: Non-static method Settings::getShowDeleted() should not be called statically, assuming $this from incompatible context in C:\website\www.networksteve.com\windows\_lib\Entity\Topic.php on line 138

Strict Standards: Non-static method Entity_Post::queryPosts() should not be called statically in C:\website\www.networksteve.com\windows\topic.php on line 21

Strict Standards: Non-static method Settings::getShowDeleted() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Entity\Post.php on line 111

Strict Standards: Non-static method Skin::showHeader() should not be called statically in C:\website\www.networksteve.com\windows\topic.php on line 23

Strict Standards: Non-static method Skin::includeFile() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Skin.php on line 46

Strict Standards: Non-static method Settings::getSkin() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Skin.php on line 91
Multiple IP addresses mess up mapped network drives (Network Steve Forum)
Multiple IP addresses mess up mapped network drives
We have Windows Vista Ultimate on brand new computers.They connect to the network just fine. We can browse to our servers and map network drives.If you add a secondary ip address, if that ip address is lower in number than the static ip address set on the network card, and reboot ever, the mapped network drive no longer works. I'll try to explain it in more detail:Lets say my static ip address is 192.168.1.100.-I map my M: drive to a network server. It works fine and I can access it like any other drive.-I need to add a secondary ip to my pc to work on something else. I add 10.10.0.100 to my network card.--My drive mapping is still there, it still works just fine.--I am able to access the other devices on the 10. network.-The following day I have to reboot for whatever reason.-After rebooting the M: drive is no longer available and I can no longer see the server when I browse the network to look for it to remap the drive letter.-Both ip's are still listed in my network cards tcpip settings.-I remove the 10.10.0.100 from my NIC.-I browse the network again and now I can see the server and remap the network drive.-I can re-add the 10.10.0.100 ip and everything stays working as before. Unless I reboot, and then the mapped drives are no longer available.-Testing this same thing but using a higher numerical ip addres (not using the 10.10.0.100), something like 192.168.4.100, does not affect anything. As long as your secondary ip's are higher than the one you have assigned as your primary (numerically speaking), then there is no issue.So, what it looks like is Vista is allowing you to add whatever secondary ip's that you want, but if any of them are lower than the static ip you first setup, in numerical value, any network drive mappings are gone the next time you reboot. I assume because Vista is taking the lowest ip address (numerically speaking) and using it as your primary ip for that computer.Anyone seen this or know how to fix it? I'd report it to Microsoft directly but apparently the only way to do that, that I've found so far is to pay to talk to them to report it. Any help is appreciated, thanks for your time.
February 25th, 2009 10:26pm

Hi, Thank you for posting. To identify the issue more clearly, please let us know where the network share which you mapped locates. Is the server on the same network segment with the 192.168.1.100 or 10.10.0.100? Please also run ipconfig /all to export all the network settings both on this computer and the sharing server and post the information to this thread. Thanks. Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
March 2nd, 2009 5:42am

The server is on the same network segment, physically, and the ip's are in the same range as the Vista computer, so for the example above it would be the 192.168.1.100.Here is the ipconfig /all of the server, and realize that I had to change the actual ip's to the 192.168 for the example as I don't want to post some of our public ip's.C:\>ipconfig /allWindows IP Configuration Host Name . . . . . . . . . . . . : server Primary Dns Suffix . . . . . . . : xxxx.com Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : xxxx.comEthernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139 Family PCI FastEtherneNIC Physical Address. . . . . . . . . : 00-50-8D-4B-90-4C DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.19 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.140Here is the ipconfig /all of the workstation:C:\>ipconfig /allWindows IP Configuration Host Name . . . . . . . . . . . . : Lan Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoWireless LAN adapter Wireless Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : USB Wireless 802.11 b/g Adaptor Physical Address. . . . . . . . . : 00-22-5F-59-BC-1D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesEthernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet Physical Address. . . . . . . . . : 00-23-54-60-DD-86 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ad88:9294:82b1:ffa7%9(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.209(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : xx.xx.xxx.5 xx.xx.xxx.5 NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter Local Area Connection*: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:c5c:2a43:baeb:502e(Preferred) Link-local IPv6 Address . . . . . : fe80::c5c:2a43:baeb:502e%15(Preferred) Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : DisabledTunnel adapter Local Area Connection* 12: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{812F64B3-F106-4CDD-B8EF-54D0EB7FA5A6} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 13: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{2278CD0B-8C0E-4BC0-ACC4-107DE22A8C6C} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 14: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : 6TO4 Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2002:4514:afd1::4514:afd1(Preferred) Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301 DNS Servers . . . . . . . . . . . : xx.xx.xxx.5 xx.xx.xxx.5 NetBIOS over Tcpip. . . . . . . . : DisabledAlso please note that in this ipconfig /all of the workstation that I only have one ip setup currently, not two. Here it is with two ip's:C:\>ipconfig /allWindows IP Configuration Host Name . . . . . . . . . . . . : Lan Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoWireless LAN adapter Wireless Network Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : USB Wireless 802.11 b/g Adaptor Physical Address. . . . . . . . . : 00-22-5F-59-BC-1D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesEthernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet Physical Address. . . . . . . . . : 00-23-54-60-DD-86 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::ad88:9294:82b1:ffa7%9(Preferred) IPv4 Address. . . . . . . . . . . : 10.10.0.100(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 192.168.1.209(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : xx.xx.xxx.5 xx.xx.xxx.5 NetBIOS over Tcpip. . . . . . . . : EnabledTunnel adapter Local Area Connection*: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:c5c:2a43:baeb:502e(Preferred) Link-local IPv6 Address . . . . . : fe80::c5c:2a43:baeb:502e%15(Preferred) Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : DisabledTunnel adapter Local Area Connection* 12: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{812F64B3-F106-4CDD-B8EF-54D0EB7FA5A6} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 13: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{2278CD0B-8C0E-4BC0-ACC4-107DE22A8C6C} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 14: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : 6TO4 Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2002:4514:afd1::4514:afd1(Preferred) Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301 DNS Servers . . . . . . . . . . . : xx.xx.xxx.5 xx.xx.xxx.5 NetBIOS over Tcpip. . . . . . . . : DisabledThanks for your time.
March 4th, 2009 3:58pm

Any more thoughts on this, Nicholas?Thanks for your time.
Free Windows Admin Tool Kit Click here and download it now
March 12th, 2009 5:29pm

Hi, Thank you for your update. Please run CMD and then route print to export the route table and post the information to this thread for our further research. If possible, please try the following: 1. Add another NIC to your computer and set the static IP Address 10.10.0.100 on it, then set 192.168.1.100 to the previous NIC. Please check if this works. 2. It is not recommended that connecting two network segments to one NIC, it may cause unexpected issues. Therefore, you can set up a router to connect the two segments. Hope this helps. Thanks.Nicholas Li - MSFT
March 13th, 2009 1:21am

Once again please note that I had to change my ip to 192.168.1.209 in this example to protect my public ip address.C:\>route print===========================================================================Interface List10 ...00 22 5f 59 bc 1d ...... USB Wireless 802.11 b/g Adaptor 9 ...00 23 54 60 dd 86 ...... NVIDIA nForce 10/100 Mbps Ethernet 1 ........................... Software Loopback Interface 115 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface12 ...00 00 00 00 00 00 00 e0 isatap.{812F64B3-F106-4CDD-B8EF-54D0EB7FA5A13 ...00 00 00 00 00 00 00 e0 isatap.{2278CD0B-8C0E-4BC0-ACC4-107DE22A8C614 ...00 00 00 00 00 00 00 e0 6TO4 Adapter===========================================================================IPv4 Route Table===========================================================================Active Routes:Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.209 276 192.168.1.0 255.255.255.0 On-link 192.168.1.209 276 192.168.1.209 255.255.255.255 On-link 192.168.1.209 276 192.168.1.255 255.255.255.255 On-link 192.168.1.209 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 169.254.0.0 255.255.0.0 On-link 192.168.1.209 296 169.254.255.255 255.255.255.255 On-link 192.168.1.209 276 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.1.209 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.1.209 276===========================================================================Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.1.1 Default===========================================================================IPv6 Route Table===========================================================================Active Routes:If Metric Network Destination Gateway14 1125 ::/0 2002:c058:6301::c058:6301 1 306 ::1/128 On-link15 18 2001::/32 On-link15 266 2001:0:4137:9e50:c5c:2a43:baeb:502e/128 On-link14 1025 2002::/16 On-link14 281 2002:4514:afd1::4514:afd1/128 On-link 9 276 fe80::/64 On-link15 266 fe80::/64 On-link15 266 fe80::c5c:2a43:baeb:502e/128 On-link 9 276 fe80::ad88:9294:82b1:ffa7/128 On-link 1 306 ff00::/8 On-link15 266 ff00::/8 On-link 9 276 ff00::/8 On-link===========================================================================Persistent Routes: None
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2009 4:01pm

And here it is with both ip's:C:\>route print===========================================================================Interface List10 ...00 22 5f 59 bc 1d ...... USB Wireless 802.11 b/g Adaptor 9 ...00 23 54 60 dd 86 ...... NVIDIA nForce 10/100 Mbps Ethernet 1 ........................... Software Loopback Interface 115 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface12 ...00 00 00 00 00 00 00 e0 isatap.{812F64B3-F106-4CDD-B8EF-54D0EB7FA5A6}13 ...00 00 00 00 00 00 00 e0 isatap.{2278CD0B-8C0E-4BC0-ACC4-107DE22A8C6C}14 ...00 00 00 00 00 00 00 e0 6TO4 Adapter===========================================================================IPv4 Route Table===========================================================================Active Routes:Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 10.10.0.100 276 10.10.0.0 255.255.255.0 On-link 10.10.0.100 276 10.10.0.100 255.255.255.255 On-link 10.10.0.100 276 10.10.0.255 255.255.255.255 On-link 10.10.0.100 276 192.168.1.0 255.255.255.0 On-link 10.10.0.100 276 192.168.1.209 255.255.255.255 On-link 10.10.0.100 276 192.168.1.255 255.255.255.255 On-link 10.10.0.100 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 169.254.0.0 255.255.0.0 On-link 10.10.0.100 296 169.254.255.255 255.255.255.255 On-link 10.10.0.100 276 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.10.0.100 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.10.0.100 276===========================================================================Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.1.1 Default===========================================================================IPv6 Route Table===========================================================================Active Routes:If Metric Network Destination Gateway14 1125 ::/0 2002:c058:6301::c058:6301 1 306 ::1/128 On-link15 18 2001::/32 On-link15 266 2001:0:4137:9e50:c5c:2a43:baeb:502e/128 On-link14 1025 2002::/16 On-link14 281 2002:4514:afd1::4514:afd1/128 On-link 9 276 fe80::/64 On-link15 266 fe80::/64 On-link15 266 fe80::c5c:2a43:baeb:502e/128 On-link 9 276 fe80::ad88:9294:82b1:ffa7/128 On-link 1 306 ff00::/8 On-link15 266 ff00::/8 On-link 9 276 ff00::/8 On-link===========================================================================Persistent Routes: NoneC:\>
March 17th, 2009 4:09pm

Hi, Thank you for updating. I noticed there is a Persistent Route entry in the route table. If it is not necessary, please just remove this entry and reboot the computer to see if it helps. To remove the entry, please refer to the steps below: 1. Open an elevated command prompt. 2. Type the following command, and then press ENTER: route delete 0.0.0.0 3. Reboot the computer and run route print again and check the results. You can paste the router table to the thread again if the issue persists. For more information, please also refer to the following document: Route http://technet.microsoft.com/en-us/library/bb490991.aspx The IP routing table http://technet.microsoft.com/en-us/library/cc779122.aspx Hope this helps. Thanks you for your efforts.Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
March 20th, 2009 2:31am

Ok, I removed the Persistent Route in the manner you listed above. Same result as from the original post.Route Print after removing the persistent route and a reboot:Microsoft Windows [Version 6.0.6001]Copyright (c) 2006 Microsoft Corporation. All rights reserved.C:\>route print===========================================================================Interface List10 ...00 22 5f 59 bc 1d ...... USB Wireless 802.11 b/g Adaptor 9 ...00 23 54 60 dd 86 ...... NVIDIA nForce 10/100 Mbps Ethernet 1 ........................... Software Loopback Interface 115 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface12 ...00 00 00 00 00 00 00 e0 isatap.{812F64B3-F106-4CDD-B8EF-54D0EB7FA5A6}13 ...00 00 00 00 00 00 00 e0 isatap.{2278CD0B-8C0E-4BC0-ACC4-107DE22A8C6C}14 ...00 00 00 00 00 00 00 e0 6TO4 Adapter===========================================================================IPv4 Route Table===========================================================================Active Routes:Network Destination Netmask Gateway Interface Metric 10.10.0.0 255.255.255.0 On-link 10.10.0.100 276 10.10.0.100 255.255.255.255 On-link 10.10.0.100 276 10.10.0.255 255.255.255.255 On-link 10.10.0.100 276 192.168.1.0 255.255.255.0 On-link 10.10.0.100 276 192.168.1.209 255.255.255.255 On-link 10.10.0.100 276 192.168.1.255 255.255.255.255 On-link 10.10.0.100 276 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 169.254.0.0 255.255.0.0 On-link 10.10.0.100 296 169.254.255.255 255.255.255.255 On-link 10.10.0.100 276 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.10.0.100 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.10.0.100 276===========================================================================Persistent Routes: NoneIPv6 Route Table===========================================================================Active Routes:If Metric Network Destination Gateway 1 306 ::1/128 On-link14 1025 2002::/16 On-link14 281 2002:4514:afd1::4514:afd1/128 On-link 9 276 fe80::/64 On-link 9 276 fe80::ad88:9294:82b1:ffa7/128 On-link 1 306 ff00::/8 On-link 9 276 ff00::/8 On-link===========================================================================Persistent Routes: None----------------------------------After that reboot I was unable to access my network drives and no longer able to get on the internet, so I removed the 10.10.0.100 address and rebooted again. Still no luck, once it was booted back up, I still could not access anything. I set my ip to obtain automatically, and saved it, and then put my static ip back in again which in turn recreated the persistent route and then I was once again able to get back on the internet.
March 23rd, 2009 8:14pm

Hi, Thank you for updating. At this time, please try the following again to see if it works: 1. Open an elevated command prompt. 2. Type the following command, and then press ENTER: route delete 0.0.0.0 3. Go to Network and Sharing Center, select Manage network connections. 4. Right click the connection which accesses the private network and choose properties. 5. Find Internet Protocol (TCP/IP) Version 4 in the list. 6. Click Properties, and then input the IP address, Subnet mask and DNS server settings manually. (Note: Leave the Default gateway empty.) 7. Then click OK to apply the settings and close the window. 8. Please reboot the computer to check the results. Thank you for your efforts. Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
March 25th, 2009 3:17am

Doing that produces the same effect: No access to the local network or internet. In fact, as soon as you do the route delete 0.0.0.0 the pc loses connectivity to the local network and internet.
March 25th, 2009 2:55pm

Does a lack of response indicate that I've actually found a bug and it's something Microsoft will have to address/fix? :-D One can always hope...
Free Windows Admin Tool Kit Click here and download it now
April 3rd, 2009 7:20pm

kdsmith- Did you ever find a solution to this problem. I am having the almost the identical problem and cannot find a solution anywhere. Your post here is the closet to my same problem and I am curious if you ever fixed it. Thanks.
May 17th, 2010 5:44pm

I have the same error. after i added a second ip the network drives are no longer reachable. (because windows takes the second address as primary) it seems to be sortet by the numbers. first ip 192.168.1.210 second ip 10.71.1.210 in xp this is working. ;-( i forgot, that you have to boot that you can see the problem. if you edit it on the fly its working.
Free Windows Admin Tool Kit Click here and download it now
November 9th, 2010 3:32am


Strict Standards: Non-static method Settings::getRecentTopicsLimit() should not be called statically, assuming $this from incompatible context in C:\website\www.networksteve.com\windows\_lib\Entity\Topic.php on line 120

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics

Strict Standards: Non-static method Skin::showFooter() should not be called statically in C:\website\www.networksteve.com\windows\topic.php on line 119

Strict Standards: Non-static method Skin::includeFile() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Skin.php on line 56

Strict Standards: Non-static method Settings::getSkin() should not be called statically in C:\website\www.networksteve.com\windows\_lib\Skin.php on line 91