Have five external Fixed Ip addresses coming in on a cable connection. On address XXX.XXX.XXX.180 I have a NAT established going to internal address 192.168.1.102 using telnet as the service. That one works, an external user using the proper software (a Unix terminal emulator) can connect to his program.
I have another Linux server on that network located at IP 192.168.1.194 that also uses Telnet and a terminal emulator to execute a program on that server. I need to connect to that server from outside using telnet also. So I can't use the same IP address as the first application to NAT to a different server. So, I created a new Policy identical to the one going to 102, but except for using xxx.xxx.xx.180 I use xxx.xxx.xxx.179 and telnet as the service and go to 192.168.1.194. Looking at my configuration dialog My Source is ANY, Destination is the 179 external IP. The service is TELNET, The firewall setting is Pass, The NAT action is from External Ip 179 to 192.168.1.194. This Policy is the fourth in the policy list so no previous policies interfere with it they are set at the standard default settings, the other policy that NATS to 102 is lower in the list. Yet when I try to telnet from outside it will not connect to the server. I can telnet from a workstation inside the network and it connects to the server OK. I checked the hardware from another computer on the network I can ping the server and the gateway. But I can't ping 179 from outside. I checked with the internet provider they say everything Ok at their end. I think the fact that I can't ping some of the virtual addresses has something to do with my problem but I can't figure out why or how to fix it. Can anyone give me a reason why this would occur and ides on how to fix this problem. I'm at my wits end. Any help would be greatly appreciated.
Bob
I have another Linux server on that network located at IP 192.168.1.194 that also uses Telnet and a terminal emulator to execute a program on that server. I need to connect to that server from outside using telnet also. So I can't use the same IP address as the first application to NAT to a different server. So, I created a new Policy identical to the one going to 102, but except for using xxx.xxx.xx.180 I use xxx.xxx.xxx.179 and telnet as the service and go to 192.168.1.194. Looking at my configuration dialog My Source is ANY, Destination is the 179 external IP. The service is TELNET, The firewall setting is Pass, The NAT action is from External Ip 179 to 192.168.1.194. This Policy is the fourth in the policy list so no previous policies interfere with it they are set at the standard default settings, the other policy that NATS to 102 is lower in the list. Yet when I try to telnet from outside it will not connect to the server. I can telnet from a workstation inside the network and it connects to the server OK. I checked the hardware from another computer on the network I can ping the server and the gateway. But I can't ping 179 from outside. I checked with the internet provider they say everything Ok at their end. I think the fact that I can't ping some of the virtual addresses has something to do with my problem but I can't figure out why or how to fix it. Can anyone give me a reason why this would occur and ides on how to fix this problem. I'm at my wits end. Any help would be greatly appreciated.
Bob