Community archive

Ask something
Discussion Locked

Computer (Master) Browser Issues

0 helpful
10 replies

by karma1

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Background:
PDC - P200MMX, 96M RAM, NT Server 4.0, IIS 4.0, Proxy Server 2.0, 2 NICs.
NIC 1 - Dlink 220 - Cablemodem connection, TCP/IP, DHCP. Works fine.
NIC 2 - LinkSys Fast Ethernet - LAN connection to a LinkSys 5 port hub. TCP/IP, Static IP -192.168.0.1, 255.255.255.0

Client 1 - PIII-733, 256M, Win2k Professional
NIC - LinkSys FastEthernet to LinkSys Hub. TCP/IP, Static 192.168.0.2, 255.255.255.0

Client 2 - PIII-600, 256M, Win2k Professional
NIC - LinkSys FastEthernet to LinkSysHub.
TCP/IP, Static 192.168.0.3, 255.255.255.0

I'm getting 8003 errors on the PDC (Browse Master). I've tried modifying the Registry keys on all machines... (Services, Browser, Parameters) IsDomainMaster and MaintainServerList... I've used justabout every combination. I still receive these errors.
I've disabled the WINS Client on the DLink (internet) NIC.
I've been through all the articles I could find on the MS KB... and so far the problem hasn't been resolved.
Any and all help would be appreciated.

10 replies

by magetower

Since you are running a dual NIC configuration on the PDC you need to make sure you are not passing UDP traffic for ports 137 and 138 from one NIC to the other.

Because of the two NIC config your server is essentially acting as a router between the two subnets. By applying a filter to block the UDP traffic it may fix your problem.

by curacao_dejavu

I am posting the following artickles:
MS KB:
Article ID: Q135464
Article ID: Q143153
Article ID: Q224131
Article ID: Q188305

On the resourcekit there are 2 utillities to help troubleshooting browserserrors , if I recall correctly they are browsmon and browstat.

regards

Leopold

by karma1

Deja_Vu,

Thanks for the help, but as I mentioned before, I've been through the Microsoft Knowledge Base. I've viewed these and other articles before. They didn't resolve the problem.

by karma1

Thanks Magetower, but...

I have the WINS Client disabled on the Internet NIC. I also have an LMHOSTS file for NetBIOS resolution. However, the error is occurring regardless of these measures.
If you know of another method I may have overlookedin the manner of blocking those UDP ports, please let me know and I'll try again.

by magetower

Which NIC are the errors being generated from? (This should be indicated in the error messages.)

If they are coming from the external NIC then you can try this to see if it works:

Go into the properties for TCP/IP and click the Advanced buttonon the IP Address tab.

Make sure the external NIC is selected in the dropdown and then check the Enable Security box toward the bottom. Then click the Configure button.

Again make sure the external NIC is selected and select Permit Only over the UDP box (should be the center one). Leave the box blank and OK your way out of the settings. (You may need to reboot)

Again, this is only if the external NIC connection is the one generating the errors. This measure will block ALL incoming UDP traffic to your server so it may cause some problems with other programs that use UDP (but you'll be more secure :) ).

Your best bet for selective filtering of traffic would be to aquire a decent firewall program like Zone Alarm, Black Ice, or similar. Especially since you are connected by cablemodem (and thus presumed continously on-line and vulnerable).

WINS on the internal network should eliminate the need of the LMHOSTS file. Use one or the other but don't use both.

by karma1

Once again thanks, but no luck. I have found the problem. Oddly enough it was a defective NIC, the LinkSys, which was the internal NIC. It's quite odd to get this result from a faulty NIC, but once I replaced it with another 10/100 NIC, the problem went away.

by info-man-

You better have Service Pack 6a installed on your NT Server or your gonna have a compatibility issue with your 2000 workstations. This will solve your problem.
Try it. Let me know.

by karma1

SP6a was installed, if u read above, you'll find that the NIC itself was faulty. Oddly enough.

This discussion is closed to new replies.