VPN won't connect

[Guest]

i was joining an XP pro client at a remote site to the domain. set DNS to the
DC etc and connected desktop vpn - all fine. On joining the domain, it
reported that it was unable to change the computer's name and had registered
it under it's old name.

Now when trying to log on to domain for first time ("log on using dial up
connection"), the vpn connected, but said it could not log the user on to
domain due to an account problem. It did this twice, then refused to connect
the vpn in the first place. Logged back on to machine using a local account
and the vpn would no longer connect from there either. It says "verifying
user name and password" then hangs and disconnects. This all worked fine
until the change from workgroup to domain.

Checking in AD, the computer is registered under the new name I gave it even
though it reported it was done under the old name, and the machine still
shows the old name. So I think something has gone astray during the domain
join. I have since left the domain and gone back to workgroup membership, but
the vpn will still not connect under any user name, yet any user name will
work from another machine.

Can anyone suggest what is preventing it from connecting. I know that error
normally occurs with the GRE protocol on the remote router/firewall, but as
all vpns work from other machines, i don't think it's the router or server -
it just seems to be affecting this one client machine.

Could a faulty domain join have corrupted something in the network
settings/registry?

I've deleted and recreated the vpn several times but to no avail.

Any help would be greatly appreciated.

Thanks

 

[Robert L [MS-MVP]]

what's your VPN? What's the router at remote site?
For more and other information, go to http://howtonetworking.com.

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
I recommend Brinkster for web hosting!

i was joining an XP pro client at a remote site to the domain. set DNS to the
DC etc and connected desktop vpn - all fine. On joining the domain, it
reported that it was unable to change the computer's name and had registered
it under it's old name.

Now when trying to log on to domain for first time ("log on using dial up
connection"), the vpn connected, but said it could not log the user on to
domain due to an account problem. It did this twice, then refused to connect
the vpn in the first place. Logged back on to machine using a local account
and the vpn would no longer connect from there either. It says "verifying
user name and password" then hangs and disconnects. This all worked fine
until the change from workgroup to domain.

Checking in AD, the computer is registered under the new name I gave it even
though it reported it was done under the old name, and the machine still
shows the old name. So I think something has gone astray during the domain
join. I have since left the domain and gone back to workgroup membership, but
the vpn will still not connect under any user name, yet any user name will
work from another machine.

Can anyone suggest what is preventing it from connecting. I know that error
normally occurs with the GRE protocol on the remote router/firewall, but as
all vpns work from other machines, i don't think it's the router or server -
it just seems to be affecting this one client machine.

Could a faulty domain join have corrupted something in the network
settings/registry?

I've deleted and recreated the vpn several times but to no avail.

Any help would be greatly appreciated.

Thanks

 

[Guest]

It's a PPTP vpn from the desktop to the public IP of a US Robotics router,
which is then forwarded to the domain controller. The router has GRE port 49
forwarded as well as PPTP port 1723. All other users can connect VPN's from
their machines no problem, and this user can connect from a different
machine.

It's just this one specific client machine that won't connect for anyone and
the problem only started happening after joining it to the domain, where
there appeared to be a discrepancy between machine names. I'm beginning to
think a repair install of XP may be required unless anyone has any other
suggestions.