Accessibility from one server to another using DNS suddenly gets stopped

Greetings!!!

I have two Windows 2008R2 server Server A access Server B with the name netbios name.  But suddenly it stops access server B wihtout any error.  But you can still ping with the IP address.

I could not find any reason why this does like this.  But if I disable the network card and enable the network card, it starts working and this is a quick fix.

However, I need to find out the cause of this.
elawAsked:
Who is Participating?
 
Krzysztof PytkoConnect With a Mentor Senior Active Directory EngineerCommented:
I would not believe it is secure channel. As you said, when you disable and enable NIC on a server everything starts working fine, so that's not the issue with secure channel as this cannot solve problem by re-enabling NIC.

I would suggest to update NIC drivers to the newest possible. Maybe something wrong with drivers. Please check on server manufacturer page if there is known error for that or drivers update is available

Regards,
Krzysztof
0
 
GanparCommented:
Your Secure channel might have broken...

You can check it by nltest /Server:[TargetServer Name] /SC_Query
http://support.microsoft.com/kb/158148
0
 
elawAuthor Commented:
what is the example if we have two servers
Server A
Server B
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
elawAuthor Commented:
I have found the example and i have run the command.  the command was successfule because there is no issue at the moment.
I will re run the command when I come accross the same issue.

so as you think that the it could be the problem if the secure channel is broken and this nltest shows as well.  Then what is the resolution to fix the problem.
0
 
elawAuthor Commented:
I just want to understand this problem.  
I still can ping the target server with the IP address.  But I am unable to ping the target server with the netbios name.  But when disable and enable the network card on the source machine then it is able to ping the target the server with the netbios name.
0
 
GanparCommented:
If you find any issue with SC then please reset it
Use following code

Nltest /Server:[TargetServer Name] /SC_RESET:<DomainName>
0
 
elawAuthor Commented:
well this is a hyper-V virtual machine
0
 
GanparCommented:
As Krzysztof said please verify u r NIC driver and update us.......
0
 
elawAuthor Commented:
Krzysztof I agree with you.  but I need to know what is the issue.  I will appreciate if someone can help me.
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
One more think, please ensure of the latest integration Hyper-V  features are installed on virtual machine.

Additionally please check event logs on Hyper-V and that "faulty" machine to check if there are no any hints for that

Krzysztof
0
 
Satish AutiSenior System AdministratorCommented:
Are you getting any events related to DNS from where we can find the roor cause. There is something causing your DNS

there is another simplest way to resolve this issue instead of disableing & renabling NIC card... Just restart the servives.

You can type this in cmd in single go...

net stop dns & net stop netlogon & nbtstat -RR & nbtstat -R & ipconfig /flushdns & net start dns & net start netlogon & ipconfig /registerdns  & net stop w32time & net start w32time & w32tm /resync /rediscover & net stop ntfrs & net start ntfrs & repadmin /syncall /AeD &  gpupdate /force
0
 
elawAuthor Commented:
Thanks auti for this commands.

but I need to resolve this issue that it should not happen again
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
And one more thing, what king of virtual network configuration are you using on a guest machine (external, internal etc.)?

Krzysztof
0
 
elawAuthor Commented:
This is running on Hyper-V and this is internal for the Hyper-V
0
 
Satish AutiSenior System AdministratorCommented:
Hello elaw,

Can you give us some event IDs if there are any in your server related to DNS.
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
OK, so this is allowing only communication between servers themselves no access out of box. Is there DNS server also running on that Hyper-V server ?

Can you check what will happen if you change NICs from internal to external ? Maybe then the issue will disappear?

Krzysztof
0
 
Neil RussellTechnical Development LeadCommented:
Do the servers have STATIC DNS Entries or are you relying on the server registering itself in DNS?

Disabling and reenabling the NIC Will force it to register its IP With the DNS Server.
Servers should really have stativ DNS A Records added by hand, if you have not.

This MIGHT be your problem.
0
 
elawAuthor Commented:
Yes, Neilsr, you are right there is a Static DNS entry.

What could be the issues please let me know.
0
 
asavenerCommented:
Can you try using the fully-qualified name and see if the problem recurs?

When using just the netbios name, the network may be relying on broadcasts to resolve name to the IP address.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.