I have the following issue regarding NAT. I have a client with a Cisco 1700 router. On this router there's a NAT pool 10.210.2.20 - 120/24. That's 100 WAN addresses being NAT'ed. The FE has an address of 192.168.0.200. The rest of the pc's and devices have ip's of 192.168.0.100.
The problem I am having is that the LAN at this specific site works fine when the users connect with their pc's to the mainframe in another city, many miles away. But when they request a printjob from the mainframe, they do not get the printjob. The mainframe ip is 184.108.40.206. The printer LAN ip is 192.168.0.110 which gets nat'ed to 10.210.2.39 when WAN devices need to communicate.
I also have to mention that this client's router is connected to a bigger router routerforcustomers, which has many other customer routers connecting to it.
I have enquired from the mainframe engineers and they say the print queue for the above printer show a lot of jobs pending, so the printer gets the requests. I then proceeded to ask the one mainframe engineer to trace from the mainframe to the printer ip to see what happens. The trace indicates that it times out on the routerforcustomers router. Yet when I ask the routerforcustomers router where it is routing the 10.210.2.39 ip it shows there is a static route for it down S0/2.10 which is the serial for this specific customer. So why can the router not pass things on to the customer router in order to get the printer to print the jobs? There are no access lists on any of the 2 routers mentioned to block things?