OWA and Global Catalogue Server
Hi,
Is it possible to change the server that an OWA server talks to for its Global Catalogue services? We were in the process of mirgrating from 2000 DC to 2003 DC so moved the Global Catalogue Database to the new 2003 DC when doing this OWA stopped authenticating it's users. It turns out that our OWA which is in the DMZ has a firewall rule in place to allow it to talk directly to the old Global Catalogue server so now we have put the rule in the firewall to allow it to talk to the new global catalogue server how can I tell OWA to use the new server and not continue to use the old one?
Any help most welcome :)
Is it possible to change the server that an OWA server talks to for its Global Catalogue services? We were in the process of mirgrating from 2000 DC to 2003 DC so moved the Global Catalogue Database to the new 2003 DC when doing this OWA stopped authenticating it's users. It turns out that our OWA which is in the DMZ has a firewall rule in place to allow it to talk directly to the old Global Catalogue server so now we have put the rule in the firewall to allow it to talk to the new global catalogue server how can I tell OWA to use the new server and not continue to use the old one?
Any help most welcome :)
ASKER
The Exchange server which is inside the LAN and not in DMZ works fine, the problem lies with the OWA server which was joined to the domain when first built but now lives in the DMZ were it has not Domain access so I think the problem lies with the OWA server still using the Global Catalogue server that it was first setup with when it was joined to the domain. Because that server was no longer the Global Catalogue server it stopped working as soon as I changed it back it started working again.
So is there a way to change the Global Catalogue server address on a Windows 2003 server running OWA only?
So is there a way to change the Global Catalogue server address on a Windows 2003 server running OWA only?
Can you verify that the DMZ OWA server can reach the new DC on TCP 3268?
cmd -> telnet FQDN_New_GC 3268
(the cmd window should turn all black).
I assume both DCs are GCs. Verify:
Open Exchange System Manager
> Administrative Groups
> First Administrative Group
> Servers
> Right click the OWA DMZ server -> Properties -> Directory Access tab
Are both DCs listed as Type = GC?
cmd -> telnet FQDN_New_GC 3268
(the cmd window should turn all black).
I assume both DCs are GCs. Verify:
Open Exchange System Manager
> Administrative Groups
> First Administrative Group
> Servers
> Right click the OWA DMZ server -> Properties -> Directory Access tab
Are both DCs listed as Type = GC?
ASKER
Yes they can telnet to the GC on 3268 but it seems to only talk to the old GC as the rule on the firewall for port 3268 pointing to the new GC has zero hits on it..
ASKER
the old GC which I disabled is now back on line and acting as a GC and OWA is back up and working but I take it I dont have to move the OWA server back into the LAN and rejoing it to the domain so it picks up the new GC do i?
There is no need to move it to the LAN, but you'll have to make sure the OWA server can connect to the new DC/GC.
You should also make both DCs a GC.
You should also make both DCs a GC.
Did you verify the other steps in http:#37036377 ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
resolved
Verify that the new DC is listed on the RUS.
http://support.microsoft.com/kb/319065
See Step 5 under: How to Configure the Default Recipient Update Service Instances