ok, I set the primary DNS as 192.168.2.3 and the secondary blank, it seems to not have helped my issue really at all though unfortunately. Any ideas to what could be causing all this?
so what should be used as my secondary dns? am I wrong to have an external as secondary and the server as primary? I haven't tried removing the pc from the domain and re adding it primarely because it isn't limited to one machine, it is a problem with any new profile created in AD so I figured...
I changed it to have the primary as 192.168.2.3 and secondary as 216.165.129.158, flushed the dns on the server as well as the workstation and still no go. One thing I did notice however...one of the first things I tried was to give another user local admin rights on my machine, when I went in...
well, it stores our profile so if we need to use a different machine it will all pull in properly, plus the global address list an so forth, it definately serves a purpose.
They do appear in GAL but since I can't get them to connect to the exchange server I can't recieve them obviously, I imagine it is out in their mailbox somewhere. What do you mean by OWA?
yeah, I know it isn't ideal, I enherited the network:( as far as the logs are concerned, nothing new since the ones I listed in the 3rd comment above.
Do you agree that I should rebuild the recipient update services?
we are a small, one server operation, so the domain controller is the server that also acts as the exchange server. it is up to date with everything and yes, I back up the exchange server regularly.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.