[phazei]

We have a network with about 20 computers. Before last weekend everything worked fine.
Now when I click "view workgroup computers" I get "the network path was not found" error on all computers.

If we type the computer name in the explorer address bar eg "\\computer\" it works just fine and all ip's are pingable.
Shared printers are still working, but if I search for network printers, it won't list the computer names.

DHCP is enabled running DNSMasq and all computers are on the same subnet. We're running DD-WRT with multiple ip's coming in and special iptable routing. All that works fine.

NetBIOS is enabled, File and Printer Sharing is enabled, everyone is on the same workgroup. Windows Firewall is disabled on all PCs.

Active and DHCP client tables show all computer host names properly.

We never had a WINS server.

I have no idea what's wrong.

help?

Thanks

Adan

 

[johnwill]

Your missing your Master Browser, that's the behavior you'll see.

Download LANScanner from this site: Scottie's Tech.info and run it. My guess is it'll find no master browser.

 

[phazei]

All the systems on the network are XP and there is no domain, only a workgroup.

How does the master browser get delegated? If I rebooted all the computers there, would one randomly get selected when they hit the network? Can there be a conflict? I take it if any computer is alone on a network, it always selects itself as the master browser.

I'll run that program as soon as I get to work in the morning and see what it says.

EDIT:
Found this:
http://support.microsoft.com/kb/188001
which was informative.

 

[phazei]

Ok, I ran LANscan and this was the results:

LANscanner v1.3 - ScottiesTech.Info

Scanning LAN...

System error 53 has occurred.

The network path was not found.


Press any key to exit...

When I ran it on my pc at home, it also gave that system error 53, but then it listed my one computer and said it was master. Here I got nothing...

Though even "ping computer-name" works between systems.

 

[johnwill]

That's really odd, try running that on another computer on the network. I've run it on a number of computers, it works fine on all of them!

 

[phazei]

I tried LANscan on a few systems now and got the same thing.
Also "net view" gives the same "system error 53"

Besides pinging the netBios name, I can also ping and access the network with the dns suffix:
ping computer-name.local.suffix.com
or
//computer-name.local.suffix.com/

 

[johnwill]

Check that all your network services are Started:

• COM+ Event System (for WZC issues)
• Computer Browser
• DHCP Client
• DNS Client
• Network Connections
• Network Location Awareness
• Remote Procedure Call (RPC)
• Server
• TCP/IP Netbios helper
• Wireless Zero Configuration (XP wireless configurations only)
• WLAN AutoConfig (Vista wireless configurations only)
• Workstation

Note: You can check the services in Control Panel, Administrative Tools, Services.

All of these services should be started, and their startup type should be automatic (or perhaps manual).

If a service is not running, open it's properties and check the dependencies. Check each of the dependencies and see which one is preventing the service from running. Checking the event log is also a good idea here, there may be clues to what is failing.

 

[phazei]

All those services (except WLAN AutoConfig) are auto or manual and all are started.

Also "net use \\pc\folder" works fine with netbios name/dns name/ip

"net start" results:

These Windows services are started:

Application Layer Gateway Service
Application Management
Ati HotKey Poller
Automatic Updates
avast! Antivirus
Background Intelligent Transfer Service
BarTender System Service
COM+ Event System
Commander Service
Computer Browser
Cryptographic Services
DCOM Server Process Launcher
DHCP Client
Distributed Link Tracking Client
DNS Client
Error Reporting Service
Event Log
Fast User Switching Compatibility
Help and Support
HID Input Service
IPSEC Services
Logical Disk Manager
Network Connections
Network Location Awareness (NLA)
Plug and Play
Print Spooler
Printer Maestro
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry
Secondary Logon
Security Accounts Manager
Security Center
Server
Shell Hardware Detection
SmartSVN Status Cache
SSDP Discovery Service
Symantec Core LC
System Event Notification
System Restore Service
Task Scheduler
TCP/IP NetBIOS Helper
Telephony
Terminal Services
Themes
WebClient
WebDrive Service
Windows Audio
Windows Firewall/Internet Connection Sharing (ICS)
Windows Image Acquisition (WIA)
Windows Management Instrumentation
Windows Time
Wireless Zero Configuration
Workstation

The command completed successfully.

 

[phazei]

I should note that some of the computers are almost never turned off. Everyone here just leaves their system running when they leave. I have rebooted a few, but some haven't been rebooted in a long time. I could get everyone to reboot all at once, but it could be difficult to get them all to do that at once.

Shoot, actually I was thinking, we do have Win2003 on our server. I was thinking that was on a different subnet, but it only has separate iptable rules so it has it's own dedicated external ip and static routing, the internal ip is on the same subnet. It hasn't been rebooted in years, it's running our Dynamics GP and runs/integrates all orders for our website.

 

[phazei]

net view and LANscan work on W2K3, but it only lists itself and our voip phone server, which are the only 2 systems on static ips and in their own workgroup different from the workgroup all the XP computers are on. It says the W2K3 is the master browser. But I don't think that matters since it's not the same workgroup...

 

[2xg]

Maybe a Server Reboot is all you need. I give all our Servers a little break every couple of months.
I would do a power cycle on you modem and router too, it might help.

 

[phazei]

I will need to schedule a reboot sometime in the next few days, hopefully that will do it.

 

[johnwill]

There is no server in this network, it's simply a workgroup, right? If there's a server, I'd recommend enabling the WINS server.

 

[phazei]

There's no server in this workgroup, there is another workgroup with Windows Server 2003 running MS Dynamics GP.

 

[2xg]

It looks like you have 2 diff networks, 2 diff Subnets I suppose. Those 20 Workgrp computers are not connected at all to the Server correct? You shd reboot all the computers as well.

Pls give us an update.

 

[phazei]

I rebooted all the computers in the main workgroup today, still getting network not found error.

The W2K3 server is on the same subnet, different workgroup. I can't reboot the server until the weekend.


Just to be clarify:
W2K3: static 10.0.0.100, workgroupB
everything else: DHCP 10.0.0.102-10.0.0.142, workgroupA

 

[johnwill]

Since they're all on the same subnet, why don't you use automatic addressing and then the server will be the browse master?

 

[phazei]

The server has to be static. It has it's own dedicated external ip, all the other systems on the network share a different external ip. Lots of stuff would break if it's not fixed, many different systems, internal and external, talk to it.

 

[johnwill]

Servers are typically statically addressed, this isn't really non-standard. If some of the workstations are connecting to the server, obviously it's internal address is on the subnet, right?

 

[phazei]

Yes, the internal address is on the same subnet. I'm going to be rebooting the server tonight.

On any of the machines if I disconnect them from the network and run "net view" it gives no errors.