Support Requests item #537567, was opened at 2002-03-31 17:34 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=203152&aid=537567&group_id=3152
Category: Configuration: Other Group: aolserver3_2 Status: Open Resolution: None Priority: 5 Submitted By: Harry Neuwirth (hneuwirth) Assigned to: Nobody/Anonymous (nobody) Summary: Problems with NAT? Initial Comment: Pardon this really thickheaded question: I am running win2k. I am trying to host from behind a firewall. The router is correctly translating my WAN IP (64.133.111.226) to 192.168.1.3 and open to port 80. (I know this because I can run apache without any problems). The WAN IP is actually known to internet dns as healthgap.net Here is the problem: I can set host to localhost and address to 127.0.0.1 and aolserver runs just fine. If I set host to healthgap.net and address to 64.133.111.226 nssock generates "failed to listen... win32 error code 0 If I set host to healthgap.net and address to 192.168.1.3 I can see the web page just fine on anonymizer.com, but not by entering either the name or ip address directly into my browser. Any suggestions would be appreciated. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-31 22:53 Message: Logged In: NO I was able to connect to healthgap.net, port 80, and it reported AOLServer + ad10, so I'm thinking it's working. I would guess it's a routing problem on your end. Which is to say, the outside world can access your website, but your pc/network/router/something is having a problem. What do you experience when you try to contact healthgap.net? * hangs for a long time, forever * comes back immediately with a message about not being able to reach the host * comes back with "no route to host" * something else? Does anything show up in the access.log or server.log when you try to connect? You should try to connect to port 80 with telnet or some similar tool. I would think you're more likely to get an informative/standard error response than with internet exporer, which is, more likely than not, going to give you an uninformative error page about not being able to access the host. If you have access to a tool like "traceroute", you should try that, both on healthgap.net, and the *external* ip address. Hmm. Just tried that myself, it hangs for me at 63.169.238.200. You aren't block *all* icmp are you? There are some kinds you can/should block, but there are kinds you should not. Look at this site (http://www.faqs.org/faqs/computer-security/most-common-qs/section-18.html) for guidance, or do a web search. Hope that helps ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=203152&aid=537567&group_id=3152
