RE: O/T more campus design issues [7:60136]

2003-01-02 Thread James Willard
Priscilla, You'll need to either have a domain controller on each segment or set the "ip helper-address x.x.x.x" on the DC-less interface on the router that's routing the two segments. In other words, if ethernet0 is on subnet 1 without a DC, and ethernet1 is on subnet 2 with a DC, place the comma

RE: O/T more campus design issues [7:60136]

2003-01-02 Thread Priscilla Oppenheimer
James Willard wrote: > > Priscilla, > > You'll need to either have a domain controller on each segment > or set > the "ip helper-address x.x.x.x" on the DC-less interface on the > router > that's routing the two segments. In other words, if ethernet0 > is on > subnet 1 without a DC, and ethernet1

RE: O/T more campus design issues [7:60136]

2003-01-02 Thread Mark W. Odette II
Simplest solution is to put a WINS Server on the Subnet that can't find the DC. Configure it to replicate with the DC on the other Subnet, or Statically configure the Domain Name entry for the NT Domain on the WINS Server in the troubled subnet. Your "DC Not Found" issue should be resolved then.

Re: O/T more campus design issues [7:60136]

2003-01-02 Thread Matthew Tighe
Actually, if there is no NetBios Name Server (WINS), all the clients will resort to broadcast (B-node) resolution (m-node, h-node) or simply fail (p-node). I'd recommend checking out the following Microsoft KB articles: http://support.microsoft.com/default.aspx?scid=kb;en-us;102725 http://support

Re: O/T more campus design issues [7:60136]

2003-01-02 Thread Priscilla Oppenheimer
I do know a lot about NetBIOS naming, but is this really a naming problem? They can't find the domain controller. Do they try to find it by name? I'll find out if there is a WINs server or if they are configured as b-nodes or other. I already asked the client that but didn't get an answer. But I'

Re: O/T more campus design issues [7:60136]

2003-01-02 Thread bergenpeak
If you only have hosts connected to the switch (not L2 devices), enable port-fast on the host ports. This eliminates the spanning tree states on the port and thus the port begins forwarding packets with a few seconds of the link coming online. This might be the problem if static IPs are assigne

Re: O/T more campus design issues [7:60136]

2003-01-02 Thread Priscilla Oppenheimer
bergenpeak wrote: Thanks. I always like hearing from you, bergenpeak. DHCP is working and the DHCP server is on the other net so we think inter-VLAN routing and the helper address are behaving and that STP forwarding delay isn't biting us. We tried having the helper address point to a broadcast j

Re: O/T more campus design issues [7:60136]

2003-01-02 Thread Matthew Tighe
My recollection is that a client will broadcast out for the DC and either the DC or the Master Browser for the subnet will respond with a name. Regardless, windows is heavily reliant on being able to resolve Netbios names. It is a definite possibility you should explore. You also may have a clien

Re: O/T more campus design issues [7:60136]

2003-01-02 Thread Matthew Tighe
One more item... If you implement a WINS server or specify a DC in the LMHOST file you may want to make sure the DHCP is specifying the node type as "H". It's one of the DHCP options on an NT DHCP Server. ""Matthew Tighe"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > My recol

RE: O/T more campus design issues [7:60136]

2003-01-02 Thread Joshua Vince
The setting is 0x8 for an H-node. Josh -Original Message- From: Matthew Tighe [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 02, 2003 7:37 PM To: [EMAIL PROTECTED] Subject: Re: O/T more campus design issues [7:60136] One more item... If you implement a WINS server or specify a DC

Re: O/T more campus design issues [7:60136]

2003-01-03 Thread William
Hi Priscilla Maybe you can try this: ip forward-protocol udp 137 ip forward-protocol udp 138 ip forward-protocol spanning-tree Best regards, William ""Priscilla Oppenheimer"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > bergenpeak wrote: > > Thanks. I always like hearing fro

RE: O/T more campus design issues [7:60136]

2003-01-03 Thread mjans001
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Priscilla, For startup (win 9x) you must put wins in place. The Netbios node type is covered in a prev thread. You can do a include statement in the client lmhosts file that refers to a lmhosts file at the DC for (example the netlogon share or on a r

RE: O/T more campus design issues [7:60136]

2003-01-03 Thread Symon Thurlow
All you need to do is configure the clients in the DC-less subnet to use a WINS server (anywhere, not necessarily in the same subnet) that has the required domain records. WINS servers hold more than just netbios-ip address tables, there are lots of different WINS record types. Here is a good lin

Re: O/T more campus design issues [7:60136]

2003-01-19 Thread cheekin
Hi Priscilla, You may want to try this if you have not solved the issue. Edit the LMHOST to add the following entry. a.b.c.d#PRE#DOM: The description of the #PRE and #DOM usage is in the lmhosts.sam file. Reboot the the computer to ensure that the entry is loaded into the