Tom Collins said: > On Nov 11, 2004, at 9:41 AM, Matthew Walker wrote: >> Now... Remote Test: >> >> arsenic ~ # telnet mail.thebraingarden.com 25 >> Trying 209.90.91.5... >> Connected to user-5.pl107658.fiber.net. >> Escape character is '^]'. >> 220 ***************************** > > Can you watch the network with a packet sniffer like Ethereal? You > said that 209.90.91.5 is actually port forwarded to your server. It > looks like it's not transparent -- like there's a proxy of some sort > running on 209.90.91.5. > > Is it possible to connect directly to the Ethernet interface of the > server without going through any firewalls? >
Yes, it is. It's also accessible from the 10.* private network that's used at work... Here, let me make a little diagram... Internet (209.90.91.5) <=> Server (192.168.1.19) <=> Internal (10.*) There's NAT of some kind going on at both boundaries. I'm attempting to find someone who knows, but I haven't found anyone yet. Regardless, the only problem is with the Internet <=> Server interface. Clients on the Internal network have no problems. -- Matthew Walker Kydance Hosting & Consulting http://www.kydance.net
