Need Help with LAN Browsing

[Draggon]

Typical home LAN setup:

Desktop1 - Windows XP Pro SP2 - Connected to Port 1 of Router
Desktop2 - Windows XP Pro SP2 - Connected to Port 3 of Router
Wireless1 - Windows XP Pro SP2 - 802.11g Wireless Adapter (TrendNet) - Less than 15' from Router

Signal Strength and Link Quality are both 95%+.

Router - Belkin Pre-N http://catalog.belkin.com/IWCatProductP...on_Id=202570&pcount=&Product_Id=184316

All three PC's have no problem accessing the Internet/Email, etc. Desktop1 can "see" other two PC's in Windows Explorer's "Network Places/Entire Network/Windows Network/Workgroup" and can browse the shared folders. Desktop2 can do the same with Desktop1, but can't see Wireless1. Wireless1 can also see and browse Desktop1, but can't see Desktop2.

All three PC's can ping each other at the command prompt. Browstat (at command prompt) shows all 3 systems and shows Desktop1 as the 'Master Browser'. Desktop2 and Wireless1 simply can't share. I've tried searching for each computer by name and by IP number. No luck. Start/Run/IP# and Start/Run/'Computer Name' does not work.

I've futzed around with settings for several days trying to figure this out. I've gone through troubleshooting guides from Microsoft Support, ezlan.net and other sources to no avail. I've uninstalled and reinstalled all services and protocols several times. I've "reset" the TCP/IP installation according to Microsoft's instructions (equivalent to uninstalling and reinstalling TCP/IP). I've tried Netbeui, and it didn't work. Currently, all three PC's are on the same workgroup, have different computer names, and have only the following three network functions running:

- Client for Microsoft Networks
- File and Printer Sharing
- TCP/IP

Last night, I set static IP addresses on all three PC's and disabled the DHCP function on the router. This caused an interesting change in the behavior of Desktop2. It could now "see" Wireless1 in Network Places and could even see the files in the shared folder (though only after lengthy delays). However, no such luck with Wireless1. It still could not see Desktop2.

The very last thing I tried last night was to disable the wireless adapter in Wireless1 and to hardwire it to Router Port 2. All problems went away when I did this. All three PC's now see each other (quite rapidly) in Network Places and can easily browse files and printers with no delays.

Based on all the evidence, this is obviously a wireless issue. I'm suspecting the Router or a setting therein, but I have no idea what to try next. I've paged through all the settings in the router several times and don't see anything that might be blocking communication between Wireless1 and Desktop2 (keep in mind, they can ping each other just fine, so connectivity is okay). I had the Router set to disable broadcast of the SSID, but I've since enabled that. My security method is WPA/TPIK.

I really don't want to hard-wire this PC. There is no easy way to do it permanently (CAT5 is currently stretched diagonally across the room), and I would think operating wirelessly wouldn't be impossible (or even all that difficult).

I'd really appreciate any ideas you might have on what I can try next in order to get the wireless functionality of my network working again. Please let me know if anything is not clear and feel free to ask additional questions.

Thanks for your time.

 

[spidey07]

you're not gonna like this answer....

This is normal for microsoft networks. Especially if any settings have been changed and everything isn't EXACTLY correct. Even then you can have the same symptoms.

You really should just access each computer by name or IP address (\\name) instead of using browsing.

-edit- oh, I see you've tried accessing them that way. Post ipconfig/all of the wireless machine and net config server and net config workstation. Very doubtful it is the router's problem - most likely a configuration issue on the PC.

 

[ktwebb]

I've futzed around with settings for several days trying to figure this out

Unfortunately this makes troubleshooting from here nearly impossible. XP is pretty good about resolution by broadcast and Network Places but as Spidey mentioned, by and large, windows networking through Net Places, without DNS or WINS is suspect at best.

I would recommend trying to get back to the default settings as much as you can or can remember. From there take each PC down and boot up one at a time. Give the workstations some time for broadcasts and master browser authentication and get to network resources via UNC as suggested by Spidey.

If using the name doesn't work then try it with IP in the path instead.

There are quite a few walkthrough websites out there with screen captures if you need a step by step. practicallynetworked.com for instance but a google search for Windows XP pro file sharing should yield numerous helpful hits.

 

[Draggon]

Originally posted by: spidey07
you're not gonna like this answer....

This is normal for microsoft networks.

Yeah, I kind of expected that one...

Post ipconfig/all of the wireless machine and net config server and net config workstation. Very doubtful it is the router's problem - most likely a configuration issue on the PC.

First, thanks a lot for taking the time to respond. I'm on the verge of desperate here...

IPCONFIG /ALL

Windows IP Configuration

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

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : IEEE 802.11g Wireless Cardbus/PCI Adapter
Physical Address. . . . . . . . . : 00-40-F4-D6-0B-D6
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1

NET CONFIG SERVER

Server Name \\P-3
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{ECB891B2-AEF7-40FB-A710-4EB44F23C22A} (0040f4d60bd6)


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

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

NET CONFIG WORKSTATION

Computer name \\P-3
Full Computer name P-3
User name Ron

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{ECB891B2-AEF7-40FB-A710-4EB44F23C22A} (0040F4D60BD6)

Software version Windows 2002

Workstation domain FAMDAMILY
Workstation Domain DNS Name (null)
Logon domain P-3

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

 

[spidey07]

your netbios node type needs to be broadcast. It's listed at the top of ipconfig/all.

bingo.

Also, I assume all machines are on the 192.168.2.0/24 network?

 

[Draggon]

Originally posted by: ktwebb

I've futzed around with settings for several days trying to figure this out

Unfortunately this makes troubleshooting from here nearly impossible.

I will respectfully disagree, but only because I know more about what I've done to my systems than you do, and I agree that my post makes it sound like I've run willy-nilly through anything I could change. I'm an engineer by trade, so I'm very methodical in how I attack a problem. I start with simple trouble-shooting first, then move on to more complex procedures as necessary. In this case, when I said "futzed around", I should clarify that the changes I've made are not all stacked on top of one another. When a change didn't work, I'd change things back and try something different. My systems are not very far from default at present. They are as described near the end of my post.

I would recommend trying to get back to the default settings as much as you can or can remember.

I wish it were that simple. I can get back to near default settings, but it won't solve the problem. I've already been there...

From there take each PC down and boot up one at a time. Give the workstations some time for broadcasts and master browser authentication and get to network resources via UNC as suggested by Spidey.

Good suggestion, but I've tried that, too. I booted them up sequentially before going to bed one night. The next morning, I verified at the command prompt that Desktop1 had been elected as Master Browser. I also verified that all the PC's were recognized as part of the network. Still, browsing or file access between Desktop2 and Wireless1 was non-existent.

If using the name doesn't work then try it with IP in the path instead.

I've tried. It will not work. This tells me that it's more than just a simple "Windows Network won't browse again" problem. Even when you can't browse, you should always be able to pull other networked PC's up with the Start/Run/ "\\IP_Number" command. Not so in my case.

There are quite a few walkthrough websites out there with screen captures if you need a step by step. practicallynetworked.com for instance but a google search for Windows XP pro file sharing should yield numerous helpful hits.

Yes, I think I've been to all of them. None seem to address the problem I'm having. I have functional connectivity at the command prompt, but no way to access between Desktop2 and Wireless1 within Windows.

The fact that all the problems I've described go completely away when I hard-wire Wireless1 to the Router makes me believe that my basic configuration is good to go.

I sincerely appreciate your effort to help, and I hope you don't take this post as my blowing off your advice. I really have tried what you've suggested. If you have any further thoughts, I'm all ears... er... eyes.

Thank you!

 

[spidey07]

heh, when troubleshooting MS networking you have to throw normal routine troubleshooting out the door. It just can't be done that way.

It truly can get that fubarred that you can't repair it or return it to a usable state without completely removing the device and repairing the IP stack manually (messy.) messing with or changing network settings without rebooting each and every time you change something and then re-installing the service pack can cause this. Heck it wouldn't be a bad idea to reinstall the service pack just to try, that can repair some network settings/files.

The fact that it works wired and not wirelessly means it is probably configuration or the stack/driver.

also, what error message do you get when you try "net use g: \\servername\sharename"

probably path not found.

 

[Draggon]

Originally posted by: spidey07
your netbios node type needs to be broadcast. It's listed at the top of ipconfig/all.

bingo.

I just checked the two Desktop machines. Both of them list the node as "Unknown", also. I've no idea how to enable broadcast or where to define the node.

Also, I assume all machines are on the 192.168.2.0/24 network?

Yes, Router = .2.1
Desktop1 = .2.2
Desktop2 = .2.3
Wireless1 = .2.5

(.2.4 is a wireless laptop that I've taken out of the loop while I'm troubleshooting)

I don't know what the "/24" part of your question means.

 

[spidey07]

something is definately not right if they are all set to unkown.

in order for it to find the resource it still needs to broadcast. I even believe a broadcast is used when you type \\ip address.

http://support.microsoft.com/default.aspx?scid=kb;en-us;314053#E0HE0ACAAA

on changing node type.

what is puzzeling is you can't access with \\ip - that means something is awry with your bindings and protocols. make sure that IP is the only protocol loaded

ipconfig/all and net config server/workstation from the other machines will help. that will tell me a bigger picture.

 

[Draggon]

Originally posted by: spidey07
heh, when troubleshooting MS networking you have to throw normal routine troubleshooting out the door. It just can't be done that way.

That's not very encouraging, spidey...

also, what error message do you get when you try "net use g: \\servername\sharename"

probably path not found.

On Wireless1, trying to access Desktop2, I get:

System error 64 has occurred.

The specified network name is no longer available.



On Desktop2, trying to access Wireless1, I get:

The command completed successfully.

 

[Draggon]

Originally posted by: spidey07
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053#E0HE0ACAAA

on changing node type.

Thanks for the link, I'll read up on that.

what is puzzeling is you can't access with \\ip - that means something is awry with your bindings and protocols. make sure that IP is the only protocol loaded

TCP/IP is the only protocol loaded on any of the three machines, and it's bound to both Client for Microsoft Networks and File and Printer Sharing in "Advanced Settings".

ipconfig/all and net config server/workstation from the other machines will help. that will tell me a bigger picture.

Here ya go:

DESKTOP1

IPCONFIG /ALL

Windows IP Configuration

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

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-11-09-DA-2F-42
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1


NET CONFIG SERVER

Server Name \\P-1
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{51568335-9B1F-4CB0-A94E-780EB759D49C} (001109da2f42)


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

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


NET CONFIG WORKSTATION

Computer name \\P-1
Full Computer name P-1
User name Ron

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{51568335-9B1F-4CB0-A94E-780EB759D49C} (001109DA2F42)

Software version Windows 2002

Workstation domain FAMDAMILY
Workstation Domain DNS Name (null)
Logon domain P-1

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




DESKTOP2

IPCONFIG /ALL

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-04-61-FE-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1


NET CONFIG SERVER

Server Name \\P-2
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{0BA3D71D-0F11-4972-8358-AB1011C11CED} (000461feffff)


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

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


NET CONFIG WORKSTATION

Computer name \\P-2
Full Computer name P-2
User name Ron

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{0BA3D71D-0F11-4972-8358-AB1011C11CED} (000461FEFFFF)

Software version Windows 2002

Workstation domain FAMDAMILY
Workstation Domain DNS Name (null)
Logon domain P-2

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

 

[spidey07]

what message do you get with net use \\ip\share?

 

[JackMDS]

I do not know what your system is used for and what level of sophistication you need in the sharing.

However Entry Level Networks based on peer to peer Windows Client OS? do the best if you bind both TCP/IP and NetBEUI, at their default setting, to the File sharing, and Map what ever you need to work with.

Successful Sharing involves some general consideration in Network settings, http://www.ezlan.net/sharing.html

As well as specific adjustment of each computer according to what is allowed to be shared. http://support.microsoft.com/default.aspx?scid=kb;en-us;304040

:sun:

 

[Draggon]

Originally posted by: spidey07
what message do you get with net use \\ip\share?

Wireless1 to Desktop2:

(after a looooong wait > 2 minutes)

The command completed successfully.


Wireless1 to Desktop1:

(immediately)

The command completed successfully.


Desktop2 to Wireless1:

(immediately)

The command completed successfully.


Desktop1 to Wireless1:

(immediately)

The command completed successfully.

 

[Draggon]

Originally posted by: JackMDS
I do not know what your system is used for and what level of sophistication you need in the sharing.

Just basic file access between machines and sharing one printer.

However Entry Level Networks based on peer to peer Windows Client OS? do the best if you bind both TCP/IP and NetBEUI, at their default setting, to the File sharing, and Map what ever you need to work with.

Yep, I've tried this, but the drive can't map, because Wireless1 just can't see Desktop2 no matter what I do (even with NetBEUI).

Successful Sharing involves some general consideration in Network settings, http://www.ezlan.net/sharing.html

Yeah, I've read many of the articles at ezlan.net over the last few days... As indicated when I connect Wireless1 with an actual CAT5 cable and sharing is then perfectly active, I'm very certain shares are set up correctly.

As well as specific adjustment of each computer according to what is allowed to be shared. http://support.microsoft.com/default.aspx?scid=kb;en-us;304040

Yes, I'll get deeper into specific permissions after I can get basic accessibility worked out.

Thanks for your reply!

 

[Draggon]

Just to try to eliminate one more thing that was bugging me, I powered down all three machines and switched the Router ports between Desktop1 and Desktop2 (D1 is now on Port 3 and D2 is now on Port 1).

After rebooting, there is absolutely no change in symptoms. Desktop2 and Wireless1 simply don't like each other at all! Desktop1 to and from Wireless1 still works great.

ARRGH!

 

[spidey07]

from your post "commnd completed successfully" you c@n sh@re?

 

[Draggon]

Originally posted by: spidey07
from your post "commnd completed successfully" you c@n sh@re?

That was the message at the command prompt. I don't know how to share in the command prompt environment, so I can't answer your question.

Were you asking me to try "net use \\ip\Sharename" from the Start/Run menu instead? If so, I hadn't tried that before.

 

[spidey07]

the drive is m@pped.

you're good to go.

 

[Draggon]

Originally posted by: spidey07
the drive is m@pped.

you're good to go.

Not quite. The success was not repeatable, and I still had major browsing issues between Desktop2 and Wireless1.

As a further troubleshooting step, I disconnected the new Belkin Pre-N router and reconnected my old D-Link DI-614+. After configuring everything back to the defaults (DHCP rather than static IP's, etc.), I tested out the network and EVERYTHING WORKS GREAT! ARRRGH!

Does this indicate a bad Belkin router, or does someone have an idea of some setting I can play around with in the router to try to get this thing working?

I truly appreciate everyone's help so far, and I'm really not trying to be a PITA.

 

[spidey07]

it's doubtful, but if you keep the clients ex@ctly the s@me @nd sw@p the router (de@ults) then it is b@d.

 

[Draggon]

Originally posted by: spidey07
it's doubtful, but if you keep the clients ex@ctly the s@me @nd sw@p the router (de@ults) then it is b@d.

Yeah, that's exactly what I've done. I put the Pre-N back into the system (not changing any client settings), reset it to factory defaults, changed only the items necessary to match my wireless settings (SSID, etc) and I get the same non-working system. As soon as I put the D-Link back, things work great.

I even went to the effort of calling Belkin's tech support (twice), and they keep trying to tell me there's nothing wrong with the router and the problem is in my client settings. Kept trying to get me to go to Microsoft's website and search File and Printer sharing. One of them finally told me to download the firmware update, which I did, but it won't "take". It gets about 1/2 way through the install and aborts. Time to send this thing back.