General discussion


Virtual Private Network

By sam ·
I am trying to connect to Virtual Private Network and I receive the following error:

?Error 800: Unable to establish the VPN connection. The VPN server may be unreachable, or security parameters may not be configured properly for this connection?

I can connect through ?Remote Desktop? with the same credentials, but not through the ?VPN? connection.

Any thoughts as to why the VPN will not connect?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by cmiller5400 In reply to Virtual Private Network

Are you trying to vpn to the same server you are remote desktoping into?

Collapse -

by sam In reply to Virtual Private Network

Yes, I am trying to vpn to the same server that I can connect to remote desktop through.

Collapse -

by GirlGeek12 In reply to Virtual Private Network

Are you trying to connect over the LAN that the server is on? What type of VPN client are you using?

Collapse -

by sam In reply to Virtual Private Network

We are using Windows VPN client.

Collapse -

by w2ktechman In reply to Virtual Private Network

VPN clients use the IE settings for proxy info. Try opening a web page, if it doesnt work, look over your proxy settings.

If the web pages open (not intranet pages), then look over the settings for vpn server/server groups. ping the servers, make sure DNS is working properly. if not, try reinstalling vpn SW

Collapse -

by cmiller5400 In reply to Virtual Private Network

Ok. So tell me if I got this wrong. You are trying to create a vpn connection directly to a server? Is this server on the same network or over the internet? If it is on the same network, there is no need to vpn the server, just use remote desktop. If you are going through the internet, is the vpn server software installed on this server you are trying to connect to?

Collapse -

by curlergirl In reply to Virtual Private Network

Either the server is not running RRAS, which is the server-side application that accepts incoming VPN connections; the server is running RRAS but for some reason is not reachable from where you are; or your user ID is not permitted to log on using a VPN connection. Network access permissions for RDP and VPN connections are different, so the fact that you can connect one way does not automatically mean you can connect the other way. So, first make sure that the server is running RRAS, that it is started and waiting to accept connections. Then, make you sure that you are using the correct IP address or FQDN when trying to connect to it. If you are sure both those things are OK, then you need to check with your network admin to see if you can be given permission to log on using a VPN connection. If you are the network admin, then you need to examine your RRAS policies and also your user ID properties to see what is preventing you from having permission to connect over the VPN.

Hope this helps!

Collapse -

Most Probabily Reason Ports Closed

by esvaras In reply to

Well, when you try to establish a VPN connection is necessary for a success connection that the ports used by the VPN Network are open, in many opportunities you have a physicall router between your local network and the internet and this dispositive has closed this ports or your firewall has closed the ports. For that reason you need to open, before attend to establish the connection ports TCP:1723 and UDP:47. I had the same problem and it was the right solution

Collapse -

by sgt_shultz In reply to Virtual Private Network

here you go:(snipped from mskb, link at end of this post)
Error Message: VPN Connection Error 800: Unable to Establish Connection
View products that this article applies to.
Article ID : 31**08
Last Review : November 4, 2003
Revision : 1.0
This article was previously published under Q31**08
When you try to establish a virtual private network (VPN) connection, you may receive the following error message:
Error 800: Unable to establish connection

Back to the top

This issue may be caused by a router that has outdated firmware. For example, this issue may occur if you are using a Cisco router with firmware that is dated 2000 or earlier.

To verify that this is the cause, look at a network trace. The Cisco device advertises a 0 window size in the TCP handshake on port 1723.**08

Related Discussions

Related Forums