Print

Print


I had a problem that sounds similar a few weeks ago that I resolved by first
removing the machine from the domain to a local workgroup, then dropping the
machine name from the domain and then re-adding the server back again as its
original name.  In my case, the problem was caused by the domain seeing two
separate SID's for a machine with the same domain name.  Even after the test
server was removed, the initial server was apparently in some diminished
capacity mode in which it could access the network but could not connect to
any shares and user could not connect to it.

 

  _____  

From: Scott Cassaday [mailto:[log in to unmask]] 
Sent: Wednesday, October 17, 2007 11:37 AM
To: [log in to unmask]
Subject: Re: [MSUNAG] Wierd issue with IMC domain

 

DNS and netbios are both the same

nothing in the event logs.

This whole thing started as they are not able to map network drives to some
server... odd thing is they seem to have a "little" connection to the
domain, enough to authenticate as users, but not to map drives over on other
servers.

----- Original Message ----- 

From: Duynslager, Lee <mailto:[log in to unmask]>  

To: Scott Cassaday <mailto:[log in to unmask]>  

Sent: Wednesday, October 17, 2007 11:33 AM

Subject: RE: [MSUNAG] Wierd issue with IMC domain

 

Scott:

 

 

Are the DNS entry and the NETBIOS settings exactly the same as the settings
on the machines that work?

 

 

Anything in the event logs? 

 

Lee Duynslager

 


  _____  


From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of Scott Cassaday
Sent: Wednesday, October 17, 2007 11:22 AM
To: [log in to unmask]
Subject: [MSUNAG] Wierd issue with IMC domain

 

Im having a wierd issue with the IMC domain....

Yesterday 3 machines just stopped connecting to the domain. Other machines
in the same office are just fine. The machines can ping the domain servers
and tracert shows only a couple of hops. Just as a test I tried removing one
of the machines from the domain and re-adding. It comes up with a login
window for the domain ( so it apparently is finding the domain" but once I
try to login it throws a "the network location cannot be reached" I have
switched IP's and checked that all settings are correct. The machines in
question are able to browse the web. Any ideas ?

 

Scott Cassaday



__________ NOD32 2597 (20071017) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com