We are in the process of upgrading to Window 7 Professional. In the process we have discovered that when one of our remote users connects to VPN there is an issue. They can access email and file shares with no problem. However some of them cannot access the AS/400 via a telnet client like Client Access. We have figured out that the ones with the problem have IP ranges of 192.168.1.x on their end. Our AS/400 IP address is 192.168.1.7. We NAT to the inside once they connect so the VPN connection is assigned a different address. It seems that the remote computer is looking for 192.168.1.7 locally and never looking across the VPN connection. The only solution we have found so far is to either have them change the range on their end, or we can ping 192.168.1.7 as part of the telnet connection and it works. We have never had this issue with Windows XP Pro, so there must be something in Windows 7 Pro that we can change to fix it. If anyone has any suggestions, I would love to hear them.

Hi, are you running with split tunneling or without? Reason why i'm asking is that we had a similar issue and the VPN was split so we put it so that it connects to the site and forces all traffic through the vpn. then in the ISA we have we put static routes to all the DC's and DNS servers. try this https://www.isinc.com/2011/08/30/configuring-a-split-tunnel-pptp-vpn-in-windows-7/"Some people are ment to be broken! i'm not one of them, BRING THE PAIN BABY!"

Thanks for the reply. We actually are not running with split tunneling. We also have the static routes to the DCs and DNS servers. I actually think the truth is Windows 7 is working correctly and Windows XP was broken. However, users are complaining and I'm trying to find what changed in Windows 7 and how to undo it. Since pinging the AS/400 fixes it, it appears that finding that "route" fixes it. If anyone can help with this, it would be much appreciated. There must be some difference from XP to Windows 7 that we can change and not have to add a ping to a batch file.

Hi, What range do you change the end IP to? Also, please try the following actions. 1. Force all the Network traffic to go through VPN connection. 2. Turn off the Firewall. If still no go, please use Network Monitor to observe the Network Package when telnet As/400. Juke Chou TechNet Community Support