NAT over INA

[fonedude]

I am having a problem with my NAT. I recently had to reprogram the INA because the customer wet from 128K to 256K. Since I couldn't get the programming out for the W20, I had to initialize it and start from scratch. I was able to get my internet access but, my NAT won't work. I programmed:
add map remote1
set inmap remote1 1 stupm xxx.xxx.xxx.xxx:3389 192.168.0.1:3389 (x = private IP address given to me by ISP, 192.168.0.1 = server, 3389 = port for pc anywhere)
then,
set w20 inmap remote1
reset w20
reset nat
When I do a show w20 I see the Remote1 in the IN map area.
When I do a show map server it says staticudpport with the numbers I entered above When I trace I get stuck at my ISPs router address.

 

[commguy]

you might want to ask your isp to see if they are blocking that port...???

 

[fonedude]

No they are not blocking that port, I asked. But, something that is odd is, if try to ping the internal router address from the server, which is 192.168.0.254, I don't get a response. And I don't have internet access at the server or the mirror server. I have rebooted the server. If I do an ipconfig on the router I get the right ip address and netmask and gateway. The only thing that I can think of is that the hub is managed in some way.

 

[Pepperz]

Try bypassing the hub and going directly to the server and then pinging. TipHelp@charter.net

 

[fonedude]

I was out there today. This is wild. From the server and the mirror I cannot ping the router. Furthermore, the clients are using dhcp. And they use the DNS from the server. The clients cannot ping the server or the mirror. So if I am at a client and try to ping yahoo.com, it times out. It seems that I cannot ping addresses 192.168.0.1 and 192.168.0.2 only. Tomorrow I am planning to initialize the router and put in some basic routing to a Linksys down the line. I can't continue like this. This is why I really don't like Avaya product. Nothing should be this hard!