Configuring VPN Server not allowing client to connect

[ljCharlie]

Sorry for double posting in here and in the Windows 2003 forum. Actually, I did not know there is this VPN forum until I already posted in the Windows 2003 forum. Below is my question.

I have the followed the instruction on how to setup a Windows 2003 VPN server from this link:

http://www.microsoft.com/windowsserver2003/techinfo/overview/connectremote.mspx

and still I'm having problems. Here's the error I got from the client side when trying to connect to the VPN server:

Checking network protocol connections…

TCP/IP reporter 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.

And here is the Warning and Error from the VPN Server System event log:

Event Type: Warning
Event Source: RemoteAccess
Event Category: None
Event ID: 20167
Date: 2/7/2005
Time: 8:30:43 AM
User: N/A
Computer: myComputer
Description:
No IP address is available to hand out to the dial-in client.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: RemoteAccess
Event Category: None
Event ID: 20050
Date: 2/7/2005
Time: 8:30:43 AM
User: N/A
Computer: myComputer
Description:
The user myDomain\myself connected to port VPN4-127 has been disconnected because no network protocols were successfully negotiated.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Will anyone tell me what's going on and how to solve this problem?

Any help is appreciated.

ljCharlie

 

[Stewartp]

I am getting exactly the same thing. I'll ley you know if I find a solution.....Happy Hunting

Cheers
Stewart

 

[jcurtiss]

No IP address is available to hand out to the dial-in client."

you have to set this up in your incoming vpn connection, or RRAS if you're using 2000 server. the clients either get a dhcp ip address or you can specify a range.

 

[VinylDave]

as jcurtiss says, dhcp seems to be disabled on the remote site. Your connection dials in, with no ip, looks for an ip withing the range, cannot communicate. set the tcp/ip settings for that particular dial connection to static ip within the range of the remote site, obviously without conflict.