RE: [SLUG] Strange connectivity situation

From: Stephen Ames (sames@managedwebservices.com)
Date: Thu May 27 2004 - 22:12:03 EDT


How are you handling name resolution on the inside? Can you ping the server
from the inside by either IP or hostname? If I understand your config, you
are probably using port forwarding on the outside so the router knows where
to direct your requests from the outside, but depending on your config,
devices may not have proper internal name resolution. Another test would be
to try to telnet locally at the server to itself using the two ports. Ex.
Telnet 192.168.0.3 25 to see if the server is answering on 25.

Thanks,

Steve

-----Original Message-----
From: slug@nks.net [mailto:slug@nks.net] On Behalf Of Steven Buehler
Sent: Thursday, May 27, 2004 9:15 PM
To: slug@nks.net
Subject: [SLUG] Strange connectivity situation

I have a rather strange connectivity issue going on.

First off, from the cable modem (RoadRunner) i have a VoIP telephone
adapter connected, using address 192.168.15.1, then a Netgear router at
192.168.15.2, which does NAT to a desktop and laptop (192.168.0.2 and .3,
respectively). .3 is a server running mail and web service.

Here's the strange problem. I can go in from outside and reach ports 25
and 80 just fine. However, if I attempt from my desktop or laptop to
telnet to the server ports using the hostname or 24.x.x.x address, the
connection either times out or is flat-out refused.

Any ideas?

SWB

-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages posted
are those of the author and do not necessarily reflect the official policy
or position of NKS or any of its employees.

-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:08:17 EDT