Link to home
Start Free TrialLog in
Avatar of TX_SCUBA
TX_SCUBAFlag for United States of America

asked on

NetBios and DNS Names NOT Resolving on Full Windows Network

I have a network that experiencing hardware issues last week.  We believe it was a switch but are still piecing together what part of the LAN was affected.  All connections have been restored and all machines can PING each other by IP but NONE of them can resolve a NetBios or DNS name.

I show DNS UP and running with out errors.  I have reviewed the event log and found that all the Services have not had any recorded entries since the problem started 2/3/12.  My network is not that clean...

While sitting on the server or client machine they can resolve themselves, but right now we are only operational because of IP to MAC.

address is: http://helpdesk.mycompany.com:nnnn
IP Address: nn.nn.nnn.nnn.nnnn
Avatar of Voodoocrazy
Voodoocrazy

That sounds fun.

How many servers do you have?

Can the servers resolve DNS

Are the computes with issues connected to the same subnet as the servers?

Are the client computers getting the DNS server address from DHCP?
Avatar of TX_SCUBA

ASKER

One Sever.  I know bad, bad admin

Sever can resolve via nslookup as well as the clients

I have four subnets and none can ping.  therre are VPN but the one that is LAN is on the same subnet as the server

All the computers are static.

The only thing that I believe has changed is a different but same model of router was installed.  DHCP is disabled on it.  

I have forwarding turned on on the the server's DNS.  All clients go to the server; then if the record doe not exist the server send the request to the public DNS server.  No issues contacting FQDN outside the network.

On other important point I think., the client receive the DNS info then show request timed out. Like the other end wont respond or the response is being blocked.

WireShark shows the ARP but no Reply from the client.
So the client computers have the servers IP address as the DNS server statically assigned?

I would take one client on the LAN and configure the dns with only your servers LAN Ip address  in the primary DNS server.  
As your using a lan with the same subnet as your server, your router isnt going to be the problem unless its handing out the incorrect DNS address via DHCP.
Sorry for the omission, the clients have two addresses for their DNS.  the primary is the server and the secondary is the ISP's  The router is set to only route.

Also I cannot hit a FQDN from outside.
SOLUTION
Avatar of Voodoocrazy
Voodoocrazy

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This is what worked