Windows 2000 Pro - cannot access network all of a sudden

[SteadySystems]

I was able to login to the network using a new addition to the network - a Win2k dekstop. However I had not yet set the computer to join the domain, I had it set to join the workgroup (accidentally typed the domain name in the workgroup section, doh!) Anyway, that was a not an issue as I was still able to map drives and authenticate. All of a sudden I could not access the network. When I reboot, the drives would not map. So I decided to try to join the domain and it returns a DNS error. "problem validating the domain, this could be caused by a DNS lookup problem. The domain does not exist or cannot be contacted." or something similiar to that effect. Now:

- all other computers on my network are fine
- I can ping 127.1.1.0
- I can ping the server ip
- I can ping the router
- I can release and renew a ip from DHCP successfully
- I can get internet access through our network, just like anyone else
- at one point, without joining the domain I was able to map drives, use network resources
- I performed a ipconfig /dnsflush and /registerdns

This is the ONLY WARNING in Event viewer on my computer:

Event ID 8021
Source - Browser
The browser was unable to retrieve a list of servers from the browser master \\LUCKYNT2000 on the network \Device\NetBT_Tcpip_{046340A6-7FEC-4302-B0DB-4F18D738449D}. The data is the error code.

***** I noticed this error on the server:

The master browser has received a server announcement from the computer DANIEL that believes that it is the master browser for the domain on transport NetBT_Tcpip_{CD8D7F09-F8C0-453C-8E. The master browser is stopping or an election is being forced.

That is my computer.

Any help appreciated!

Daniel

 

[SteadySystems]

okay, I walked over to a working computer in the same network and noticed that they have all the same errors I do in thier event viewer. SO this must not be an issue enough to knock the other computers off the network. I am the only computer that cannot get to the network.

 

[bcastner]

I do not know if these are your internal DNS servers:

DNS server list :
66.51.205.100, 66.51.206.100

If these are your ISP's DNS servers, then you need to do something more.

On a "good" computer, examine closely what is entered under TCP/IP properties, Advanced, the DNS tab. Write these down.

On the "bad" computer, go the the Advanced DNS properties sheet and make sure it matches exactly the "good" settings.

If you make any changes, reboot before testing again.

 

[SteadySystems]

These are the same settings that every computer has. Those are our ISP's DNS servers I believe.

 

[bcastner]

I was afraid they were your ISPs DNS servers.

See if the "good" machines have a HOSTS entry for your DC, or an LMHOSTS entry for your DC that does not exist on your "bad" machine.

In joining the workstation to the Domain, in the absence of a local DNS server, you need some unambiguous way for the new workstation to resolve the Netbios name of the DC/Server. You might try this:

Set a static IP of 192.168.1.254 (check that it is not in use already). Subnet 255.255.255.0, Gateway 192.168.1.1

Under the Advanced, DNS tab provide the IP of the DC/Server as the only entry. Uncheck the dynamic registration with DNS tab.

Reboot and try to join the Domain.

 

[SteadySystems]

bcastner, thanks.

- no host or lmhosts file on "good" computers
- I statically added 192.168.1.69, added dns and subnet, default gateway, etc.

However I do not see this: "Uncheck the dynamic registration with DNS tab."

Now what is strange is, I did not even reboot after I statically change ip and added the dns 192.168.1.198

I went to map a drive and it worked. I noticed that NORTON INTERNET SECURITY 2004 asked if lsass.exe is okay to access the internet, I approved. And viola! The drive was mapped.

Everythings fine right?

Wrong.

I rebooted, I cannot sign in to the domain, but I can AGAIN login to local admin and map drives. SO STRANGE!

Now, is it possible that someone has a D.O.S. on my machine? I mean , why would Norton want clearance for lsass.exe to access the internet?

This is an enigma.

Daniel

 

[bcastner]

It is not unusual for lsass to want to get outside your firewall.

But you raised something important. Turn off, remove, disable, kill the firewall until after you have setup everything, including joining the Domain.

It most certainly explains your issue. Warning: just clicking on the Task Tray icon and selecting disable is not good enough. I would Control Panel, Add/Remove Programs, and remove it until you have everything else sorted.

Under TCP/IP properties, Advanced, DNS tab, there should be a checkbox 'Register this connection's address with DNS' and that is what I wanted you to uncheck.

 

[SteadySystems]

okay, I removed all of norton from add/remove

- rebooted
- still cannot login to domain

So I disjoined from the domain and changed to workgroup and changed computer name to DDC (it was Daniel)
- rebooted

Walked over to the server and removed my DANIEL computer account (which had an X through it because I disjoined)

Back on my machine I tried to join the domain, when asked for user/pass I used the administrator (like I have before successfully) and get this error:

Network Identification
The following error occured attempting to join the domain luckystarusa.
The credentials supplied conflict with an existing set of credientials.

I also, as a another attempt set the TCP IP settings back to Obtain IP and DNS automatically (like the "good" machines). Bcastner, let me know if I should change it back to your suggestion.

Daniel

 

[SteadySystems]

In Event Viewer there is a new error:

1000 Userenv
Windows cannot determine the user or computer name. Return value (1326).

 

[bcastner]

After removing the machine account from the Domain you usually have to wait around 15 minutes or so before attempting to rejoin.

Note that your Name Resolution and DNS registration errors are gone. So you are finding the Server.

I would reset the System Properties back to their Domain setting, let the server calm down a few minutes, and try the join again.

 

[SteadySystems]

Waited 15 mins or so, same error as above when trying to join the domain:

"Network Identification - The following error occured attempting to join the domain luckystarusa. The credentials supplied conflict with an existing set of credientials"

Also on the server here is another error:

The session setup from the computer DANIEL failed to authenticate. The name of the account referenced in the security database is DANIEL$. The following error occurred:
Access is denied.

I am going to freak out at any moment.

 

[bcastner]

At the command prompt type:
net use * /del

this will clear out all mapped drives, and also any IPC$ connections you may have that are conflicting with your logon attempts. You should then be able to connect with different credentials.

 

[SteadySystems]

Well, finally some headway. Came into work this morning, joined the domain, was able to sign in to the domain as well and all is good for now.

However, the errors still exist in EV and also I have no clue what the resolution was, we tried so many things.

Let me know your thoughts!

Regards and many thanks,

Daniel

 

[1stITMAN]

I would uninstall all network devices and protocols and rename the computer.

Zaheer Ahmed Iqbal
I.T Systems Support Engineer
Bsc. (Hons).

 

[straybullet]

OMG OMG OMG OMG - Im having the same problem!!!!
Did we download an "update" or something that is messing us up? Im printing out this whole thread to give me a chance to go over it bit by bit.
Any other suggestions? In my case, the workstation that is suddenly unable to access the network was able to for short periods ( a few hours at a time) when TCP/IP was reinstalled. However, even that option is now gone as my Network Connections window is now empty...
EEEEEEEEEEEK!!!

Willing to take just bout any suggestions at this point - Ill be sitting here with one hand on the keyboard and the other wielding a hammer.

 

[SteadySystems]

No, there was no update installed. The workstation was working fine and was new to the network.

I think the problem could have been Norton Internet Security 2003 or an internal issue with DNS on my server.

That is yet to be determined.

 

[chefGeek]

do you have a spare NIC around? I've used that to t/s this type of problem before. I've seen NICs on their last legs act funny with DHCP and DNS issues. What if you hosted DHCP and DNS locally (on your PDC) that will solve name resolution issues... just a couple of ideas. Both of these have worked for me before.