telefunken
asked on
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
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
did you use the connectcomputer wizard to join the computers to the domain? enabled Netbios?
ASKER
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.
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.
ASKER
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
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
Might try flushing the Netbios cache:
nbtstat -RR
-RR (ReleaseRefresh) Sends Name Release packets to WINS and then, starts Refresh
good good, just checking on that wizard
ASKER
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
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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
Great, and thank you.. :)
FE
FE
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