Windows xp and vista Network/internet issue

Hi People,

We Been having these issue for About 1 year now,

We have a network of 5 vista machines, 3 xp machine, 7 voip phone and 1 network printer.

The internet of all 3 windows xp machine keeps on dropping once everyday, removing the ethernet cable and putting the cable back doesn't help it, restarting the system doesn't help it, refreshing the ip doesn't, restarting the router either,

the only way I found to give them internet again is to manually set the ip and dns configuration daily.

If somebody out there has experience these same issues,

I would really appreciate your help.

Thank you,
Pablo

Do all 3 XP machines lose internet connectivity at the same time, or even within 10 or 15 minutes of each other?

Are the XP machines plugged into the same switch/router as the Vista boxes, the VoiP device, and the printer?

Does moving the cables around at the switch/router end make any difference as to which machines/devices experience these connectivity losses? In other words, if you plug a Vista box into the same switch port where an XP machine was previously connected, and vice versa, will the Vista client now develop the same issue instead of XP?

Hi,

Thanks for the response

They seem to loose the ip each morning when its trying to re-lease the ip address

All 3 windows xp system , vista, voip phone, printer are connected to the same switch,

Moving the xp systems to a different ports on the switch make no difference or if connecting a vista system on that specific port (Where the Xp System was ) still has the same problem.

Xp will not be able to connect again, and all Vista system will always work

Thank you
Pablo

pablopablo said:

They seem to loose the ip each morning when its trying to re-lease the ip address

Click to expand...

Can you tell me more about the timing there please? I'm interested to understand to what extent the 3 XP machines seem to develop problems at the same time.

Why do you believe that (DHCP) lease renewal is somehow linked to the problem trigger?

Hi,

I will give you more information tomorrow when I am onsite,

Thanks Man

ON THE SYSTEM LOG

9:09 A.M (SYSTEM 1)
------------------------
TIME PROVIDER NTPCLIENT: AN ERROR OCCURRED DURING DNS LOOKUP OF THE MANUALLY CONFIGURED PEER 'TIME.WINDOWS.COM,0X1.

NTPCLIENT WILL TRY THE DNS LOOKUP AGAIN IN 15 MINUTES.

THE ERROR WAS: A SOCKET OPERATION WAS ATTEMPTED TO AN UNRERACHABLE HOST. (0X80072751)


11:06 A.M (SYSTEM 1)
-------------------------
THE MASTER BROWSER HAS RECIEVED A SERVER ANNOUNCMENT FROM THE COMPUTER OPEN-PC THAT BELIEVES THAT IT IS THE MASTER BROWSER FOR THE DOMAIN ON TRANSPORT NETBT_TCPIP_{459774CE-89C4-439A-8.

THE MASTER BROWSER IS STOPPING OR AN ELECTION IS BEING FORCED


9:36 A.M (SYSTEM 2)
------------------------------
Your computer was not assigned an address from the network ( by the DHCP server) for the Network Card With network address 0016767e5b70.
The following error occurred: The semaphore timeout period has been expired.
Your computer will continue to try and obtain an address on its own from the network address ( DHCP) server.

9:59 A.M (SYSTEM 2)
----------------------------
Your computer has automatically configured the IP address for the Network Card with network address 0016767E5B70.
The IP address being used is 169.254.***.***.

SYSTEM 1 & SYSTEM 2
Intel ( R) PRO/100 VE Network connection: Has determined that the adapter is not functioning properly.

The 1st error suggests that the machine had already lost its valid IP lease by 9:09am when the time sync was attempted.

The 2nd error is by itself harmless. It's a normal part of (NetBIOS) browser operation, except in this case it may also be a side-effect of the machine losing/gaining network connectivity.

The 3rd one is an obvious problem.


By default, DHCP clients will attempt to renew their leases (for the first time) at 50% of the lease duration interval, so the fact that this appears to happen to you every morning suggests to me that the lease interval configured on the DHCP server (the router?) is uncharacteristically short. IPCONFIG /ALL would tell you precise details of that interval. If it's anything shorter than a week, you may possibly gain some respite by increasing the lease duration to say 2 weeks, or even longer.

Otherwise, the most obvious explanation for these symptoms would a problem with the NIC drivers on the 3 XP machines - especially if they all share the same NIC model and the same driver. Something happens to them internally at DHCP lease renegotiation time and there is no obvious link to the hardware since other OSs and devices don't have DHCP problems using the same infrasturcture.

I'd suggest briefly testing a completely different model of NIC on one of the XP machines.