Link to home
Start Free TrialLog in
Avatar of texastwostep
texastwostep

asked on

numerous event log warnings - can someone help me decipher? Ack!

Windows Server 2003.  Already rebooted and restarted some of the services.  Messages appearing in Event Viewer > System

WARNINGS:

1. Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source.  It is recommended that you either configure a reliable time service in the root domain, or manually configure the PDC to synchronize with an external time source.  Otherwise, this machine will  function as the authoritative time source in the domain hierarchy.  If an external  time source is not configured or used for this computer, you may choose to disable  the NtpClient.

3. Your computer has automatically configured the IP address for the Network Card with network address 0010181446D7.  The IP address being used is 169.254.133.139.

4.  Broadcom NetXtreme Gigab: The network link is down.  Check to make sure the network cable is properly connected.

5. The reason supplied by user SCDTX\Administrator for the last unexpected shutdown of this computer is: Other Failure: System Unresponsive
 Reason Code: 0x8000005
 Bug ID:
 Bugcheck String:
 Comment:

Thanks!  Super freaking!

Thanks,

texastwo
Avatar of jcdesign4u
jcdesign4u

There is something wrong with your network connection (because you gat a manufacter ip adress 169.254.133.139.
).

Try the following:
* Check your network cable (is it plugged in correctly)
* check your dhcp server or your static ip adress
* try a new network card (maybe the old is broken)
Seems like firewall security problem

Do you have a Sygate firewall
Avatar of texastwostep

ASKER

tried both these things, they are in working order.  tried different cables, diagnostics on network card (plus our network is up and running) tried different outlets, etc.  any more suggestion *very* welcome.  thanks.
Do you have dual NICs on this server.

What is the result of "ipconfig /all".

Do you see a valid ip address for any of the NICs.

NTP error is normal. All you need to do is to specify a NTP time source, so that server can syncronize its time with. Leave it for a while, you can set it after you have network connectivity.

Can you ping other devices in your network.
Do you have a Sygate firewall
Avatar of Rob Williams
The 169.254.x.x address is assigned by the computer itself using APIPA when it requests, but cannot obtain, a DHCP address from a DHCP server. This would imply, as others have suggested, that the is a bad NIC, connection, DHCP server etc. The bigger question is why is your server trying to obtain a DHCP address. Servers should be configured with static addresses. Has something changed?
weird.  our IP address isn't 63.254.x.x etc.  doesn't even start with those #s.
Any Windows system that cannot find a DHCP server will assign itself an IP of 169.254.x.x   It is a designated subnet for this and is not related to your own DHCP server configuration.

Was your server IP static before?
Did you used IPconfig /all and get that IP address.

Prashax

Do you have dual NICs on this server.
Yes, just disabled one (after posting this message).

What is the result of "ipconfig /all".


Do you see a valid ip address for any of the NICs.
Yes

NTP error is normal. All you need to do is to specify a NTP time source, so that server can syncronize its time with. Leave it for a while, you can set it after you have network connectivity.
It appears that our time source is set to our internal hard drive.  is this okay?  leave it? or do i need to do something else with

Can you ping other devices in your network.
Yes
ASKER CERTIFIED SOLUTION
Avatar of prashsax
prashsax

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial