Strange VPN Issue

Hello,

We are trying to connect to a server via VPN. The owners of the server, for our testing purposes, has the firewall open for all IP addresses.

On our network, our firewall allows outgoing VPN on two servers. On one server (the older server, Winows Server 2003), the connection is successful. On the new server (Windows Server 2008), the connection is unsuccessful.

To troubleshoot, we tried connecting to the VPN through personal laptops using personal hotspots.

I got on my laptop and connected to my AT&T hotspot to try to do a VPN connection. The connection was successful.

I then used a Verizon hotspot to try to do the same VPN connection and the connection was not successful!

I don't know if the laptop/hotspot issue has anything to do with the server issue, but still; this is very strange/confusing!

Any thoughts? This is a pretty high-priority issue, so any help would be great.
infotechelgAsked:
Who is Participating?
 
infotechelgAuthor Commented:
Never mind, guys. Sometimes it takes a Web developer to provide an extra set of eyes for the Network Admins. The third octet of the IP address entry in the firewall was typed in incorrectly.

These things happen!

Thanks for your help and time.
0
 
sharjeel ashrafSenior Network EngineerCommented:
check the settings on the properties tab for the new VPN from the windows 2008 server, and match the encryption settings, under secuirty the default for server 2008 is requires encryption, change this to optional and see what happens.

i assume this is a windows PPTP connection
0
 
infotechelgAuthor Commented:
Thanks, not_an_expert. I tried that and still got an error, but a different error (See VPN02.jpg).

So, I took that to the network admin and it turns out GRE is already allowed (VPN03.jpg).

I've also included a screenshot of my security settings (VPN01.jpg).

Any other thoughts/ideas?
VPN01.JPG
VPN02.JPG
VPN03.jpg
0
 
infotechelgAuthor Commented:
Never mind, guys. Sometimes it takes a Web developer to provide an extra set of eyes for the Network Admin. The third octet of the IP address entry in the firewall was typed in incorrectly.

These things happen, I guess.

Thanks for your help and time.
0
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.