Windows Networking Issues

[jlinker]

I posted this at HardOCP earlier, and after a few days, none of us were able to come up with any solutions. Here's the post from there with extras added. I'm getting frustrated about this issue.

I should start by saying we're on a college network, so my knowledge of the physical connection is somewhat limited, however I do have some still.

I recently went to reinstall my Windows XP Pro copy, as my machine was coming up on 2 years without a reinstall, and it was starting to get sluggish. Anywho, my roomate had decided to reformat as well recently; he needed to since he received an Athlon 64 and respective motherboard for Christmas.

After reinstalling Windows, neither of us could see each other on the Windows "Networking". We had similar issues beforehand, but were able to resolve them one way or another. When going into the "View Workgroup", I would originally get a message "The list of servers for this workgroup is not currently available". My roomate would try the same, and his view workgroup would only display his computer or none. It almost seemed random.

I went through the almighty google, and followed some similar solutions through by changing the registry value on both machines to HKEY_Local_Machine\System\CurrentControlSet\Services\NetBT\Parameters
DhcpNodeType to mixed (4).

From there, I was finally able to see both computers in the browser, but he is only able to view himself. If I try selecting his computer, I receive the message

\\______ is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

The network path was not found.

Ok, easy enough I hoped. I decided to try directly browsing to his IP via \\xxx.xxx.xxx.xxx, but I get nothing.

Here's what we've also verified.

• Both computers are on the same class B IP range. We've statically assigned them to ensure they are such.

• Both Computers run through the same Gateway, DNS and are on the same subnet.

• Both computers are on the same workgroup.

• Both computers are running Windows XP Professional with the latest security and optional updates as of Jan. 16, 2006. We both also have the .NET 2.0 Framework and SDK installed as per class requirements for our programming courses.

• File sharing is enabled on both machines, and the folders set to be shared are accessible by "anyone" for reading, but not writing.

• The Computer Browser service is in the "started" state on both computers. They're both set to be automatically managed by Windows.

• The NetBIOS settings is set to default within the TCP/IP advanced config.

• Both computers are running AVG Free antivirus; there are no firewalls installed. Windows firewall is also disabled. Our school has no restrictions on file sharing through our LAN.

• Out of a bit of desperation, we've both run the Windows Networking Wizard. With any misfortune, this has caused more harm than good.

• \\xxx.xxx.xxx.xxx\ from either machine doesn't work either.

We've run
netsh int ip reset c:\results.txt
on both machines, as per one bit of advice, and also checked afterwards to ensure that our DHCP gave us a matching IP range/subnet, and there was still no success.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters\"MaintainServerList"
The value for MaintainServerList is set to Auto, and both machines have their Computer Browser, Service, Client services all set to auto.

I can ping his machine, but can't access in it for file/printer sharing, but the clients are installed and we both have active shares. Oddly enough, however, I can view other workgroup users on our school network and view their folders, but his machine can't.

We've also tried disabling Simple File Sharing on both machines. Any help would be appreciated, thanks.

 

[DaiShan]

If you want to share files only, why don't you just install an FTP on one of your computers. Thats the easy solution rather than deal with a "cloud" topography. Alternatively, you could use a switch and have an internal network in your dorm.

 

[RebateMonger]

It's pretty difficult to have XP Professional networking NOT work.

My suggestion is to first verify basic Windows networking and connectivity:

0) Verify that "Simple File Sharing" has been DISABLED on each PC.
1) Hook the two computers together using either a crossover cable or a switch, a router, or a hub.
2) Remove the NICs from both computers from both the Network Connections Control Panel and from the Device Manager. I can never remember which has to come first. Just delete whatever you have to to get the network cards to completely disappear from the Device Manager.
3) Reboot the PCs.
4) Allow the NIC drivers to re-install.
5) In the Network Connections control panel, set the TCP/IP properties of each NIC so that they have manually-set IP address and subnet mask. Use 192.168.0.1/255.255.255.0 and 192.168.0.2/255.255.255.0 on the two computers. Don't bother with DNS or Default Gateway. You don't need them for this test.
6) You should now, hopefully, have working network connections to each other.
7) Verify that you can ping each other. Windows XP2's incoming firewall will reject pings by default, so you'll either have to allow pings or turn off the firewalls temporarily.
8) On each computer, create an account for the other person. It must have a password.
9) Create a new shared folder. In the Sharing controls, set them to "Everyone", Full Control. In the Security controls, add the other person's account and give them at least "Read" rights to the folder.
10) Ensure that each person's account on his own computer requires a password.
11) Log off each computer. Then log back on, using your password.
12) Open up Internet Explorer and, in the address bar, type: "\\192.168.0.x", where that's the IP of the OTHER computer.
13) If asked for an account/password, enter the UserName/Password of your account that has been created on the OTHER computer.
14) You should now be able to see each other's shared folders.

If the above steps don't work, then you have messed-up Windows XP networking and some repair steps will be needed.

 

[JackMDS]

Did you try to install NetBEUI and see if it shares through it?

Set NetBEUI as the Default Sharing Protocol in WinXP.

:sun:

 

[jlinker]

Originally posted by: DaiShan
If you want to share files only, why don't you just install an FTP on one of your computers. Thats the easy solution rather than deal with a "cloud" topography. Alternatively, you could use a switch and have an internal network in your dorm.

I also use my roomate's printer, so Windows Networking seems to be the easiest solution.


RebateMonger,

Ok I just put both of our computers on a switch I had laying around in my room.

I noticed that, in my event viewer, under normal "problematic" conditions I see

Error 8003

The master browser has received a server announcement from the computer OMEGA that believes that it is the master browser for the domain on transport NetBT_Tcpip_{B9C217BA-4784-4413-A91. The master browser is stopping or an election is being forced.

Omega is my roomate's machine.

After putting both of computers on the same switch, his computer doesn't show anything in the View Workgroup Computers, but if I run \\xxx.xxx.xxx.xxx\ from his computer, it communicates with mine.

If I run the View Workgroup Computers, I only see myself, and can't use the \\ip\ route to view his shares.
I did notice, however, that after trying to view his computer while we were on the switch, I see
Error: 3019

The redirector failed to determine the connection type.

What concerns me is that within 30 minutes of freshly installing Windows on both machines, this problem arises. It doesn't come until after I've installed all of the Windows updates.

I've had a customer's machine that was properly communicating between 2 PCs on a residential gateway. He bought his son a laptop, and it came preinstalled with Windows XP Pro. Now, I ran Windows Updates to make sure he had the security updates, and then their entire household network started having this same problem. Could these be related?


JackMDS,

No, not yet. What advantages, if any, would that provide?

 

[JackMDS]

Well it probably would let you share files and printers.

http://www.ezlan.net/sharing.html

:sun:

 

[RebateMonger]

Originally posted by: jlinker
Error 8003
The master browser has received a server announcement from the computer OMEGA that believes that it is the master browser for the domain on transport NetBT_Tcpip_{B9C217BA-4784-4413-A91. The master browser is stopping or an election is being forced.

The "Master Browser" message isn't a problem. It's just your PCs trying to determine who will be in charge of the network "phonebook".

After putting both of computers on the same switch, his computer doesn't show anything in the View Workgroup Computers, but if I run \\xxx.xxx.xxx.xxx\ from his computer, it communicates with mine.

The "View Workgroup Computers" listings come from the NetBIOS service. The \\xxx.xxx.xxx\ function comes from basic TCP/IP connectivity.

Error: 3019
The redirector failed to determine the connection type.

That could be a problem...

What concerns me is that within 30 minutes of freshly installing Windows on both machines, this problem arises. It doesn't come until after I've installed all of the Windows updates.

I didn't get from our original post that you'd JUST re-installed Windows. I don't know of any current XP updates that will mess up a freshly-installed Windows XP installation.

(NetBEUI)No, not yet. What advantages, if any, would that provide?

You can, alternatively, use NetBEUI or IPX/SPX as a networking protocol. IPX protocol is included in a default XP install. You have to install the optional NetBEUI protocol. But you really should try to get TCP/IP working correctly.

 

[jlinker]

Well I'd rather keep with TCP/IP, but if I really have to, I can always try NetBEUI or something else.

I haven't heard of any issues with current XP updates either, but I do find it peculiar that I've had functional networking until I install a system with new updates.

Any ideas as to why I can see a computer listed in the NetBIOS listing, but can't establish a connection?

Microsoft says that the "The Redirector..." error can be safely ignored; I'm not sure whether or not I want to trust that just yet.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q315244

 

[jlinker]

^^^

 

[piasabird]

You can turn master browser off it does nothing for anyone on a LAN.
Is your Firewall on?
What are the settings on the Windows Firewall?
Do you have a firewall installed?
Does your network have a client you need to install?

 

[JackMDS]

LOL.

On a small network TCP/IP and NetBEUI work very well together.

If you have water surce in the bathroom, and in the Kitchen, nothing happened if you add a third faucet in the tool shed.

When people start this, "I only want TCP/IP" it might be that sharing is not as important to them.

Or may be I do not get it.:shocked:

:sun:

 

[RebateMonger]

Originally posted by: JackMDS
On a small network TCP/IP and NetBEUI work very well together.

You can certainly use NetBEUI or IPX/SPX to network computers on the same, unrouted, subnet. Lots of people did this when Windows XP came out and they couldn't get TCP/IP working for file sharing. For that matter, you can grab the files onto a USB Flash drive.

But what happens when this person wants to access OTHER shared folders on his college network? Are they going to ask everybody on the network to install NetBEUI? NetBEUI is not supported by Microsoft anymore and requires an XP Install CD to install it. At least if you pick (supported) IPX/SPX, you don't need a CD, and you can play some of the games that require it (like StarCraft).

TCP/IP is the "native" networking protocol for XP. It should work out of the box. If it's not working, I think it's a good idea to try to find out why.

 

[RebateMonger]

OP,

Are you joined to a domain?

 

[jlinker]

Originally posted by: piasabird
You can turn master browser off it does nothing for anyone on a LAN.
Is your Firewall on?
What are the settings on the Windows Firewall?
Do you have a firewall installed?
Does your network have a client you need to install?

As stated before
Firewall Off.
I unbound Windows Firewall from our LAN connections, but the "File Sharing" is still checked in the allowed list, even though the firewall is disabled.
No Firewall installed.

Our college network doesn't require any extra client; it's all windows-based.

Rebatemonger,

Our residence hall isn't on the same network as our main college buildings. The residence hall doesn't have a domain; it's all user-preference. The ResNet offers ethernet jacks in the room which go to their room with a server that monitors bandwidth (for restriction purposes), but the bandwidth monitoring is only applicable to WAN bandwidth and not LAN.

They have no restrictions on file sharing, but their AuP states that you're not allowed to move pornography or otherwise illegal materials. (The files I want from his machine aren't illegal in any way; in fact, I just don't want to spend 900mb of my bandwidth redownloading AAO, and I need to use his printer from time to time).


Edit real fast:

In case anyone is wondering, yes. These are both LEGIT copies of XP Professional.

Mine is an XP Pro copy I bought a few years back.
My roomate's is from our MSDNAA access.

 

[RebateMonger]

jlinker,

I couldn't tell from your posts whether you can ping either computer when they are hooked to the same switch. The basic test of connectivity when hooked to each other like that is if you can:
Ping using the IP address.
Ping using the NetBIOS name.

If you can do that from both computers, then you have functional TCP/IP networking and you have functional NetBIOS connectivity.
If the pings AREN'T working, then there's a connectivity problem.
If the pings ARE working, then there's a sharing setup problem in Windows.

 

[jlinker]

Originally posted by: RebateMonger
jlinker,

I couldn't tell from your posts whether you can ping either computer when they are hooked to the same switch. The basic test of connectivity when hooked to each other like that is if you can:
Ping using the IP address.
Ping using the NetBIOS name.

If you can do that from both computers, then you have functional TCP/IP networking and you have functional NetBIOS connectivity.
If the pings AREN'T working, then there's a connectivity problem.
If the pings ARE working, then there's a sharing setup problem in Windows.

When connected to the switch I can ping.
When connected to our ResNet, I can ping.

I have files set to share, and the permissions are both set to allow read access to anyone, but write access is disabled.

 

[RebateMonger]

Originally posted by: jlinker

Originally posted by: RebateMonger
jlinker,

I couldn't tell from your posts whether you can ping either computer when they are hooked to the same switch. The basic test of connectivity when hooked to each other like that is if you can:
Ping using the IP address.
Ping using the NetBIOS name.

If you can do that from both computers, then you have functional TCP/IP networking and you have functional NetBIOS connectivity.
If the pings AREN'T working, then there's a connectivity problem.
If the pings ARE working, then there's a sharing setup problem in Windows.

When connected to the switch I can ping.
When connected to our ResNet, I can ping.

I have files set to share, and the permissions are both set to allow read access to anyone, but write access is disabled.

jlinker: I'm not sure what "I can ping" means. Does that mean you can ping both computers using both IP addresses and NetBIOS names?

What happens if you go to each computer and try to access "\\computername", where "computername" is the NetBIOS name of your OWN computer? Can you then open one of the shared directories on your own computer? That will tell you if sharing is set up properly.

Microsoft Support: How to troubleshoot home networking in Windows XP.
All the rest of Microsoft's XP network troubleshooting articles.

 

[jlinker]

If I go into my command prompt and ping the IP of both the computers, I get an active response <1ms.

If I do a ping from my computer to my computer using the NetBIOS name, it's reads properly.

If I ping OMEGA (netBIOS name) from my computer (my roomate's machine), I get an error that it can't be found.
If I ping OMEGA or do \\OMEGA\ from his machine (basically finding itself), it reads properly.

http://www.jlinker.com/netw/

That's at least what Windows shows. I'll add more screenshots later after class.

 

[RebateMonger]

jlinker,
You never verified here that all accounts on both computers have passwords. Lack of passwords will kill file sharing in this situation.

 

[spidey07]

LOL - just load netbeui and be done with it.

otherwise just access the machine with \\ip address

If you really want to keep banging your head getting on an inherently broken mechanism to work then post output of

net config workstation
net config server
ipconfig/all

on each machine. And of course make sure that you are sharing something and have setup accounts/passwords

 

[jlinker]

Originally posted by: RebateMonger
jlinker,
You never verified here that all accounts on both computers have passwords. Lack of passwords will kill file sharing in this situation.

Both do, sorry.

I've also tried with the same account name/password on both.

Spider,
\\ip\ doesn't work. It's been said a already.

Have you considered reasons for not loading NetBEUI? It's an outdated protocol that wasn't loaded with default installations because of that. Hell, Microsoft doesn't even support it anymore. If a certain protocol is causing problems, it's honestly poor practice to just bypass it and be "done with it" when there's a chance you can still resolve the problem.


net config workstation

Computer name \\ADMIRATEUR2
Full Computer name admirateur2
User name Jon Linker

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{B9C217BA-4784-4413-A913-55EAE61147C5} (000461DFFFFD)

Software version Windows 2002

Workstation domain STRUT3
Workstation Domain DNS Name (null)
Logon domain ADMIRATEUR2

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.

net config server

Server Name \\ADMIRATEUR2
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{B9C217BA-4784-4413-A913-55EAE61147C5} (000461dffffd)


Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : admirateur2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : oit.edu

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : oit.edu
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : [snipped]
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 140.211.139.196
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 140.211.136.1
DHCP Server . . . . . . . . . . . : 140.211.135.12
DNS Servers . . . . . . . . . . . : 140.211.135.12
Lease Obtained. . . . . . . . . . : Thursday, January 19, 2006 7:18:59 P
M
Lease Expires . . . . . . . . . . : Friday, January 20, 2006 7:18:59 PM

 

[spidey07]

undo your registry change. You are in "mixed" mode for netbios over TCP.

you need to be "hybrid", which is what is will be if you don't muck with the registry.

also post for both computers.

"Node Type . . . . . . . . . . . . : Mixed "

also don't rely on network neighboorhood or "view places" as it is unreliable. also don't go booting machines willy nilly to fix the problem as that only makes it worse. windows can take up to 4 hours to get browsing settled. also make sure that the protocol/network/netbios over TCP settings/bindings are EXACTLY the same on each computer

 

[jlinker]

Originally posted by: spidey07
undo your registry change. You are in "mixed" mode for netbios over TCP.

you need to be "hybrid", which is what is will be if you don't muck with the registry.

also post for both computers.

"Node Type . . . . . . . . . . . . : Mixed "

also don't rely on network neighboorhood or "view places" as it is unreliable. also don't go booting machines willy nilly to fix the problem as that only makes it worse. windows can take up to 4 hours to get browsing settled. also make sure that the protocol/network/netbios over TCP settings/bindings are EXACTLY the same on each computer

You might want to explain "booting machines willy nilly", as that statement makes no sense.

I got it working, with node type as mixed, actually. It turns out to be an odd issue with the 5.11 Forceware Ethernet drivers. THere's a *.sys file that's commonly causing BSODs under certain instances, amongst other errors. I reinstalled the 5.11, and obviously had the same problem.

Finally went back and installed the 5.10 on both machines; all is good.

Thanks to those that helped!

 

[petey117]

ok, i see you are using a nvidia ethernet controller.
the driver for them includes a Nvidia firewall.
check for the tray icon, or check the control panel.
you can also try: nbtstat /R

 

[jlinker]

It's fixed.
Like I said, it was the driver version and a known issue with the version / SP2.
The firewall was disabled, and has been so; I've already said that.