Vista drops network map connection

[Guest]

My home network consists of a Windows XP Home SP2 machine and a Vista Home
Premium machine. Both machines connect to the internet via a cable/dsl router
connected to a cable modem. There is a shared printer that hangs off of the
Vista machine. LLTD protocol has been installed on XP and netBIOS over TCP/IP
has been set on Vista. XP is running the Windows firewall; Norton Internet
Security is installed on Vista with the Windows firewall set to off.

Upon initial boot of Vista both computers are able to see each other, files
can be transferred and print jobs are successful. The problem is that the
connection eventually disappears from the Vista network map (I have been
unable to determine the time variant thus far). When this happens, neither
machine can see the other and files are unable to be transferred. However, XP
is still able to print. Running Network Discovery on Vista is no help; only a
reboot of the Vista machine will solve the issue.

Any ideas/suggestions?

 

[Robert L [MVP - Networking]]

It could be computer browser issue. Any errors in the Event Viewer?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
My home network consists of a Windows XP Home SP2 machine and a Vista Home
Premium machine. Both machines connect to the internet via a cable/dsl router
connected to a cable modem. There is a shared printer that hangs off of the
Vista machine. LLTD protocol has been installed on XP and netBIOS over TCP/IP
has been set on Vista. XP is running the Windows firewall; Norton Internet
Security is installed on Vista with the Windows firewall set to off.

Upon initial boot of Vista both computers are able to see each other, files
can be transferred and print jobs are successful. The problem is that the
connection eventually disappears from the Vista network map (I have been
unable to determine the time variant thus far). When this happens, neither
machine can see the other and files are unable to be transferred. However, XP
is still able to print. Running Network Discovery on Vista is no help; only a
reboot of the Vista machine will solve the issue.

Any ideas/suggestions?

 

[Guest]

Yes - a bunch. Mostly Dhcp-Client 1003 (timeout expired) with the occasional
1000 (lost lease) and 1002 (lease denied). I can't be positive, but it looks
like it may drop the map when the lease is denied. The server that is denying
the lease is at IP 192.168.1.101

From the Vista machine: Pinging the XP machine by name gets an immediate
response from 192.168.1.100. Pinging the Vista machine by name gets Request
timed out from the MAC address. When I try to ping 192.168.1.101, I also get
request timed out.

From the XP machine: Pinging the XP machine by name gets an immediate
response from 192.168.1.100. Pinging the Vista machine by name gets an
immediate response from 192.168.1.101.

According to XP, it appears that the Vista machine is supposed to have IP
192.168.1.101 However, I've looked at both TCP/IP v4 and v6 settings in the
network connections and both are set to DHCP. And one more piece of info:
even though Vista drops the network map, the machine is still able to access
the internet.

I'm confused now. Should I set the Vista machine to 101 and see what happens?

 

[Robert L [MVP - Networking]]

We need more information to help. Do you have domain network? What are the description of those events?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Yes - a bunch. Mostly Dhcp-Client 1003 (timeout expired) with the occasional
1000 (lost lease) and 1002 (lease denied). I can't be positive, but it looks
like it may drop the map when the lease is denied. The server that is denying
the lease is at IP 192.168.1.101

From the Vista machine: Pinging the XP machine by name gets an immediate
response from 192.168.1.100. Pinging the Vista machine by name gets Request
timed out from the MAC address. When I try to ping 192.168.1.101, I also get
request timed out.

From the XP machine: Pinging the XP machine by name gets an immediate
response from 192.168.1.100. Pinging the Vista machine by name gets an
immediate response from 192.168.1.101.

According to XP, it appears that the Vista machine is supposed to have IP
192.168.1.101 However, I've looked at both TCP/IP v4 and v6 settings in the
network connections and both are set to DHCP. And one more piece of info:
even though Vista drops the network map, the machine is still able to access
the internet.

I'm confused now. Should I set the Vista machine to 101 and see what happens?

 

[Guest]

I do not understand what you mean by "domain network"... There are no error
logs with that title and my network is a 2 node home network that I *think*
is statically assigned...

The description of the previously mentioned events are as follows (note the
two different network addresses in 1003; I have only one NIC):

1000 - Your computer has lost the lease to its IP address 192.168.1.101 on
the Network Card with network address 001A92101D14.

1002 - The IP address lease 192.168.1.101 for the Network Card with network
address 001A92101D14 has been denied by the DHCP server 192.168.1.1 (The DHCP
Server sent a DHCPNACK message).

1003 - Your computer was not able to renew its address from the network
(from the DHCP Server) for the Network Card with network address
8000600FE800. The following error occurred:
The operation was canceled by the user.. Your computer will continue to try
and obtain an address on its own from the network address (DHCP) server.

1003 - Your computer was not able to renew its address from the network
(from the DHCP Server) for the Network Card with network address
001A92101D14. The following error occurred:
The semaphore timeout period has expired.. Your computer will continue to
try and obtain an address on its own from the network address (DHCP) server.

 

[Stanley Feng \(MSFT\)]

Take a look at this KB article http://support.microsoft.com/kb/928233

Please post-back to let us know if this solves your problem...