Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7090
  • Last Modified:

XP domain clients can't browse network, but can ping by name or IP address

I'm running a SBS 2003 server with about 20 XP pro clients.

On most clients, I can't browse the network.  I either get: a blank window, the machine itself's shares, or a warning saying "network not accessable".

If I go into the "active" list for the WINS server on the SBS, I can see all the computers listed as active and their leases look normal etc.

Pinging by name or IP address seems to work ok too.

I'd love to be able to browse the network!  Any ideas?

Thanks,

CAL
0
telefunken
Asked:
telefunken
  • 4
  • 4
  • 2
1 Solution
 
Fatal_ExceptionCommented:
Do you have the WINs server in your ipconfig?  Although it is not necessary, you might try making sure that Netbios over TCP is turned on (WINs tab of TCP Advanced pane)...

Also, can you reach the network clients using the Run Line?  IPAddress and Computername?

Start > Run > \\ipaddress (or computername

Also, if any of your clients have a firewall turned on, this will prevent you from getting to them..  make sure you either disable the firewall, or make Exceptions for File and Printer Sharing..

FE
0
 
Jay_Jay70Commented:
did you use the connectcomputer wizard to join the computers to the domain? enabled Netbios?
0
 
telefunkenAuthor Commented:
The machine I'm using for testing is XP Pro (SP2) and has the following setup:
static IP, Microsoft's firewall with file sharing allowed, NetBIOS over TCP turned on, correct WINS server designated

I CAN access most other machines via the command line, using either IP or machine name.

I can also ping all machines and do NSLOOKUP on them.

The problem seems to be browsing only and most machines on the network share this problem.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
telefunkenAuthor Commented:

Jay,
Yes, I did use the connectcomputer wizard to join all clients.  

When you say did I "enable NetBIOS", do you mean on each individual machine or on the WINS server?  The PC I'm using for testing does have this enabled.
CAL
0
 
Fatal_ExceptionCommented:
If the problem is only with Network Places, then something is wrong with Netbios (or WINs)  

Might try flushing the Netbios cache:

nbtstat -RR

-RR  (ReleaseRefresh) Sends Name Release packets to WINS and then, starts Refresh
0
 
Jay_Jay70Commented:
good good, just checking on that wizard
0
 
telefunkenAuthor Commented:
Fatal_Exception,

I ran the nbtstat -RR but nothing changed.  When I run a "net view" from the command line I only get the name of the machine I'm using.

CAL
0
 
Fatal_ExceptionCommented:
Here is a link (Technet) to a good way to analyze TCP problems, including Netbios...  About half way down the page..

http://www.microsoft.com/technet/itsolutions/network/evaluate/technol/tcpipfund/tcpipfund_ch16.mspx#ECG
0
 
telefunkenAuthor Commented:
Fatal_Exception,

After reading the link you provided, I performed a "repair" on the network connection (LAN connection).  Nothing happened, at first, but I checked again about 15 minutes later and then I COULD browse the network and see all domain computers!

Thanks for the help,

CAL
0
 
Fatal_ExceptionCommented:
Great, and thank you..  :)

FE
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 4
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now