In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
VPN client through SG 203 firewall to windows server
Hi,
We currently have a sonicwall firewall on our network which is forwarding PPTP (port 1723) requests to a local Windows 2000 Remote Access server. This is allowing clients to create a VPN connection through the firewall to the server. This appears to be the only rule on the firewall relating to VPN's.
We are trying to swap this firewall with an Avaya SG 203 firewall - I have replaced the sonicwall and set the 203 up in exactly the same way (same ip addresses, port forwarding rules etc). However when I try to connect a VPN client, it gets as far as verifying username and password and then fails with error 628 (the client is windows 98).
Any idea what I'm doing wrong?
Thanks in advance,
Edd
We currently have a sonicwall firewall on our network which is forwarding PPTP (port 1723) requests to a local Windows 2000 Remote Access server. This is allowing clients to create a VPN connection through the firewall to the server. This appears to be the only rule on the firewall relating to VPN's.
We are trying to swap this firewall with an Avaya SG 203 firewall - I have replaced the sonicwall and set the 203 up in exactly the same way (same ip addresses, port forwarding rules etc). However when I try to connect a VPN client, it gets as far as verifying username and password and then fails with error 628 (the client is windows 98).
Any idea what I'm doing wrong?
Thanks in advance,
Edd
Who is Participating?
I just changed from a PIX to a SGS Firwall. In addition to the port forward, on the new firewall I also needed a rule to let it in and a rule to let it back out.
Hmm....I have setup firewall rules to allow pptp in and out, and I've tried turning the firewall security off entirely - still no joy.
If your firewall security is fully off you may have another issue. I would reverify that the VPN works fine internally. As long as it's good inside, it's back to the firewall.
OK, With my small VPN/Firewall appliances, all I do is the port forwarding. With the SGS I had to do the Port Forward, Rule in and out as well as setup a NAT pool. I thought the NAT pool was a little weird, but that's what the SGS required. Also make sure your port is TCP and not UDP. Oh, one more thing, you may have to enable GRE which is TCP Protocol 47. I had to do that on my SGS.
Here is a link to the Port 47 Issue. I would try this first before fooling with NAT pools, etc.
http://support.microsoft.com/?id=241251
OK, With my small VPN/Firewall appliances, all I do is the port forwarding. With the SGS I had to do the Port Forward, Rule in and out as well as setup a NAT pool. I thought the NAT pool was a little weird, but that's what the SGS required. Also make sure your port is TCP and not UDP. Oh, one more thing, you may have to enable GRE which is TCP Protocol 47. I had to do that on my SGS.
Here is a link to the Port 47 Issue. I would try this first before fooling with NAT pools, etc.
http://support.microsoft.com/?id=241251
Ok, I have finally found where to enable custom protocols and have enable GRE and added it to the rules, but still am not getting anywhere.
I can't see any options for NAT pools - what are they for?
I can't see any options for NAT pools - what are they for?
Oh and the VPN works fine with the old firewall, so I'm assuming the problem is not with the VPN server/client.
Hey,
Sorry, had forgotten all about this. The points are yours. The problem still isn't fixed sadly - any tips on NAT pools?
Ta,
Edd
Sorry, had forgotten all about this. The points are yours. The problem still isn't fixed sadly - any tips on NAT pools?
Ta,
Edd
Thank you, I appreciate that.
With my SGS, I had to create the rule and do port forwarding. I also had to setup a NAT pool to make it work. The pool would not work on the physical IP address of the firewall, so I had to assign it another address. For example, the interface might be 12.108.43.10. I had to assign the VPN Nat Pool .11 and direct all my vpn traffic to that address to make it work.
With the Watchguard, everything is the same, but they use a one to one NAT only for the PPTP. So, I still had to create the rule and do the forwarding, assign a different IP address than the physical one and direct the VPN traffic to that IP. The only difference is the Watchguard has you setup a one to one NAT for the PPTP to use.
Have you looked at the manufacturer's web site or called them about the PPTP?
With my SGS, I had to create the rule and do port forwarding. I also had to setup a NAT pool to make it work. The pool would not work on the physical IP address of the firewall, so I had to assign it another address. For example, the interface might be 12.108.43.10. I had to assign the VPN Nat Pool .11 and direct all my vpn traffic to that address to make it work.
With the Watchguard, everything is the same, but they use a one to one NAT only for the PPTP. So, I still had to create the rule and do the forwarding, assign a different IP address than the physical one and direct the VPN traffic to that IP. The only difference is the Watchguard has you setup a one to one NAT for the PPTP to use.
Have you looked at the manufacturer's web site or called them about the PPTP?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month9 days, 22 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
I have done this same thing with both SGS and Watchguard firewalls and am sure that is issue is in a NAT pool or one-to-one NAT for his issue. I'll ask for the points as I presented good, logical troublehsooting with some of the suggestions he did use. As for the rest, we might not know or it may have fixed his issue.