Re: TCP/IP Connectivity Issue on V4R5

You don't say how you are doing the tunnel? If it is a hardware vpn
tunnel, done like with routers then you really don't have to make any
entries on the as/400 except one.

I have connected remote printers in california and indiana to a v4r4
box and the vpn tunnels are handled by some netgear routers, at the
as/400 it is a 192.168.1.x, at california it is 192.168.2.x and the
other is 192.168.3.x

But the one entry you have to make and without it, it won't work is:

*DFTROUTE subnet: *NONE next hop: 192.168.1.1 (my router) pref
int: *none

You see say the printer is configured at 192.168.2.222, the above tells
it to route it to the router which part of the vpn tunnel policy will
know to send it down the line and vice versa.

I happen to use IO brand print servers on these printers I have but
should not matter.

Without the above statement, things within the network will work fine,
but outside the local lan, nope. The above is the ONLY routing
statement I have.

c
René H. Hartman wrote:
Definitely looks like a routing issue. Why would you have a separate
route to the remote LAN if you're using the default route's next hop
anyway?
You have to bear in mind that the PC's on the remote LAN originate their
traffic, haveng the AS/400 send the ack, while printer traffic is
originated from the AS/400.
Try pinging a Windows box's address. Chances are you can't. If it works,
you should find out the difference between the definitions of the
Windows boxes and the printers.

--
Best regards,

René H. Hartman
www.hac-maarssen.nl


"David Gresham" <gresham@xxxxxxxxx> schreef in bericht
news:e77v78$mmc$1@xxxxxxxxxxxxxxxxxxxx
Have an AS/400 E Series machine Model 720 running V4R5.
We have a VPN tunnel between two locations. The local
network where the AS/400 is 192.168.130.x/24. The
remote network is 192.168.5.0/24.

the IP of the AS/400 is 192.168.130.1 and currently the
route table shows a default route of 192.168.130.2 and
has a route for the 192.168.5.0/255.255.255.0 network
with a next hope of 192.168.130.2.



Users from the remote site can log-in to the box.
However, they are unable to print jobs to printers on
their subnet.



Using netstat I see the connections that are being made.
However, If I try to ping the ip address of one of these I
get no reply.

If I go to a Windows XP machine that is on the 192.168.130.x
network and ping this address I get a reply. I am also able
able to connect to any device on the remote network(192.168.5.x).

I do not see any port restrictions on the AS/400. I am
new to the AS/400 world, however I do have a good understanding
of TCP/IP.



Dave

.

Relevant Pages

  • Re: A question about Checkpoint firewall and Telnet over VPN
    ... I have been trying different options to resolve an issue with a remote ... I have the tunnel up and working. ... Since I am using Shiva VPN devices, I have tried using their Shiva ... VPN connection via an ADSL connection that connected to the company LAN ...
    (comp.security.firewalls)
  • Re: A question about Checkpoint firewall and Telnet over VPN
    ... I have been trying different options to resolve an issue with a remote ... I have the tunnel up and working. ... Since I am using Shiva VPN devices, I have tried using their Shiva ... The only problem is with the telnet session from that remote site ...
    (comp.security.firewalls)
  • Re: Branch Office Setup
    ... My original plan was to use the T/S through the VPN but I assume you are ... remote users to access their 'virtual' desktops. ... to a local printer at the remote office. ... Use the Site-Site VPN to map printers from the Terminal Server/SBS ...
    (microsoft.public.windows.server.sbs)
  • Connecting Remote Site and ISA
    ... I'd like to get some advise on setting up a 24 hour VPN ... Linux server to access the databases for item maintenance. ... We currently have the need to connect a remote office to ... VPN tunnel, since the workstation will be getting DHCP ...
    (microsoft.public.backoffice.smallbiz2000)
  • A question about Checkpoint firewall and Telnet over VPN
    ... I have been trying different options to resolve an issue with a remote ... I have the tunnel up and working. ... Since I am using Shiva VPN devices, I have tried using their Shiva ... The only problem is with the telnet session from that remote site ...
    (comp.security.firewalls)