Server 2008 R2 VPN Setup
Hi all, I am setting up a VPN using Server 2008 R2. I've sifted through many online docs and walk throughs even from this forum and nothing seems to get me pointing in the correct direction. When I try to enable remote access service I get a warning. Remote Access Service is unable to enable Routing and Remote Access for the probable reason like: unable to open ports for Routing and Remote in Windows Firewall service. In this case RAS may not accept vpn connections. "I have looked in windows firewall and have enabled all remote services" The server is on a workgroup only, no DC or Authentication. We will be sharing files and such over 2 offices eventually. Our configuration: 10.148.110.16 = modem 128.0.0.1 = router what is my ISP reports 99.253.202.52 server ip 128.0.0.105 and port is forwarded 1723 do i need to put it in the routers DMZ? When I try to connect internally to the vpn using 99.253.202.52, I get to verifying username and password i get error 721 when I use 128.0.0.1 i get error 52. I'm a Release Engineer not a IT Specialist. I have some network knowledge. Any help is appreciated. I know it will work.
July 20th, 2010 8:30pm

When I switch to 128.0.0.105 in connection settings of my client, and test internally, I connect with no issues.
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2010 8:48pm

Hi, Thank you for your post here. Before we go further, could you please tell more about your network topology? internet | | | (99.253.202.XX) Modem | (10.148.110.16) | | | | (10.XX.XX.XX) ? Router | (128.0.0.1) | | | Server (128.0.0.105) Do I understand your network topology right? 1. First of all, I would like to know whether you set 128.XX.XX.XX as your internal private network. Please understand that 128.X.X.X is not a valid private IPv4 subnet and it is public subnet. What will happen if you migrate your internal network to IPv4 private subnet such as 192.168.X.X/32?
July 21st, 2010 12:27pm

Thank you for the reply. Yes you have it correct. The network was setup as 128.x.x.x a number of years ago. I can easily migrate to the typical 192.168.x.x. This is a print shop, I would just need to assign new IP's to the devices. It won't work with the current configuration? When I try from a remote location, I get the verifying login/password, but it fails. I can login to the server over vpn internally. Thanks
Free Windows Admin Tool Kit Click here and download it now
July 21st, 2010 3:46pm

Hi all, I am the original poster for this one. I've solved this issue. It was a router/port issue. Without changing anything on the server side I can connect from the remote office to main office. Thanks Everyone
July 21st, 2010 7:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics