Clients mappings to servers are failing.

Mapping to shares on win 2003 servers are failing. Clients are getting "No
network found" message. The share can be mapped by IP.
The first server with this problem was removed from the domain and added
back which seems to have corrected the problem. The second server saw no
change to the problem when it was removed and added back to the domain.
There are no meaningful events in the logs of the servers or the clients to
provide some direction for trouble shooting the problem.
Thank you in advance.

If this is a Win 2k3 domain it sounds like you don't have DNS set up
properly.



How is your DNS setup? What server do your AD clients point to for DNS?


hth
DDS

"basenjibob" <(E-Mail Removed)> wrote in message
news:19C081D7-E0D7-4122-8AD5-(E-Mail Removed)...
> Mapping to shares on win 2003 servers are failing. Clients are getting "No
> network found" message. The share can be mapped by IP.
> The first server with this problem was removed from the domain and added
> back which seems to have corrected the problem. The second server saw no
> change to the problem when it was removed and added back to the domain.
> There are no meaningful events in the logs of the servers or the clients
> to
> provide some direction for trouble shooting the problem.
> Thank you in advance.

Hello,
basenjibob wrote:
> Mapping to shares on win 2003 servers are failing. Clients are
> getting "No network found" message. The share can be mapped by IP.
> The first server with this problem was removed from the domain and
> added back which seems to have corrected the problem. The second
> server saw no change to the problem when it was removed and added
> back to the domain. There are no meaningful events in the logs of the
> servers or the clients to provide some direction for trouble shooting
> the problem.
in addition to Dannys answer:
DNS could be an issue - where NSLOOKUP would show you, which machine answers
to DNS requests and allows to try resolution of IP address and names. Which
DNS Server is the one to which the TCP/IP settings of the server are set?
Should not point to localhost (127.0.0.1), but to the real IP address.
Did you create a Reverse Lookup Zone for each subnet?
Netbios name resolution is realized how? It's recommmended to use a WINS
server for this, to which all clients and servers are registering.
Is the network segmented or are all clients in the same IP range?
Best greetings from Germany
Olaf

Thank you both for your replies. I was waiting for our DNS administrator to
return from vacation to follow up.
The problem was resolved this AM with a correction to the static IP/WINS
info on the server. The clients get their info through DHCP and that had been
changed to reflect an upgrade to our network. The strange thing was that some
clients were having problems and others weren't.
Thanks again.

"Olaf Engelke [MVP Windows Server]" wrote:

> Hello,
> basenjibob wrote:
> > Mapping to shares on win 2003 servers are failing. Clients are
> > getting "No network found" message. The share can be mapped by IP.
> > The first server with this problem was removed from the domain and
> > added back which seems to have corrected the problem. The second
> > server saw no change to the problem when it was removed and added
> > back to the domain. There are no meaningful events in the logs of the
> > servers or the clients to provide some direction for trouble shooting
> > the problem.
> in addition to Dannys answer:
> DNS could be an issue - where NSLOOKUP would show you, which machine answers
> to DNS requests and allows to try resolution of IP address and names. Which
> DNS Server is the one to which the TCP/IP settings of the server are set?
> Should not point to localhost (127.0.0.1), but to the real IP address.
> Did you create a Reverse Lookup Zone for each subnet?
> Netbios name resolution is realized how? It's recommmended to use a WINS
> server for this, to which all clients and servers are registering.
> Is the network segmented or are all clients in the same IP range?
> Best greetings from Germany
> Olaf
>
>