whoam
asked on
Copy to Sysvol Very Slow
When I copy to the sysvol, a file takes ~3minutes to copy, where as if i copy to a DC in the site via \\server\sysvol\domain\, it takes ~10 seconds. I don't see replicaiton errors in the logs. I have looked over assignment of subnets in sites and services and it looks to be good. This is a new occurance. Until about a month ago, copying to the sysvol was just fine.
Domain & Forest are 2003 function level
8 sites, the site in question has 3 DCs.
Domain & Forest are 2003 function level
8 sites, the site in question has 3 DCs.
Have you created subnets in AD Sites and Services and assigned them to the correct site?
ASKER
snusgrubben,
Yes, I have thanks.
Yes, I have thanks.
So I can assume the IP to the spesific server, has a subnet defined in AD S&S?
Do all clients have this delay copying to SYSVOL?
Do all clients have this delay copying to SYSVOL?
ASKER
No, clients okay, in fact doing some testing I find that
1. it's only one server that exhibits this behavior that I have found so far.
2. I have found that DC that the trouble server considers authoritative for the sysvol. The problem server and it's preferred DC are in different sites.
3. The logon server of the trouble server is in the same site with the trouble server, but it isn't looking to it for sysvol queries.
Let’s say site 1is the main site and site two is the distant site
Server A is ‘the trouble server’. Server B is the DC listed by Server A is it’s logon server when I log in. Server A and B are in site 1. Server C is the DC in site 2. Server B is looking to server C for sysvol queries. Very odd. The subnets folder in AD S&S is populated with my subnets and they are assigned to sites. Sites list their correct DCs.
1. it's only one server that exhibits this behavior that I have found so far.
2. I have found that DC that the trouble server considers authoritative for the sysvol. The problem server and it's preferred DC are in different sites.
3. The logon server of the trouble server is in the same site with the trouble server, but it isn't looking to it for sysvol queries.
Let’s say site 1is the main site and site two is the distant site
Server A is ‘the trouble server’. Server B is the DC listed by Server A is it’s logon server when I log in. Server A and B are in site 1. Server C is the DC in site 2. Server B is looking to server C for sysvol queries. Very odd. The subnets folder in AD S&S is populated with my subnets and they are assigned to sites. Sites list their correct DCs.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER