Bizarre XP VPN Probs. About to slash wrists. Please Help!!

[prak355]

Hi, we have a client who is trying to connect to a remote office through VPN on a XP workstation. Everything was working fine untill this week, for some reason it stopped connecting and throwing up 721 connection errors. I have checked both client and server and everything is setup fine. I can VPN into the server using the client's credentials from other locations. To make things worse, I can VPN into other places from the same workstation just fine. It's almost as if the workstation doesn't like connections to that one ip/server?!?!

Have tried reinstalling service packs/sfc/repairing from xp cd. Nothing. Insanity is around the corner, please help.

Thanks.
Prak.

 

[bcastner]

1. By now you need to repair your Winsock service stacks. See the "fix" here: faq779-4625

2. Use System Restore and revert the Hotfix:

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/ms04-004.asp

 

[prak355]

Thanks for the reply BCaster, have tried the fix and it didn't do anything. Got really desperate last week and did a complete format/reload. The problem still exists!
It's so bizzare. It has to be server side now, is there anything on 2000 server that could be stopping a certain i/p or range? I've checked user credentials etc.. can even vpn into the server using her details. The user can vpn to anywhere else just fine...

Thanks.
Prak.

 

[Binks7]

Prak355:

I recently spent 5 hours with Microsoft on this same issue. We tried everything, including the Winsock rolling back Hotfixes, etc. My clients could VPN into other servers setup the same way, no problem. The problem was limited only to this one particular server W2k and WinXP SP1 clients. It had worked for 2 1/2 years then after the RPC buffer overflow patch stopped connecting. When it came down to it, I uninstalled RRAS, wiped it out. rebooted the server, then reinstalled RRAS, but with a new IP range pool. It worked. Microsoft could not explain why it would not function before or why this fixed the problem. A reinstall with the same IP range would not work. Microsoft looked at logs all day and couldn't figure it out. Both the client and the server acted as if they were connected, but no authentication was actually taking place. You never know what these "patches are going to do.