resolvco
asked on
Network Browser Errors and Odd Behavior
I'm helping a company from New Orleans with their Network. They have a mess. With that said, the PDC and BDC are W2k standard. They are also running 2 NT4.0 servers for a specific application that only runs there?! Then they are also running 2 2003 Standard Servers, one a file and print the other an Exchange 2003 server. The behavior is on one of the 2003 machines, the file and print server (2003 Standard). Everything looks good with it's NIC settings, DNS and WINs. I removed and then rejoined it yesterday to the Domain and it browsed correctly for the rest of the day, a couple of hours anyway, but today it's now saying it cannot browse the Domain and that it might not have permissions etc.
W2k PDC
W2k BDC WINs, DNS
W2003 Exchange 2003
W2003 File and Print
W2k Standard for Blackberry
W2k Misc.
W2k Misc.
NT4 for a Baan ERP
NT4 for Timberline
With the exception of the W2003 File and Print, all other computers can browse through Network Neighborhood.
All systems can Ping / be Pinged as well
At this Point I've looked at everything I know to look at.
Help, as always, would be Greatly Appreciated!
Thanks
W2k PDC
W2k BDC WINs, DNS
W2003 Exchange 2003
W2003 File and Print
W2k Standard for Blackberry
W2k Misc.
W2k Misc.
NT4 for a Baan ERP
NT4 for Timberline
With the exception of the W2003 File and Print, all other computers can browse through Network Neighborhood.
All systems can Ping / be Pinged as well
At this Point I've looked at everything I know to look at.
Help, as always, would be Greatly Appreciated!
Thanks
I'd double check your WINS settings. I had a case that was similar to this and the offending server had NETBIOS over TCPIP disabled.
ASKER
I Have Done a complete review of WINS and DNS and did not find a Problem
Maybe it's time to get off the server as the source of the problem. Plug your workstation into a different switch or port on your switch.
On your local workstation, check for spamware/viruses. Look in your LMHOSTS/HOSTS file for invalid entries as well: c:\windows\system32\driver
On your local workstation, check for spamware/viruses. Look in your LMHOSTS/HOSTS file for invalid entries as well: c:\windows\system32\driver
What happens when you are logged into the local workstation as the domain administrator?
Is it service pack 1. What errors does it report in the event log?
ASKER
The problem is the Server, not a workstation. I can browse the network with every other machine, just not this machine regardless of how I'm logged into it.
It's SP1
It's SP1
If you can browse the server and the network with every other workstation except this one, why do you think it is the server instead of the workstation that is the problem?
If the user id on the machine works properly from the other machines and not this workstation then it's the workstation. If the domain administrator can browse the network fine from this machine but the user id cannot then there is something wrong with the user profile on the workstation.
If the user id on the machine works properly from the other machines and not this workstation then it's the workstation. If the domain administrator can browse the network fine from this machine but the user id cannot then there is something wrong with the user profile on the workstation.
ASKER
The Admin account works wherever it's used
The original Problem that I posted a question about deals only with a server and not a workstation
No matter how I logon to the Windows 2003 Server, which is a File and Print server, I cannot browse the network using the Network Browser
Where are you getting workstations out of all of this?
The Network, and the Servers and Workstations in it are all fine with the exception of this one file server, Windows 2003 Standard Server SP1. Machines can see it, ping it and even get their files from it. The server can ping everything else on the network, regardless how I do it, Machine.Domain.com, Machine, 192.168.1.123. But it cannot browse the Network. I Click on the network Icon on the Server's desktop, double click entire network, double click on the domainName and it tells me it does not have permission to browse or access the domainName.
The original Problem that I posted a question about deals only with a server and not a workstation
No matter how I logon to the Windows 2003 Server, which is a File and Print server, I cannot browse the network using the Network Browser
Where are you getting workstations out of all of this?
The Network, and the Servers and Workstations in it are all fine with the exception of this one file server, Windows 2003 Standard Server SP1. Machines can see it, ping it and even get their files from it. The server can ping everything else on the network, regardless how I do it, Machine.Domain.com, Machine, 192.168.1.123. But it cannot browse the Network. I Click on the network Icon on the Server's desktop, double click entire network, double click on the domainName and it tells me it does not have permission to browse or access the domainName.
OOPs, sorry about that. I should have re-read the problem and had this mixed up with another. My bad. I apologize.
lame followup question: the server, rpc, workstation and other related services are started, right?
lame followup question: the server, rpc, workstation and other related services are started, right?
ASKER
No bad......I Appreciate your time and effort! Thanks!! Yep, those services all running. I've started to think about looking at the Master Browser. Using Dameware I was able to see the Domain Master Browser, the Master Browser and Backup Browser but they all look okay as well.
Went back to the server and tried again after removing Browser roles on a couple of Workstations to no avail. Except the error message also stated there was not a Duplicate name on the Network. Everyway I know to find a duplicate failed so I'm not sure where that came from.
GoofY!
And that's where I'm at. Still can't figure it out
Went back to the server and tried again after removing Browser roles on a couple of Workstations to no avail. Except the error message also stated there was not a Duplicate name on the Network. Everyway I know to find a duplicate failed so I'm not sure where that came from.
GoofY!
And that's where I'm at. Still can't figure it out
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check this out as well: http://support.microsoft.com/default.aspx?scid=kb;en-us;323357
ASKER
Yes I do have 2 NICs
ASKER
MMDCisco hung in there and gave me excellent ideas on what potentially to check for. So after his last question and my checking a few things because of that question I disabled the Second NIC which I had enabled for another issue, and it now works great! I would like an area though I can go to and see what causes that behavior.
So MMDCisco............Thanks
So MMDCisco............Thanks
Any time.