This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NAT Problem again!!!!

Hi all,

I setup the DNAT/SNAT for my internal web server following the method from the ASL documents..After that I can't reach my web site from the outside, so I try to use the TCP connection tool to send request to the internal web server IP...but finally I got the following message:

10.126.0.50: inverse host lookup failed: Host name lookup failure : Connection timed out
(UNKNOWN) [10.126.0.50] 80 (http) : Connection timed out
sent 0, rcvd 0

I did put the hostname to the hosts file...it doesn't work....please help!

Gary

This thread was automatically locked due to age.

Parents

0 lanman over 23 years ago

Have you created a rule to allow port 80 to you your web server.

From | To | Service | Allow
Any | WEBSVR | HTTP | ALLOW
Cancel
Vote Up 0 Vote Down

Cancel
0 Andy_01 over 23 years ago in reply to lanman

check the default gateway on the webserver, it should be the according interface of the ASL box.
Cancel
Vote Up 0 Vote Down

Cancel
0 garylee over 23 years ago in reply to Andy_01

but sometimes I can ping the firewall and sometimes it doesn't work.....then I have to go to the firewall windows to ping back my workstation, so my workstation can ping the firewall again....? It's so strange.......is that really a problem the firewall and the Lan pluged in the same hub?
Cancel
Vote Up 0 Vote Down

Cancel
0 acsb over 23 years ago in reply to garylee

based from my scant experience, u really have to separate the firewall and other servers from using the same switch,especially with DNAT
Cancel
Vote Up 0 Vote Down

Cancel
0 garylee over 23 years ago in reply to acsb

thanks...I will try it later....
Cancel
Vote Up 0 Vote Down

Cancel
0 Andy_01 over 23 years ago in reply to garylee

check your kernel log, you might find SPOOFING in there using the hub for multible IP networks
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Andy_01 over 23 years ago in reply to garylee

check your kernel log, you might find SPOOFING in there using the hub for multible IP networks
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data