connect by name works, but not by IP

[dave64]

WE have a SBS 2003 server (server1) which crashed due to a disk
controller issue. Once fixed almost everything works fine.

A few months ago we added a server 2003 (server2) whch runs an
application. The two have worked fine together (until today).

After controller problem is fixed, clinets cannot run the app.
Message is that the computer cannot be found or no permissions to
access it. Indeed if one tries Start -> Run \\192.168.16.3 (that
address of server 2) from server 1 one gets the errors messages.
However, if you substitute the name (server2) for the address
everything works fine. Same story on any client computers as well.

I've tried running netdiag on the server2 computer and the output is
mostly clean except for it can't find the domain controller. Could
something have changed that makes server2 think server1 does not
exist ?

 

[Phillip Windell]

Re: connect by name works, but not by IP

Depends on how you "fixed" the controller problem.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"dave64" <dave@dfel.com> wrote in message
news:9cd460f8-566b-4da5-86c3-8da187bcadcc@y21g2000hsf.googlegroups.com...
> WE have a SBS 2003 server (server1) which crashed due to a disk
> controller issue. Once fixed almost everything works fine.
>
> A few months ago we added a server 2003 (server2) whch runs an
> application. The two have worked fine together (until today).
>
> After controller problem is fixed, clinets cannot run the app.
> Message is that the computer cannot be found or no permissions to
> access it. Indeed if one tries Start -> Run \\192.168.16.3 (that
> address of server 2) from server 1 one gets the errors messages.
> However, if you substitute the name (server2) for the address
> everything works fine. Same story on any client computers as well.
>
> I've tried running netdiag on the server2 computer and the output is
> mostly clean except for it can't find the domain controller. Could
> something have changed that makes server2 think server1 does not
> exist ?

 

[Meinolf Weber]

Re: connect by name works, but not by IP

Hello dave64,

Would be nice if you can stick to this posting "can't find server by address,
but can by name" created on 20:26.

If you have more problems then only pinging, please describe how you restored
the server. Seems that the second server is not recognized anymore correctly
in the domain.

Also you should post this to a SBS NG:
microsoft.public.windows.server.sbs

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> WE have a SBS 2003 server (server1) which crashed due to a disk
> controller issue. Once fixed almost everything works fine.
>
> A few months ago we added a server 2003 (server2) whch runs an
> application. The two have worked fine together (until today).
>
> After controller problem is fixed, clinets cannot run the app. Message
> is that the computer cannot be found or no permissions to access it.
> Indeed if one tries Start -> Run \\192.168.16.3 (that address of
> server 2) from server 1 one gets the errors messages. However, if you
> substitute the name (server2) for the address everything works fine.
> Same story on any client computers as well.
>
> I've tried running netdiag on the server2 computer and the output is
> mostly clean except for it can't find the domain controller. Could
> something have changed that makes server2 think server1 does not exist
> ?
>