|
Question : XP admin machine not integrating well with Win2k environment
|
|
Howdy folks,
I've recently upgraded a single machine in our Win/Exch 2k domain to XP... this is the PC I use for network admin and all the juicy stuff...
Our network isn't without it's quibbles, so I'm not sure whether what I'm experiencing here is because of XP or some (mis)configuration on the network, but as far as I can say, this started with the XP upgrade...
The admin account I use is an Enterprise Admin, holding Domain Admin rights for our root and 3 child domains (I've checked memberships in AD and all appears to be A-OK)... however, with XP and Office 2003, I can't (for example) access someone else's mailbox... rather, I should say, SOMEtimes I can, but mostly I can't... it will often prompt me for a username/password, and even if I re-enter my creds, it will tell me it's unavailable... like I said, sometimes this works... or will work with 1 child domain and not others... or whatever it feels like NOT doing depending on it's mood!
Other curious things, like the DHCP console not letting me view the child domain servers ("access denied"), and issues expanding the servers in exchange admin...
Any suggestions would be much appreciated... one thing on my mind lately is that we currently don't have reverse lookup zones in our DNS servers, but everything really appears to work, and I didn't have these sorts of troubles when I was running a Win2k machine for admin... should I just go back to Win2k? Nah, I know we love to work through problems here, so I won't take the easy way out...
As these are all cross-domain problems, I'm also hoping it may reveal any probs we may have in our network as a whole, but like I said, everything generally runs fine so it's more "odd and annoying" than anything...
Cheers, Herb
|
Answer : XP admin machine not integrating well with Win2k environment
|
|
Check your dns numbers and make sure the first dns number is the ad server
|
|
|
|