Re: The name could not be resolved...

2008-07-18 Thread MarvinC
Looks like rebooting my 2nd DC/GC resolved the issue as I'm now able to create the profile and send a test message to the outside. Thanks for the responses. On Sat, Jul 19, 2008 at 12:46 AM, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > Sometimes to get the event log information you need, you

re: The name could not be resolved...

2008-07-18 Thread [EMAIL PROTECTED]
Sometimes to get the event log information you need, you have to increase diagnostic logging. In this case, the Recipient Update Service is probably not performing its duty. You could try increasing logging on the MSExchangeAL | Address List Synchronization and then manually forcing RUS to upd

Re: The name could not be resolved...

2008-07-18 Thread MarvinC
Will do. thanks On Sat, Jul 19, 2008 at 12:26 AM, Thomas W Shinder <[EMAIL PROTECTED]> wrote: > Hi Marvin, > > > > You really need to head on over to www.isaserver.org. This is a well worn > scenario that we've covered over a dozen times. Everything you need to know > is there. Just read the do

RE: The name could not be resolved...

2008-07-18 Thread Thomas W Shinder
Hi Marvin, You really need to head on over to www.isaserver.org. This is a well worn scenario that we've covered over a dozen times. Everything you need to know is there. Just read the docs and enjoy a working FE/BE scenario. HTH, Tom Thomas W. Shinder, M.D. || Microsoft Security Arc