• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3037
  • Last Modified:

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
0
texastwostep
Asked:
texastwostep
  • 3
  • 3
  • 2
  • +2
1 Solution
 
jcdesign4uCommented:
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)
0
 
ded9Commented:
Seems like firewall security problem

Do you have a Sygate firewall
0
 
texastwostepAuthor Commented:
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.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
prashsaxCommented:
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.
0
 
ded9Commented:
Do you have a Sygate firewall
0
 
Rob WilliamsCommented:
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?
0
 
texastwostepAuthor Commented:
weird.  our IP address isn't 63.254.x.x etc.  doesn't even start with those #s.
0
 
Rob WilliamsCommented:
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?
0
 
prashsaxCommented:
Did you used IPconfig /all and get that IP address.

0
 
texastwostepAuthor Commented:
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
0
 
prashsaxCommented:
NTP is network time protocol.

It is used to syncronize time for your server with Atomic clocks.
There are servers on internet who act as NTP server and you can use them for free to syncronize your time.
e.g time.nist.gov

You can use this command to set the NTP server.

net time /setsntp:time.nist.gov

Just make sure you can access time.nist.gov from this server on port 123.(check firewall rules)

Now, you see a valid IP address for your current NIC.
You can browse your network and connect to other servers and devices.

 Do you see any more errors regarding limited network connectivity on the current network card.

0
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 3
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now