Protocol? Nah, more like a simple resolution issue. The obvious is configured right such as DNS, and your not using a split model and having the server resolve the dns name erroneously outside for example? jlc
From: Bob Peitzke [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2008 6:51 PM To: NT System Admin Issues Subject: RE: New server can't see domain It's a member server. Sorry, shoulda made that clear. Removed it from domain, but can't rejoin domain as it cannot see it. Seems like a protocol glitch. - Bob ________________________________ From: Stephan Barr [mailto:[EMAIL PROTECTED] On Behalf Of lists Sent: Wednesday, July 09, 2008 5:30 PM To: NT System Admin Issues Subject: RE: New server can't see domain What does your local DNS show regarding the new server? What do DCDIAG and NETDiag tell you? What do the DCs logs tell you about the new server? Easy thing to do first is disjoin and rejoin the domain as long as it's not already a DC. Logs will tell you the problem. Cheers. ________________________________ From: Bob Peitzke [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2008 7:25 PM To: NT System Admin Issues Subject: New server can't see domain I set up a new Win2K3-R2 server recently and while it can ping & respond, it can't see the domain. I dissolved the NIC team and assigned static IP to NIC 1, no change. I noticed that in the LAN connection properties Client for MS Netowrks and F&P Sharing are unchecked. When I check them it pops up a box saying, "Your current selection will also disable the following components: (and lists these two). DISable, but I checked them to ENable !!! No relevant events. I'm about ready to blow it away & reinstall, unless anyone has any suggestions. It's a ProLiant DL380-G2, updated with Firmware Maint 8.0. Bob Peitzke Senior IT Manager Colony Advisors, LLC ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
