• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

WinXP and WIN2k netorking probs

gogeeta13

Diamond Member
On my network, I have 2 XP boxes, and 2 2k boxes. one of my XP boxes, and botht he win2k boxes can see each other. My other XP box can't access or see the other ones. It has internet working, and it is using TCP/IP just like the others. It has the same workgroup, and no domain. It is running with the same DHCP and everything as all the other boxes.

What is wrong?
 
Is IP working (can you ping the other boxes?)? Check physical layer (cables).

What other protocols do you have set up? (On the working boxes, and the problem one).
Do you have "NetBIOS over TCP/IP" enabled? (on the problem box)

Hmmm... <still thinking>

--Woodie
 
Physicals are fine, all the boxes have net access..

All the boxes have netbios(I need to keep this on for LAN party purposes)

I am about to try pinging..

yEAH, they can all ping each other
 
So, you have TCP/IP working, and you have NetBIOS...is that installed as a seperate protocol or as "NetBIOS over TCP/IP"?

How does name-resolution work? Do you have your own DNS? Check to see what ipconfig /all says, particularly the info after: DNS Suffix Search List

Does the event-log on the problem box give any clues?

--Woodie

 
The XP machines have netbios over TCP

here is my /all:


<< Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Andrew1>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : andrew
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . : clvhoh.adelphia.net.
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet Adapt
er(LNE100TX v4) #3
Physical Address. . . . . . . . . : ***EDITED
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : December 17, 2001 4:49:00 PM
Lease Expires . . . . . . . . . . : December 20, 2001 4:49:00 PM

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet Adapt
er(LNE100TX v4) #2
Physical Address. . . . . . . . . : ******EDITED

C:\Documents and Settings\Andrew1>
>>



 
Interesting...if I read this correctly, you have 2 nics, and the second one (Ethernet #2) is not connected, and not important to your connection.
Your (primary) adapter is configured by name to map to your ISP, and the IP address is given out by your router, which is also your gateway and your DNS.
What is the binding order? I'm wondering if somehow some protocol is bound to the second adapter, and it's trying to browse out through that.

In case you (or any lurkers) didn't catch this...physical layer is ok, TCP/IP is working fine, the problem is somewhere in the MS Browsing functionality--possibly master browser-type services, or in the binding order from the application to the right NIC.

--Woodie
 
If you can ping all the boxes, the next issue I would tackle is the name resolution. I'm looking at your set-up and thinking you are employing ICS. Correct me if I am wrong. Do me a favour and navigate to c:\winnt\system32\drivers\etc\hosts on the box hosting the ICS ( and DNS apparently)
Edit the hosts file to include an entry for the box you are having issues on.

<computername> ip.address.goes.here

lemme know if that resolves the problem.
 
I am not home right now, but I know I have the ICS box unchecked in connection properties.

The second ethernet adapter got fried, and it thinks it has a connection, but it doesnt. I will pull it out later tonight,when I get home.

Thanks for all the help and advice guys!
 


<< If you can ping all the boxes, the next issue I would tackle is the name resolution. I'm looking at your set-up and thinking you are employing ICS. Correct me if I am wrong. Do me a favour and navigate to c:\winnt\system32\drivers\etc\hosts on the box hosting the ICS ( and DNS apparently)
Edit the hosts file to include an entry for the box you are having issues on.

<computername> ip.address.goes.here

lemme know if that resolves the problem.
>>



I am home now..

I have no box hosting DNS/ICS

I have a netgear rt314 router
 
😀 Well From what I know is that it can take up to 45 mins for Win Boxes to see each other on the network.... if you can force your way onto a box with an IP they should work fine. Windows just has some weird network code.
 
after several, several reboots and many rejoinings of the domain it is workig again..

I didnt bother removing the other network card either..
 


<< after several, several reboots >>



LOL...don't you just looove windows?? 😉 A little frustrating, since we still don't know the real cause of the problem, other than it had something to do with domain membership.


Happy you've got it working the way you want, though.

--Woodie
 
Back
Top