It sounds to me like the workstations that suffer from this problem have access to more than one DHCP server, and that one of them are configured with wrong subnet information. Also, check to see if the configured scopes are large enough for all clients. You might have a DHCP server running on a box that you were not aware off. Hth, Ole ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ole Drews Jensen Systems Network Manager CCNA, MCSE, MCP+I RWR Enterprises, Inc. [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ http://www.RouterChief.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NEED A JOB ??? http://www.oledrews.com/job ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----Original Message----- From: Christopher Supino [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 26, 2001 4:24 PM To: [EMAIL PROTECTED] Subject: OT: NT DHCP Clients receive incorrect Subnet Masks and No [7:21218] All, This is off-topic, but I have been up against this issue with one of our customers for quite awhile, and I am accessing any avenue possible to get it solved. We have a customer that is running a distributed NT domain. The topolgy is as follows: Core location: Core Switch/Router is Alcatel ATM OmniSwitch (the ATM WAN backbone was integrated by a third party provider, who also is the ISP), which terminates 10mb ATM WAN connections from 8 remote locations, and also provides a 100mb PVC for the Internet. This switch is wearing many hats, as it is the "router" (layer three switch) for these 9 sites, as well as the internet router. As well as ATM connections(8 for remote sites, 1 for Internet), there are 2 active FE connections on this box. One feeds the local LAN (10.1.0.0/16), the other is attached to a PIX box (public address on PIX outside interface to public address on OmniSwitch FE interface routed via ATM PVC back to provider CO through). This configuration is actually a bit kludgy, but it works because the web clients point to a proxy server that sits behind the PIX box. On the LAN at the core location are a bunch of file servers, including the PDC for the domain. This server also performs DHCP for the core location. Distribution switch is a Catalyst 6000, single vlan, and the access layer is 35xx switches. The PC's are Dell OptiPlex models. Remote Sites: Alcatel OmniAccess Switches, falling back via ATM to core location, single ethernet port handing off to LAN. LAN consists of Cisco 35xx switches, and a BDC at each location, providing DHCP and print services. Remote LANS are addresses 10.2.x.x-10.9.x.x/16. HERE IS THE PROBLEM: Frequently, client will receive an improper subnet mask and other incorrect DHCP information at boot-up. The address is correct for the clients scope, but the mask is a class A rather than class B. Also, client sometimes experience login problems, and some users are unable to change their password over the network. The DHCP server listed is correct. These problems are evident at both the core site and the remote locations. Has anyone ever experienced anything similar to this, and if so what was the solution. Any help would be appreciated. Chris Supino Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=21222&t=21222 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
