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 cache. You can confirm this by executing this command at the command prompt: nbtstat -c Your description of the problem is similar to what I experienced 3 years ago while supporting NT 4.0 Workstations. We have DNS and WINS server setup at each remote location but the mobile users were unable to logon to their DC when they were out of their offices. HTH, cheekin Priscilla Oppenheimer wrote: > 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 just in case that > would help Windows. It didn't break DHCP but it didn't help Windows either. > ;-) > > Most things are working, just not Windows. Luckly the customer is a Windows > type, unlike me, so we'll get it working hopefully. > > THANKS! > > Priscilla > > >>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 assigned to the >>hosts. If DHCP is being used and DHCP is working, I'd expect >>it is not a problem with the port and spanning tree. >> >>One other possible gotcha is regarding routing and the VLAN >>interface. >>If no devices are active on the VLAN, the router might consider >>the >>VLAN subnet "down" and withdraw the route from its >>advertisements. >> >> >> >> >> >>Priscilla Oppenheimer wrote: >> >>>You all remember my very simple campus network re-design that >> >>I've been >> >>>helping out with? It sure has been keeping me humble. ;-) >>> >>>So we upgraded the single subnet to two subnets and two VLANs. >>> >>>Everything is working OK except for Windows networking. The >> >>PCs on the new >> >>>subnet can't find a domain controller for authentication. >>> >>>So, you can feel free to yell at me for not gathering more >> >>information on >> >>>the symptoms, but the client hasn't told me much. ;-) But >> >>does this ring a >> >>>bell with anyone? Are there standard recommendations on how >> >>to handle this >> >>>in a subnetted VLANed internetwork. >>> >>>I'm not too well informed on Windows networking. My co-author >> >>wrote that >> >>>chapter in my troubleshooting book. >>> >>>Thank-you so much! >>> >>>Priscilla Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=61341&t=60136 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
