woodjack
asked on
Windows 2003 server not working with Linksys router
I have Windows 2003 server I am trying to implement a VPN to through a Linksys WRT54GS router using VPN Pass Through. The VPN is set up to use PPTP. When I test the VPN without the router (the server is directly connected to the cable modem), I can connect to the VPN every time. When I put the router back in place, I get an "Error 678: there was no answer."
I have used Linksys tech support and they have walked me through all of the options to make passthrough work and have even administered the router remotely to configure the router themselves and they cannot figure out the problem.
The following are already in place:
PPTP is enabled
The following ports are forwarded to the VPN server in Port Forwarding:
47, 50, 500, 1723
We have also tried:
Port Triggering instead of port forwarding.
Placing the server in the DMZ
Nothing seems to work. I still have an outstanding ticket with level 2 tech support but if anyone has any suggestions I am willing to try most anything.
If it helps, I have a similar problem with a Netgear router but want to focus on the Linksys since it is critical and time sensitive. I am open to the possibility that there is a misconfiguration problem on the server but it does not seem likely since I can always connect when the router is taken out of the equation.
Thank you.
I have used Linksys tech support and they have walked me through all of the options to make passthrough work and have even administered the router remotely to configure the router themselves and they cannot figure out the problem.
The following are already in place:
PPTP is enabled
The following ports are forwarded to the VPN server in Port Forwarding:
47, 50, 500, 1723
We have also tried:
Port Triggering instead of port forwarding.
Placing the server in the DMZ
Nothing seems to work. I still have an outstanding ticket with level 2 tech support but if anyone has any suggestions I am willing to try most anything.
If it helps, I have a similar problem with a Netgear router but want to focus on the Linksys since it is critical and time sensitive. I am open to the possibility that there is a misconfiguration problem on the server but it does not seem likely since I can always connect when the router is taken out of the equation.
Thank you.
ASKER
Hi Jay,
I opened port 51 to no effect but thank you for the advice. I upgraded my firmware as a first step and have hardbooted the router several times since. I checked the port forwarding destination and it has the correct VPN IP address.
I am befuddled.
Thanks for the suggestions.
I opened port 51 to no effect but thank you for the advice. I upgraded my firmware as a first step and have hardbooted the router several times since. I checked the port forwarding destination and it has the correct VPN IP address.
I am befuddled.
Thanks for the suggestions.
hmm has me stuffed as well, ill get some additional help from a VPN guru
ASKER
Thanks Jay. I don't have a VPN resource nearby that I can tap for this. Much appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks Rob
Don't thank me yet <G>, but you are welcome.
ASKER
Thanks Jay and Rob.
I tried the above recommendation and it still does not work. I have to admit it doesn't make a lot of sense at this point. I'm back on the phone with Linksys tech support.
Jack
I tried the above recommendation and it still does not work. I have to admit it doesn't make a lot of sense at this point. I'm back on the phone with Linksys tech support.
Jack
Have you tried verifying that the appropriate port, 1723, is in fact forwarded. From the server log on to
Http://www.canyouseeme.org and test for port 1723
This will also verify the true WAN IP address that you should be connecting to from the remote location. Also make sure when you log onto the Linksys that on the status page of the router it shows that IP as being the WAN/public IP.
And, again verify PPTP pass-through is enabled on the router, though this does not usually generate a 678 error, that would be more the port forwarding or wrong WAN IP.
Another test would be to turn on remote management of the router and verify you can connect.
Http://www.canyouseeme.org and test for port 1723
This will also verify the true WAN IP address that you should be connecting to from the remote location. Also make sure when you log onto the Linksys that on the status page of the router it shows that IP as being the WAN/public IP.
And, again verify PPTP pass-through is enabled on the router, though this does not usually generate a 678 error, that would be more the port forwarding or wrong WAN IP.
Another test would be to turn on remote management of the router and verify you can connect.
ASKER
I just tried www.canyouseeme.org and it can see port 1723 on the server. The router log also shows an incoming connection to 1723. PPTP is verified as enabled. Also, I can remotely manage the router.
The public address on the router was the address that showed at www.canyouseeme.org.
Thanks.
The public address on the router was the address that showed at www.canyouseeme.org.
Thanks.
Then I am stumped. You should at least get as far as a 721 error. Any chance of trying another router?
No chance of a Windows or other firewall enabled on the machine to which you are connecting?
ASKER
Thanks Rob.
Yes, it doesn't make sense to me either.
We are on the verge of trying another router.
Thanks again.
Yes, it doesn't make sense to me either.
We are on the verge of trying another router.
Thanks again.
probably save yourself some time and frustration at least trying another router or doing a hard reset on your current one
ASKER
Gentlement. I apologize for not responding. It was not my intent to abandon.
For my resolution I started from scratch with the router. I reset to facorty defaults and upgraded the firmware again. I then changed all relevent settings as posted in this thread.
Likewise, on the server I recreated routing and remote access from scratch just to make sure everything was configured properly and the VPN now works.
I can't be sure exactly which item in the thread helped the most but the suggestion to remove any extraneous port forwarding let me to reconfiguring from scratch so I award the points to Rob.
Thanks again and sorry about the lack of response.
For my resolution I started from scratch with the router. I reset to facorty defaults and upgraded the firmware again. I then changed all relevent settings as posted in this thread.
Likewise, on the server I recreated routing and remote access from scratch just to make sure everything was configured properly and the VPN now works.
I can't be sure exactly which item in the thread helped the most but the suggestion to remove any extraneous port forwarding let me to reconfiguring from scratch so I award the points to Rob.
Thanks again and sorry about the lack of response.
Thanks woodjack, and appreciate the update.
--Rob
--Rob
51 is another port worth opening for IPSEC, are you certain you have forwarded the ports to the correct address? have you tried hardbooting your router and reoconfiguring and/or updating its firmware