Issue closed. It was simply a matter adding a route (on the AS400) to the new gateway on the network after the firewall install. I was hoping it was something simple, that didn't require doing anything at the clients.
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...
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...
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...
The AS400 is unaware of the subnet the VPN clients are on. Does the AS400 have to have a new route added? I had assumed that it would be like all the other boxes, that the routers would take care of any addressing issues, and handle i.p. traffic going to and coming from the AS400.
What you say...
Installed the Watchguard Firebox 600. Fairly straightforward. One issue. No MUVPN clients can connect to our AS400 via the VPN client. They are using the PRMS client to access the AS400.
This behavior is consistent across platforms. Win98, Win2k, Win ME. None can connect, ping by name, or ping...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.