Link to home
Start Free TrialLog in
Avatar of adimit
adimit

asked on

Browser Service Windows 2003 and port flooding

When I run a network sniffer i get several of the following errors

Source: 192.201.0.16 (PC)
Destination: 192.201.0.63 (Switch)
Protocol: Browser
Info: Domain/Workgroup announcement <my domain controller name>

Source: 192.201.0.16
Destination: 192.201.0.63
Protocol: NBNS
info: name query, nb_illegal nescon(00)

Question: My domain controller is on a 192.203.x.x network
How does the 192.201.x.x  network know of the domain controllers existence

The PC whose address is 192.201.0.16 has a second NIC which is on the 192.203.x.x network

Question 1: How do I stop my domain controller from broadcasting to other subnets that are physically separate (no VLAN's configured, but each network has its own switches with no routers to other switches)?

Question 2: If I have hardcoded ip addresses how can i stop my dns from broadcasting? Should I use WINS on top of DNS? There are 12 PC's connected to the domain controller. I want to stop browser elections and browsing? If browsing stops are there any negative effects?

I also have problems where computers added to the domain take longer to ping the domain controller then computers on the same subnet that aren't added to the domain.


I am using layer 2 switches
ASKER CERTIFIED SOLUTION
Avatar of Justin Owens
Justin Owens
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of adimit
adimit

ASKER

forgive me but I am not sure of what you mean by UDP on port 137? I'm not an expert. The sniffer just told me that the brotocol is nbns and browser.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of adimit

ASKER

when you say server do you mean my domain controller?  My main concern is that a pc on one network knows about a domain controller on another. That's the problem i am trying to solve. I want to make sure that traffic for each physical lan doesn't go to another lan. no vlans are used. all networks are wired separately.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of adimit

ASKER

most pc's have two network cards. each network card goes to a different switch. aren't the different subnets suppose to separate traffic?
Avatar of adimit

ASKER

I believe the information is correct, but I was hoping for an answer to my last question because I equate a subnet to a vlan to a broadcast domain and I am a little confused.  I also expect that switches on physically different networks are the equivalent of a vlan.