Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN with Windows XP Pro

Status
Not open for further replies.

rpg121

Programmer
Joined
Mar 14, 2001
Messages
89
Location
US
I have a Windows 2000 Server that I have Routing and Remote Access set up to accept VPN connections. VPN with Windows 2000 Professional clients works great, but the same is not true for Windows XP clients. Whenever an XP machine attempts to connect, I get a 733 error. It says that I need to adjust TCP/IP settings.

For both 2000 and XP machines, I have default settings enabled except I have "use remote gateway" setting disabled. I am also connecting through PPTP.

Thanks for the help.
 
On the XP client, open the setting for the VPN connection. Click the "networking" tab. Make sure the type of server is set to PPTP. Click the settings button. Clear the "Negotiate Multi-link for Single Link connections" check box. Try the connection again.

If those all appear to be OK and you still aren't having any luck, post back the specific error you are receiving, including the text. 733 error can mean several different things (although the above covers the most common), somtimes the text will narrow it down a bit.
 
I tried that and no luck. Here's the error:

Checking network protocol connections...

TCP/IP CP reported error 733: A connection to the remote computer could not be completed. YOu might need to adjust the protocols on this computer. For further assistance, click More Info or search Help and Support Center for this error number.

Hope that helps. Thanks.
 
If you were having problems with clients prior to XP, I would guess that for whatever reason TCP/IP was not bound to the VPN connection. In theory this should not be possible as TCP/IP is bound to every connection with XP. You don't have a major problem with the TCP/IP stack, or you wouldn't have any connection at all. I also get the impression that you have multiple XP clients with this problem.

Having said that, other protocols being present on the server side but not on the client side can in certain combinations cause this error, so check to make sure the protocols bound on the server side are also bound on the client side. If for some reason TCP/IP is not bound on the server side you would see this problem as well.

Also, there were problems with ppp in W2K, particualy prior to SP2. Make sure you are up to date with those service packs on both sides.

Failing that, enable logging on the server side and see if anything of interest shows up there. If nothing there, I would enable logging on the client side and check that out. Both sides should show something, but at least one side will for sure. Doesn't really matter which side you start with, I usually start with the server because it is a little easier start to finish and I'm lazy. Instructions here:

The article mentions it, but make sure to disable logging when your done as it does eat hard drive space. Also, the article doesn't mention XP, but the netsh instructions for W2K Pro should work.

If you see something there you don't understand, post back.
 
I got it! I was looking around in other forums and help sites. I had to change the IP Address Assignment to Static address pool instead of DHCP and it works fine. Thank y'all for the help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top