Link to home
Start Free TrialLog in
Avatar of SBSWIZARD
SBSWIZARDFlag for United States of America

asked on

VPN Error 800 - SBS 2008

Trying to connect machine to network so I can join to domain.

Tried connecting and received Error 800 - The remote connection was not made because the attempeted VPN tunnels fialed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.

Checked the Verizon router. Port 1723 is opened and forwarded to the server.

Checked the SBS Console and saw the VPN connection was turned off. Ran the "Configure a virtual private network" wizard. Received a green checkmark on the "Configure virtual private networking on the server." Received yellow warning on "Internet Router" - ports must be manually opened on the router - 1723 (which I did).

Checked canyouseeme.org for port 1723 and it failed with a connection time out.

Firewall on the server is turned off.

Not sure what I am missing.
Avatar of Kimputer
Kimputer

Just opening port 1723 isn't always enough since GRE protocol 47 is also needed. Sometimes it's not part of the port forwarding page, and it's described as "PPTP forwarding/tunneling enabled" on another page.
To know if it's a firewall/router issue, test the VPN locally first (use pc inside your network to connect to the server). If that's successful, it's either your router/firewall or your ISP might be interfering.
Post up the model number of your router so we can see if it supports VPN.
Avatar of SBSWIZARD

ASKER

@Kimputer

GRE is also added to the Port Forwarding page.

@VB ITS

It's the normal red/black Actiontec Verizon router that is supplied. Not onsite to grab the model number.
SOLUTION
Avatar of Kimputer
Kimputer

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok. Must have jumped over that comment earlier. Will test later tonight. Thanks.
Ok. I tested from a machine inside the network and was able to establish a VPN connection using the server's internal IP address.

So next step is the router. What else do I need to look for since GRE and 1723 are opened and pointing towards the internal server?
Are you able to get the model number of the router? That way we can have a look up the manual/specs to see if it natively supports PPTP port forwarding. You could also look at upgrading the firmware on the router as sometimes the manufacturer releases updates to address these sort of issues.

When you went to create the port forwarding rule, did you create a new rule for port 1723or did you use a pre-defined rule which is usually named PPTP or something along those lines?
I used a pre-defined rule that set already called "VPN" that had a setting for TCP 1723 as the port.
Model: A90-9100EM15-10
Firmware Version: 2.01.02.00
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Well after updating firmware it still didnt work but then a couple days later the modem took a dive anyway. Verizon replaced it with a new Actiontek router and after configuring, I was able to get the VPN working.
My next suggestion would have been to replace the router with something else if possible. Either way glad to hear it's working now. Is the new router the same model as the old one or is it a different one?
Different model. Thankfully.