I would get a laptop and take it to where one of your desktops are located and take the network cable from the desktop and plug that into the laptop. Power up the laptop and see if what you are reporting happens with the laptop. If it does, shut the laptop down and take it to the server and plug a network cable to the closest switch to the server, power up the laptop and see if the issue happens again. If it does, you have a problem with the DHCP on the server, or routing issues. If it doesn't, and you get a proper IP Address, move to the next leg down the line and try again.
Process of elemination. If you don't have an issue with the laptop connected so close to the server, move to the next point and try. Then, when the problem happens again, you have found where the issue is. The switch may have a configuration issue. It could be cabling. It could be that the cable is running over/near a ballast running a light fixture. But, that's me and my $.02 Daniel On Thu, Nov 17, 2016 at 12:50 PM, Chad Leeper <[email protected]> wrote: > My DHCP servers live on the /24 network. Yes, I do have Helper IPs > configured. > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Don Ely > *Sent:* Thursday, November 17, 2016 10:27 AM > *To:* [email protected] > *Subject:* Re: [NTSysADM] Windows 7 asking for network after expanding > dhcp range form /24 to /22 > > > > Where does the DHCP server live? Do you have IP helper/DHCP relay > configured on the L3 interface for your new /22 VLAN? > > > > On Thu, Nov 17, 2016 at 8:01 AM Chad Leeper <[email protected]> > wrote: > > All, > > > > So when my network was originally created (Novell 3.x) the admin at the > time used a /24 address for static AND dhcp range. > > Fast forward 20 years and we are running out of addresses. I have kept > all static devices on /24 but, have setup a new dhcp scope on /22. > > We have Hp switches connecting everything and Ubiquity edge routers are > doing the heavy lifting. i.e. routing between vlans > > I am testing a few pcs now just to make sure everything is happy. > (untagging the new vlan on a few specific ports) > > Everything works as it should. BUT here is the rub…. > > > > When a test machine boots up the user cannot initially log in. (No logon > servers available) > > Logging in as local admin, selecting work network when prompted, then > disabling and reenabling the NIC gets the machine back on the domain > network with > > the correct IP from the new scope. Which is horrible to have to do for > each pc. > > > > I think I can get around it with some router trickery so that everything > comes in and goes out on the same interface but, that does not seem like > the most efficient. > > (The MAC address would remain in the same “bucket” for lack of a better > word.) > > > > Anyone been down this road before and have some words of wisdom? Windows > 2008 r2 domain, Win 7 pcs. > > > > Thanks, > > > > /Chad > > > > -- Daniel Rodriguez [email protected]
