can't find server by address, but can by name

[dave64]

Hi. We had an SBS 2003 server crash dues to a problem with a RAID
controller card. This is the controller for our network. Problem is
fixed. Almost everything works well.

A while ago a Windows server 2003 was added to run an appllicaton.
All has worked well with it and the network. Now, after the outage
earlier, we can see server2 in the network neighborhood just like
before. However when we try to run the app it fails saying it cannot
find the server. When the app was installed they pointed to it by
address - 192.168.16.3\somewhere.

In trying to see what is and is not working, we tried the old standby
Start -> Run \\192.168.16.3 from a couple of workstations and even
from server1. Invariably the message is that 192.168.16.3 cannot be
found or that we do not have permission. Yet if we do Start -> Run \
\server2 it works just fine. Same thing with the app, if swe change
it to use the name rather than the address, everything works fine.\

Other info. Only found 1 spot in server1 that had any issues after
repair and reboot. There was a complaint about the IPSEC service not
rnning properly and the suggestion to disable it. We did and it seems
fine now.

More other info. Two messages from Symantec Endpoint 11. One said
SNAC.EXE abended. Another messages regarding WG service not
running. Symantgec's web site shows other posts about this but no
solution. I am not sure if this even relates to our problem or not.

Any idea would be appreciated. Thanks

 

[Spaceman]

Re: can't find server by address, but can by name


"dave64" <dave@dfel.com> wrote in message
news:2c3ffdf3-e628-49d5-bb35-f6008ac15c32@d70g2000hsc.googlegroups.com...
> Hi. We had an SBS 2003 server crash dues to a problem with a RAID
> controller card. This is the controller for our network. Problem is
> fixed. Almost everything works well.
>
> A while ago a Windows server 2003 was added to run an appllicaton.
> All has worked well with it and the network. Now, after the outage
> earlier, we can see server2 in the network neighborhood just like
> before. However when we try to run the app it fails saying it cannot
> find the server. When the app was installed they pointed to it by
> address - 192.168.16.3\somewhere.
>
> In trying to see what is and is not working, we tried the old standby
> Start -> Run \\192.168.16.3 from a couple of workstations and even
> from server1. Invariably the message is that 192.168.16.3 cannot be
> found or that we do not have permission. Yet if we do Start -> Run \
> \server2 it works just fine. Same thing with the app, if swe change
> it to use the name rather than the address, everything works fine.\
>
> Other info. Only found 1 spot in server1 that had any issues after
> repair and reboot. There was a complaint about the IPSEC service not
> rnning properly and the suggestion to disable it. We did and it seems
> fine now.
>
> More other info. Two messages from Symantec Endpoint 11. One said
> SNAC.EXE abended. Another messages regarding WG service not
> running. Symantgec's web site shows other posts about this but no
> solution. I am not sure if this even relates to our problem or not.
>
> Any idea would be appreciated. Thanks

It sounds like your server IP changed.
Open a command promp and ping it by the name server2 and see what IP it
tells you.

 

[Meinolf Weber]

Re: can't find server by address, but can by name

Hello dave64,

Check your ip address of the server and also that it is correctly registered
in the DNS server zones.

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


> Hi. We had an SBS 2003 server crash dues to a problem with a RAID
> controller card. This is the controller for our network. Problem is
> fixed. Almost everything works well.
>
> A while ago a Windows server 2003 was added to run an appllicaton. All
> has worked well with it and the network. Now, after the outage
> earlier, we can see server2 in the network neighborhood just like
> before. However when we try to run the app it fails saying it cannot
> find the server. When the app was installed they pointed to it by
> address - 192.168.16.3\somewhere.
>
> In trying to see what is and is not working, we tried the old standby
> Start -> Run \\192.168.16.3 from a couple of workstations and even
> from server1. Invariably the message is that 192.168.16.3 cannot be
> found or that we do not have permission. Yet if we do Start -> Run \
> \server2 it works just fine. Same thing with the app, if swe change
> it to use the name rather than the address, everything works fine.\
>
> Other info. Only found 1 spot in server1 that had any issues after
> repair and reboot. There was a complaint about the IPSEC service not
> rnning properly and the suggestion to disable it. We did and it seems
> fine now.
>
> More other info. Two messages from Symantec Endpoint 11. One said
> SNAC.EXE abended. Another messages regarding WG service not running.
> Symantgec's web site shows other posts about this but no solution. I
> am not sure if this even relates to our problem or not.
>
> Any idea would be appreciated. Thanks
>