charlesAMAG
asked on
Windows Server 2003 not sending/ 3COM superstack 4200 not recieving DHCP address pool
I have windows server 2003 with DHCP configured, scope configured and suthorized and 3COM superstack 4200 switch configured to automatically run DHCP if there is a DHCP server connected to it.
The server is connected to it, but none of the addresses in the pool are being used. When I check my IP I'm pulling a default ip from the stack like there's no DHCP.
I know there's probably a simple option somewhere that I need to toggle but I'm not finding it...
The server is connected to it, but none of the addresses in the pool are being used. When I check my IP I'm pulling a default ip from the stack like there's no DHCP.
I know there's probably a simple option somewhere that I need to toggle but I'm not finding it...
ASKER
switch rebooted... still not using DCHP addresses...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
any vlans setup on the 3com?
ASKER
I changed out to a smaller switch and had the same issue so perhaps the DHCP server is not responding to requests... But I cannot see why that would be...
can you go into dhcpmgmt.msc and expand the server then take a screenshot, are you familiar with windows dhcp servers?
ASKER
And nope, no vlans
ASKER
Well, I'm not sure what happened but suddenly it works. Apparently it needed to be unplugged and plugged back in. Which is odd because I've brought down the switch a dozen times and you'd think that would do the same thing as plugging and unplugging... ah, well.
Thanks for your solution though, it totally worked.
Thanks for your solution though, it totally worked.
contact a DHCP server on the network requesting IP information from the
server. The attempts are at 0, 4, 12, 28 second intervals.
If the DHCP process fails after 30 seconds on all four attempts, then
the Switch activates its Auto-IP configuration feature.
The Auto-IP feature starts with an IP address of 169.254.100.100.
Did you turn the switch on before the scope was activated? try rebooting the switch...