TCP/IP Name Resolution Issues

[Steven]

Mark

Your ISP has your reverse lookup entry incorrect. If you PING
ziggy.spotsystem.com you get your ip address 204.94.143.32, but if you PING
-a 204.94.143.32 you get mark.spotsystem.com.

Ask you ISP to check it out DNS server NS1.MOBIUS.NET. The reverse lookup
entry on your DNS server is correct.

Good Luck
Gary and Steven

Mark Schoenbaum <ma...@spotsystems.com> wrote in article
<01bc8675$9e0f26e0$208f5ecc@ziggy>...
>
> We have a direct ISDN connection to our ISP and everything seems to be
> working fine including the ability of our MS Exchange server to recieve
and
> transmit mail. We are having a problem, though, trying to access our
ISP's
> mail server directly from any NT40 workstation. In tracking the problem
> with our ISP, we have determined that the host name in the TCP/IP header
is
> incorrect and cannot be reverse then forward resolved properly. My host
> name is ziggy.spotsystems.com, but my ISP reports that the telnet request
> indicates that I am mark.spotsystems.com (my user name rather than my
host
> name). Since we run our own authoratative DNS (without DCHP or WINS)
only
> my host name is resolved. The only time I see any identification by my
> user name is when I run "nbtstat -n" which shows that "mark" is in my
> NetBios local cache for messager services. Does anyone have any ideas
how
> I go about fixing this problem?
>
> Mark Schoenbaum
> Director of Systems Development
> Spot Systems, Inc.
>
>