connection to AS400 via VPN no-go

[rlehto]

Is it possible that our clients are unable to connect to our (single) AS400 when coming in on a VPN because they are using a different range of i.p. addresses than our internal clients use? Our VPN clients can get into everything else on the network, except the AS400. They cannot ping it by name or number.

I'm not familiar at all with AS400 networking, all I do is start and stop jobs on it.

Our internal clients use 172.x.x.x, the VPN clients use 10.x.x.x once they are inside the firewall. No problem with anything else, like I said, just the AS400.

 

[rlehto]

Here is Watchguards response. Not the answer I wanted. Not "you are stupid, set it up like this", the answer is "yeah, that happens a lot, let us know if you fix it..."

Here is response...

"We have been looking into this issue, which appears to be very common with AS/400's and VPN clients.

The best fix we have found so far involves setting the MTU on the remote client's network adapter to a higher number. We strongly suggest you use a value of 1350.

You can find the tool to change your MTU here:

http://www.dslreports.com/front/DRTCP019.exe

Please ONLY change the field labeled "MTU" next to your network adapter, as other changes could dramatically affect your network and introduce many variables into the task at hand.

Let me know if this resolves the issue or if you need further assistance."

 

[flapeyre]

I connect from home using a VPN (Cisco). But my client software is ViewNow. Client Access is a chore to set up properly, and we use it only when we have to.


"When once you have tasted flight, you will forever walk the Earth with your eyes turned skyward, for here you have been, and there you will always long to return."

--Leonardo da Vinci