Interesting Windows 2000 Issue

We have a client who runs a Windows 2000 ISA server (runs 2000 server and ISA 2000).  This server of course has 2 NICs, one for outside and one for inside.

Just a week ago, she said that when she came in, her NICs had lost their static IP address assignments and were showing the default IP assignment (169.x.x.x, you know what I mean).  Of course this means that the NICs could not get any DHCP addresses.

So she put the Static IPs back on, but here is the issue.  The ISA IP filtering logs show that UDP port 67 and 68 are being blocked (source IP of the server and dest. is the broadcast address) constantly, those ports are used for DHCP.  It appears that the NICs are still trying to get DHCP addresses?

My question first is, how is it that the NICs could lose their Static IPs like that?  The woman insists that there was no way anyone had access to the server over that weekend, so it must of been some kind of failure.

My second question is, why would it seem that the server is still trying to get DHCP addresses?  Has anyone come across this before?  These blocked packets only started appearing after the odd server error mentioned above.

Thanks for the input.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I am guessing, but I think your TCP/IP stack got hosed. My simple solution is remove TCP/IP from the server. Restart, Add TCP/IP back and reconfigure the NIC settings. I also highly recommend that if you don;t have the complete settings written down somewhere you do that as soon as possible.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TheTullAuthor Commented:
Not a bad idea, I also assumed something corrupt happened with the windows side of things, whether the TCP/IP stack froze up or what.  I would still like to know for sure what caused it, but we may never find out.
If it is some kind of hardware cause corruption, you might want to scandisk the HD. Another thing you might want to do is reinst sp4 to make sure core files arnt corrupt.

Any luck resolving this?
TheTullAuthor Commented:
Well, I left the problem in the hands of the original IT person working on it.  And actually I took a new job, so I won't even be able to work on that issue if I wanted to, but thanks for the help, I will distribute the points.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.