|
|
Joined: Jun 2005
Posts: 261
Member
|
Member
Joined: Jun 2005
Posts: 261 |
Does he have VMWare installed? I've found that the default VMWare network settings sometimes conflict with some of the SOHO routers, although if he's able to browse the lan, that is probably not the problem.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Aug 2005
Posts: 6,692
Member
|
Member
Joined: Aug 2005
Posts: 6,692 |
Well I think I've got it resolved. I finally got my hands on them today and the problem got even more bizarre. On my network they worked flawlessly, so I took both of them back over to the client's house. Sure enough when I got over there the problems popped up again, however my laptops worked fine from his network, so I rebuilt the TCP Stack, and then upgraded all the network drivers just as a precaution. By the time I got done they seemed to be fine. The real test will come when he gets them back to the law firm tomorrow morning and we find out if they work there.
Thanks for all the input guys.
|
|
|
|
Joined: Oct 2007
Posts: 289
Member
|
Member
Joined: Oct 2007
Posts: 289 |
I would also try to find out whether the customer uninstalled something recently. Also, run an antivirus & antispyware check on the laptops and the network. There is a somewhat obscure part of Windows networking called "Winsock" that provides "jacks" for 3rd party network extensions (called LSPs), to plug into. Occasionally, when the 3rd party software is uninstalled, the "plugs" fail to remove. Also, spyware often plugs into these software "jacks". If this is the case, (and I'm not sure it is, but it looks like it), it wouldn't be a bad idea to run a complete scan on your net too. There is a way to tell whether the problem is a Winsock LSP gone bad:
You need to install the XP Support Tools on the Windows CD (browse to \Support\Tools, run Setup.exe). Then, open a command window and enter: netdiag /test:winsock /v. If the diag found a problem, open a command window and type: netsh winsock reset Then immediately restart the computer. After restart you should reinstall the TCP stack. This should do it. The above work only on Win XP SP2. Mind you, there's a chance Winsock was reset after you reinstalled the drivers.
|
|
|
Forums84
Topics94,515
Posts639,961
Members49,847
|
Most Online5,661 May 23rd, 2018
|
|
1 members (WolfpactVI),
170
guests, and
41
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|