Does anybody know where I can find instructions on how to move my NT 4.0 network from public to private IPs? No PCs will pick up an IP from the new DHCP scope.
thanks in advance, chachi
Please provide more details. It sounds like you want to change the client IP addresses.
How many clients do you have?
If the clients were configured to use static IP address, you will have to visit each client machine and configure the TCP/IP properties for DHCP.
Is you DHCP server on the same network segment? Maybe there is something blocking the DHCP server from reaching the clients. Remember, you have to bootP enabled routers if your clients are located on the other side of the router (If you don't have bootp enables routers, use DHCP relays to make your DHCP environment work.)
-hope this helps.
Joseph L. Poandl
MCSE 2000
If your company is in need of experts to examine technical problems/solutions, please check out
My network consists of about 100 Windows 98 PCs and about 30 Macs. The PCs and Macs are on separate subnets with a router in between. We are using DHCP (no static IPs except for the servers) and a public IP range, but we're trying to move to 10.x.x.x. When we turn off the public scope and try to start a Win98 PC and log in, it won't take a 10.x.x.x IP, it will only say something about not connecting to DHCP (I never saw the exact message, sorry). We don't want to remove the scope from the registry because we're only testing at this point, but maybe that's causing the problem.
Huh, I see what you are saying. I guess you have already tried a WinIPCFG and "release" then a "renew"... if not, give this a try on one of the client machines.
How bout this...
I don't think you should have active leases when you remove the scope...
I think you should start by deactivating the scope until all client leases expire or all client lease extension requests are denied.
Once there are no more active leases contained in the scope, you can remove the scope by selecting the scope under DHCP Servers and choosing Delete on the Scope menu.
At the same time....
...I think you should also add another NIC to the DHCP server. You may need this so that the server can belong to two different segments at the same time. Create the new scope and activate it. check this Technet Article out:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.