Hi,
We have two subnetworks separated by a Cisco router. The router runs two Ethernet points, one per subnetwork.
The Domain Master Browser is in Subnetwork A. The Domain Master Browser (PDC) is also the master browser for A.
In subnetwork B, there is a master browser.
We have been getting the EventID 8003 errors on the PDC and I looked it up on the Cisco and also the Microsoft KnowledgeBank sites and saw the remedy for this. I have disabled IP FORWARD for UDP ports 137 and 138 on the Cisco router.(For the broadcast packets on subnetwork B would not be passed through to Subnetwork A - we have the IP HELPER-ADDRESS enabled since we have a DHCP server in Subnetwork A).
This worked for 1 week, that is, I could see the full browselist from both the master browsers (in both Subnetwork A and B). In other words, the Domain Master browser is replicating the other parts of the browselist to the Master browser in Subnetwork B, and the master browser is sending it's own subnetwork browselist to the Domain Master browser.
We had some trouble with one of our domain BDC, so we took the 2nd BDC off the network. Then the browselist stopped working. Subnetwork A seems to only contains its own browselist, and subnetwork B has its own browselist.
Since then, our PDC seemed to be acting funny. Some users can't log only the network. When we re-synchronise the PDC, users then seemed to be able to log on. I am wondering whether the browsing problem we have has anything to do with this... (PDC getting out of sync?)
Correct me if I am wrong, the exchange of Browselist occurs using TCP protocol via port 139?
Has anyone got an idea what went wrong?
I also have another query. When filtering both 137 and 138 ports for UDP traffic. I can't seemed to use USer Manager for Domain, DHCP managers on subnetwork B. The DHCP server and also the User Manager for Domain resides on the PDC (that is, also the domain master browser).
I hope someone would be able to shed some ideas as to what is going wrong.
Thanks!
Regards,
Elizabeth
We have two subnetworks separated by a Cisco router. The router runs two Ethernet points, one per subnetwork.
The Domain Master Browser is in Subnetwork A. The Domain Master Browser (PDC) is also the master browser for A.
In subnetwork B, there is a master browser.
We have been getting the EventID 8003 errors on the PDC and I looked it up on the Cisco and also the Microsoft KnowledgeBank sites and saw the remedy for this. I have disabled IP FORWARD for UDP ports 137 and 138 on the Cisco router.(For the broadcast packets on subnetwork B would not be passed through to Subnetwork A - we have the IP HELPER-ADDRESS enabled since we have a DHCP server in Subnetwork A).
This worked for 1 week, that is, I could see the full browselist from both the master browsers (in both Subnetwork A and B). In other words, the Domain Master browser is replicating the other parts of the browselist to the Master browser in Subnetwork B, and the master browser is sending it's own subnetwork browselist to the Domain Master browser.
We had some trouble with one of our domain BDC, so we took the 2nd BDC off the network. Then the browselist stopped working. Subnetwork A seems to only contains its own browselist, and subnetwork B has its own browselist.
Since then, our PDC seemed to be acting funny. Some users can't log only the network. When we re-synchronise the PDC, users then seemed to be able to log on. I am wondering whether the browsing problem we have has anything to do with this... (PDC getting out of sync?)
Correct me if I am wrong, the exchange of Browselist occurs using TCP protocol via port 139?
Has anyone got an idea what went wrong?
I also have another query. When filtering both 137 and 138 ports for UDP traffic. I can't seemed to use USer Manager for Domain, DHCP managers on subnetwork B. The DHCP server and also the User Manager for Domain resides on the PDC (that is, also the domain master browser).
I hope someone would be able to shed some ideas as to what is going wrong.
Thanks!
Regards,
Elizabeth
