B
bill.herde
I have all W2K workstations with Office2K, Servers are 1 -W2K sp2 (fsmo) and
2 - 2K3. All are DC and GC, all run DNS. Exchange 2K3 on one of the new
servers. All was working well when all 3 servers lived in the same building
and subnet. Last week the W2K server moved to another building and got it's
address changed. The two networks are connected via hardware VPN. Host
records were added to DNS as needed and all servers resolve and ping fine.
Netdiag and DCdiag all report no problems.
After all that, here is the problem. Ehen users in either building open
outlook, the progam will open fine, then hang for a measured minute, then
proceed to work normally. There is no excess disk or network activity
during this time period. Nothing will cause this delay again once Outlook is
running, but can be repeated continually every time it is closed then opened
again.
Sure acts like a name resolution type problem, but I can not get any other
program to behave this way.
Confused
(e-mail address removed)
2 - 2K3. All are DC and GC, all run DNS. Exchange 2K3 on one of the new
servers. All was working well when all 3 servers lived in the same building
and subnet. Last week the W2K server moved to another building and got it's
address changed. The two networks are connected via hardware VPN. Host
records were added to DNS as needed and all servers resolve and ping fine.
Netdiag and DCdiag all report no problems.
After all that, here is the problem. Ehen users in either building open
outlook, the progam will open fine, then hang for a measured minute, then
proceed to work normally. There is no excess disk or network activity
during this time period. Nothing will cause this delay again once Outlook is
running, but can be repeated continually every time it is closed then opened
again.
Sure acts like a name resolution type problem, but I can not get any other
program to behave this way.
Confused
(e-mail address removed)