How setup Windows 2003 VPN server?

[ljCharlie]

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

 

[ljCharlie]

After the vpn client connected, I do ipconfig/all and I do received the IP address within the range of the specified IP addresses in the Routing and Remote Access property/IP tab. The DNS Servers ip address is also correct. But somehow I just can not map to any drive.

ljCharlie

 

[ljCharlie]

And yes, the IP address of the primary WINS Server is also correct.

 

[ljCharlie]

And when I tried to map, the error said: The network path \\domainComputer\myShare$ could not be found.

And by the way, when I ping the vpn server, I used 192.168.0.2. If I used the public IP then I won't be able to ping the vpn server either.

ljCharlie

 

[MoobyCow]

It could be a problem with permissions then. When you're setting up a VPN there will be someplace that you can say what parts of the network you want your clients to be able to access.

You can try putting the appopriate mappings in your local hosts files:

http://accs-net.com/hosts/how_to_use_hosts.html

If putting the IP address of your file server in the hosts file does not work, then your VPN is blocking you from accessing the network and you have to find that setting and allow yourself access to the network.

 

[ljCharlie]

Thanks! I'll let you know how it goes.

ljCharlie

 

[ljCharlie]

I'm guessing that it might have something to do with filtering. I mean I am able to connect to the vpn server but just unable to map to any network drives. I believed it be the filtering issue; but I'm not sure how to go about verifying.

ljCharlie

 

[jmicho]

ljCharlie,

I was trying to set up a VPN server on my home network, and was following along your thread, and wanted to ask you some questions, I have a 2003 server as a domain controller with AD, with DCHP and DNS installed on it and another 2003 controller that is just a member server, and I tried to install VPN on that computer, and I followed the RAS wizard, and wanted to say have one of my xp laptops connect to my network, which is on its own LAN behind a linksys router I connect to the internet via Cable Roadrunner and I am not sure how to connect my laptop to the VPN server, if I use AOL and connect to the internet and then try and connect to the VPN server it does not work, I am curious how you set up your VPN to actually connect, I could really use some help!!! Thanks, Jeff

 

[ljCharlie]

You did follow this white paper here,

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

correct?

If your client computer couldn't connect to the vpn server, what are some of the errors? Check the event log on the client computer and also on the vpn server.

I got mine to connect but could not access any network resource so I'm not sure I'm qualify to help you out.

ljCharlie

 

[MoobyCow]

ljCharlie,

Sorry, I'm out of advice. I don't use the same VPN software as you, so I don't know where to tell you to look. On my VPN there is a security setting on which you tell the VPN what network resources you want the VPN users to have access to.

I would look around and see if you can find something like that.

 

[ljCharlie]

MoobyCow, many thanks for all your suggestions and help so far. I'll keep looking and see if there is any solution to this problem.

ljCharlie

 

[hugbear]

Guys been following the messages. Try this Charlie map the a network share using using IP, ie \\192.168.x.x\nameofshare

Thios will give an indication if the problem is with DNS or permissions.

 

[ljCharlie]

Thanks, hugbear, for trying to help. I am able to ping and map the vpn server using the \\192.168.x.x\sharename; however, the problem is I want to map our file server and not the vpn server. I can only ping and map the vpn server and no other computers on the network.

 

[hugbear]

Ok, now I see what the problem is. If it is only a few clients use the hosts/Lmhosts file on the client machine and add the server and IP address if it is quite a few then will llok up my notes as I have solved this puzzle before (about a year ago).

 

[ljCharlie]

Thanks, hugbear. I'm not sure if I need to use lmhosts file because I already have the WINS server setup. Once the vpn client got connected, the IP address changed to 192.168.x.x and this is normal, correct? I have searched a lot of places and have no help on the problem I am having. I'm not sure why I am able to ping/map the vpn server using the 192.168.x.x, but unable to ping or map the vpn server using the computer name or the actual IP address that is not 192.168.x.x. Something is wrong there, I think.

ljCharlie