DNS issue??

  • Thread starter Thread starter Rob
  • Start date Start date
R

Rob

Hello, I am having some challenges with a server that is
a domain controller and a DNS. Ping and NSLOOKUP return
the proper values when queried(i.e. I ping "thatserver"
and it returns IP 172.1.2.3. When I use nslookup on
172.1.2.3 "thatserver" is returned). When I map using
the IP (net use * \\172.1.2.3\c$) I am amble to map the
drives, but when I try to map by name (net use *
\\thatserver\c$), "The specified network name is no
longer available" is returned. This is only for servers
that are not on the local sub net. Servers on the local
subnet can be mapped by name. Also, other servers on the
same subnet as the server with the problem are function
correctly. Any ideas?? Thanks!
 
Rob said:
Hello, I am having some challenges with a server that is
a domain controller and a DNS. Ping and NSLOOKUP return
the proper values when queried(i.e. I ping "thatserver"
and it returns IP 172.1.2.3. When I use nslookup on
172.1.2.3 "thatserver" is returned). When I map using
the IP (net use * \\172.1.2.3\c$) I am amble to map the
drives, but when I try to map by name (net use *
\\thatserver\c$),
Click to expand...

You don't say what OS is the "client" -- some older clients
would use a NetBIOS lookup for that \\thatserver since it is
SHORTER than 16 characters and no dot this would even
happen for NT4 (Not sure which one Win2000 would try first
but I believe it is the DNS resolver.)

Are you also using:

nslookup thatserver

OR

nslookup thatserver.somedomain.com
"The specified network name is no
longer available" is returned. This is only for servers
that are not on the local sub net. Servers on the local
subnet can be mapped by name.
Click to expand...

That confirms NetBIOS is working -- it's resolving local
(same subnet) by broadcasts problably.
Also, other servers on the
same subnet as the server with the problem are function
correctly. Any ideas?? Thanks!
Click to expand...

Sounds like you have a DNS problem:

DNS
1) Dynamic for the zone supporting AD
2) All internal DNS client NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2

Restart NetLogon on any DC if you change any of the above that
affects a DC.

Pretty much the same thing applies to NetBIOS with WINS servers.
You really need the WINS Server(s) too if you have Windows +
IP + multiple subnets.

Browsing (and other things) are based on NetBIOS.
 
In
Rob said:
Hello, I am having some challenges with a server that is
a domain controller and a DNS. Ping and NSLOOKUP return
the proper values when queried(i.e. I ping "thatserver"
and it returns IP 172.1.2.3. When I use nslookup on
172.1.2.3 "thatserver" is returned). When I map using
the IP (net use * \\172.1.2.3\c$) I am amble to map the
drives, but when I try to map by name (net use *
\\thatserver\c$), "The specified network name is no
longer available" is returned. This is only for servers
that are not on the local sub net. Servers on the local
subnet can be mapped by name. Also, other servers on the
same subnet as the server with the problem are function
correctly. Any ideas?? Thanks!
Click to expand...

If only on servers on a different subnet, then based on the resolver method,
it apparently is treating it as a NetBIOS name, so therefore, WINS would be
required for this to work. YOu can test this by finding the machine in the
neighborhood and try clicking on it, if you get the same message, then WINS
is your answer.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top