Wink2 RAS and Linksys BEFSR41

[Chris]

I spent about the last 2 hrs searching through all the posts on this
subject, but didn't find any information that enabled me to solve my
problem, here it goes.

1. On my Win2k Server SP4 I have installed the RAS server, not the
VPN. I'm using 1 NIC.
2. My BEFSR41 is set with Port 1723 forwarded to the server's ip
address. PPTP, IPSec, and Multicast pass thrus are enabled and Block
WAN request is disabled. It also has the latest 1.45.7 firmware.
3. I can make a VPN connection over the local ethernet without
issues.
4. When I attempt to make a connection from outside, it hangs at the
"verifying user name" and terminates with an error 721.
5. Adding the server to the DMZ settings has no effect.

Any suggestions?

Many thanks,
Chris

 

[Chris]

I should add that I downgraded to 1.44.2 with no effect and that a pttpping fails.

Chris

 

[Freedom]

You have your BEFSR41 setup correctly. You may wish to try enabling both
TCP and UDP for 1723, but I doubt that's the problem.

I've experienced this problem before when a DSL or Cable modem did not
support Protocol 47 (GRE), aka "PPTP Pass-Through". If a modem or router at
either end of the connection is interfering, that could be your problem.

Hope that helps!
-- Freedom


I spent about the last 2 hrs searching through all the posts on this
subject, but didn't find any information that enabled me to solve my
problem, here it goes.

1. On my Win2k Server SP4 I have installed the RAS server, not the
VPN. I'm using 1 NIC.
2. My BEFSR41 is set with Port 1723 forwarded to the server's ip
address. PPTP, IPSec, and Multicast pass thrus are enabled and Block
WAN request is disabled. It also has the latest 1.45.7 firmware.
3. I can make a VPN connection over the local ethernet without
issues.
4. When I attempt to make a connection from outside, it hangs at the
"verifying user name" and terminates with an error 721.
5. Adding the server to the DMZ settings has no effect.

Any suggestions?

Many thanks,
Chris

 

[Chris]

1 problem solved.

Before I began this endeavor I called the LAN person at the client who
was trying to request. I made sure the subnets were not the same,
firewall would allow the right traffic, etc. I also requested the LAN
configuration not change during the vpn troubleshooting window. A
call to the client today and talking with another LAN person informed
me:
1. They changed their subnet to be the same as the one I was using.
2. They changed their firewall rules to block the nessecary traffic.
Both of these things occurred as I was troubleshooting the vpn
connection.

Argh!!!

Now they can succesfully connect, but can't ping or otherwise see the
network. Back to doing my research.

Thanks for the help,
Chris

 

[Bill Grant]

If the IP subnets are the same on both sides of the link, there is no
way you will get anything across it.

For example, if a site using 192.168.1.0/24 tries to send a packet to
say 192.168.1.56 , tcp/ip will decide it is local and send it to the local
LAN using hardware addressing. It will not go to a router.