C2k Help
Non-C2k Issues => Legacy Networks => Topic started by: Gerard on November 14, 2006, 01:54:55 PM
-
Been getting alot of machines freezing today on our rm 2.4 network
check the event log... been getting this dhcp error message.. its appeared about 16 times today on the log
any ideas? ,.... i have no idea what it means
is this whats causing all our machines to freeze? :cry:
[attachment deleted by admin]
-
Strange one - check this out however, as it might help:
http://support.microsoft.com/kb/284145
-
Hi Gerard
I get that message a lot on on old NT machine that I use to handle my DHCP addressing it never caused any problems like freezing pcs
One thing to check is that the little darlings have not connected your Legacy network and the C2k network together using a patch cable.
-
Gerard,
You arnt by any chance getting low on available IP addresses?
You might need to extend your scope.
-
Gerard,
You arnt by any chance getting low on available IP addresses?
You might need to extend your scope.
and how do i do that? lol
i should be alright cos we have done away with a suite of 24 machines so the RM network is getting smaller
but we have our new 2003 server shared across so that all the users only have the one username and home directory
could the problem be because of that?
-
Gerard,
To view your IP Scope statistics do the following:
Open Administration tools and fire up DHCP.
Right-click in the "server" icon (at the top of the tree)
and click on Display Statistics.
That will tell you (amongst other things) what percentage
of IPs have been used and whats left.
Not sure if thats your problem though, but its useful info
to have at hand anyway.
-
We have our new 2003 server shared across so that all the users only have the one username and home directory
could the problem be because of that?
Hmm yep. If you didn't update your legacy network DHCP settings to acommodate the C2K network I think you would have problems. Sharing users across both networks sounds pretty horrible to me in the first place and I am suprised that C2K allowed you to do that (maybe they didn't... :wink: ). Maybe all the C2K machines are using your Legacy server to acquire their IP address?
Try increasing the range of allowable IP addresses anyway to see if that works.
-
lol sorry i mis lead you there by "our 2003 server network" i means our legacy.... we upgraded 1 suite and a new server this summer of our legacy network.. nothing to do with c2k
-
oh ok - I probably read it wrong :oops:
I think the problem still lies with your DHCP server though - it must be configured wrong. Maybe a quick google of Server 2003 DHCP configuration may shed some light on the matter?
-
thanks .. ill give it a try later