MSFN Forum: Problems after removing Update Rollup 1 for W2K - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Problems after removing Update Rollup 1 for W2K Rate Topic: -----

#1 User is offline   cdplayer 

  • Newbie
  • Group: Members
  • Posts: 11
  • Joined: 17-August 05

Posted 18 August 2005 - 10:47 PM

Two days ago I installed Microsoft’s Update Rollup 1 for Windows 2000 SP4 on one computer. After the successful (?) installation of the update I was not able to access the Internet or other computers on my LAN (Peer-to-Peer).

At that point I uninstalled Microsoft’s Update Rollup 1 for Windows 2000 SP4.

After the uninstall I was able to access the Internet but soon after I realized that I could not communicate with the computers at home via the network. All of the other computers can talk and see one another, pass files back and forth etc. They could not see me I could not see them.

Finally after trying >many< things I removed all networking components from Comet (Comet is the computer that got injured via the Update), reboot then set them up again. Now I can connect to the Internet see and access all computers on the LAN. The down side is that the computers on the LAN can see me (Comet) but cannot access the computer.

Example:
When I am on another computer (Blazer) and trying to reach the other computer (Comet) I get the following message:

\\Comet is not accessible. The network path was not found.
Comet is the computer that got injured via the Update.

On each computer I have done an IPconfig/all. Everything looks correct.
The network configuration data found under the Internet Protocol (TCP/IP) Properties is the same for all computers on the LAN with the exception of the IP addresses. The computers addresses were setup manually.

NetBIOS over TCP/IP is enabled on all computers
From Comet I can ping to the other machines.
Under "Network Identification" tab everything looks correct on the troubled machine (Comet).

After I did a nbtstat –n on Comet I looked in the Event Viewer and discovered an error
(Event Viewer error follows the nbtstat -n data):

C:\WINNT\system32>nbtstat -n

Local Area Connection:
Node IpAddress: [192.280.1.176] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
COMET <00> UNIQUE Registered
COMET <20> UNIQUE Registered
WGM <00> GROUP Registered
INet~Services <1C> GROUP Registered
IS~COMET....<00> UNIQUE Registered
WGN <1E> GROUP Registered

WGN = Workgroup Name

Event Viewer Error Message:

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 8/18/2005
Time: 6:55:49 PM
User: N/A
Computer: COMET

Description:
A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

OK I have the data from the NetBIOS Local Name table as you can see but I
am not sure what my next step should be. Where do I go from here? :unsure:

I feel am so close to completing the final step yet so far............

Any comments or suggestions are appreciated!

Thanks!


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy