-
October 16th, 2007, 03:46 PM
#1
One of the stranger things I've seen...
So I just installed a new exchange server (yeah, I know "my condolences"), sorry, work is work.
Anyway, I've been noticing a few 1054 event ID which usually indicates a DNS config issue, well needless to say DNS is straight, netdiag looks good, etc.
So I ping the domain to see how it responds.
This is what I get:
C:\Documents and Settings\Administrator>ping domain
Pinging domain.local [192.168.7.10] with 32 bytes of data:
Reply from 192.168.7.10: bytes=32 time=-148ms TTL=128
Reply from 192.168.7.10: bytes=32 time=-148ms TTL=128
Reply from 192.168.7.10: bytes=32 time=-148ms TTL=128
Reply from 192.168.7.10: bytes=32 time=-148ms TTL=128
Ping statistics for 192.168.7.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = -148ms, Maximum = -148ms, Average = 1073741676ms
Give me some love and tell me why this is occurring. I've done due diligence and have yet to find a good reason. I have various other servers attached the same way, same OS, patch level, config et al and I don't see them exhibiting this behavior.
peace
P.S. I'm not entirely concerned because it seems to function correctly, I just can't stand having any errors, at all.
Mankind have a great aversion to intellectual labor; but even supposing knowledge to be easily attainable, more people would be content to be ignorant than would take even a little trouble to acquire it.
- Samuel Johnson
-
October 16th, 2007, 04:05 PM
#2
Sorry...whats the version of the exchange server??
2003?? or 2007??
Dont mind me...I have the reputation of asking "dumbass" questions
I think it maybe a GP issue??
User Action
To troubleshoot the network connectivity or configuration problem, try one or all of the following:
In Event Viewer, click System, and check for any networking-related messages, such as Netlogon messages, that indicate a network connectivity issue.
At the command prompt, type netdiag, and note any errors. Those errors usually have to be resolved before Group Policy processing can continue.
At the command prompt, type gpupdate, and then check Event Viewer to see if the Userenv 1054 event is logged again.
To verify that the domain controller can be contacted through Domain Name System (DNS), try to access \\mydomain.com\sysvol\mydomain.com, where mydomain.com is the fully qualified DNS name of your domain.
Verify that you can access the domain controller by using tools such as the Active Directory Users and Computers snap-in.
Check to see whether other computers on your network are having the same problem.
If this computer is a part of a cross-forest domain, verify that the forest for the user account is currently available and can be contacted by the computer on which the Group Policy processing failed.
http://www.microsoft.com/technet/sup...renv&LCID=1033
MLF
How people treat you is their karma- how you react is yours-Wayne Dyer
-
October 16th, 2007, 04:29 PM
#3
No thats a good question to ask MLF dont worry.
Is there a more exact error message or is that all? Is there a certain time(s) this is happening?
-
October 16th, 2007, 04:39 PM
#4
Oliver's Law:
Experience is something you don't get until just after you need it.
-
October 16th, 2007, 04:43 PM
#5
muhuhahaha!!
Exchange 2003.
I've already verified Active directory users and groups works fine, gpupdate gives the 1054 error immediately.
I've read all the KB articles related to this and none of that needs fixing.
I can reach the sysvol.
No other servers are having this error, none. Not even close.
It happens with all the time.
Is it getting interesting yet?
P.S. I think it's the NIC drivers but they are correct and approved and it has all the latest patches. Or my other idea is that it's the Dual core AMD Opteron 2.6GHz.
Last edited by KorpDeath; October 16th, 2007 at 04:45 PM.
-
October 16th, 2007, 04:52 PM
#6
Sorry for the double post but SirDice, you rock!!! That's got to be it. I searched all over this morning for negative ping time and didn't come across this wiki. Thanks muchly and I'll be sure to return the favor when I can.
I'll update this if the fix works.
Thank again.
-
October 16th, 2007, 05:21 PM
#7
Wow...who would have thought processor???
I would think hardware...NIC, cabling, router...communication problem between server
makes sense though....
MLF
How people treat you is their karma- how you react is yours-Wayne Dyer
-
October 18th, 2007, 09:21 PM
#8
Hokay, So that patch did the trick, amazingly, no other issues to report. It's as slick as whale snot now. Thanks all and especially sirdice.
-
October 19th, 2007, 05:03 PM
#9
Good thing to know about AMD dual core processors...and that there is a patch
Who would a thunk?
MLF
How people treat you is their karma- how you react is yours-Wayne Dyer
-
October 21st, 2007, 01:25 AM
#10
MLF
I don't think you ask stupid questions. I have read lots of your replys and they all seem to be logical to me.
From experience, things have to be asked multiple times in order to establish the facts. Seems that the initial stated "facts" that a user reveals when seeking help aren't usually fact... sometimes.
Similar Threads
-
By |3lack|ce in forum Cosmos
Replies: 13
Last Post: April 28th, 2005, 09:41 PM
-
By unhappy in forum Microsoft Security Discussions
Replies: 12
Last Post: March 5th, 2005, 06:40 PM
-
By gore in forum Operating Systems
Replies: 2
Last Post: February 25th, 2005, 08:12 AM
-
By gore in forum Operating Systems
Replies: 3
Last Post: March 7th, 2004, 08:02 AM
-
By VenomFrogg in forum Cosmos
Replies: 8
Last Post: March 13th, 2003, 11:37 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|