AD Sites and Services - subnet not listed effects?
I had a server that was recently put into a subnet, and I think as a result, since it had some LDAP query jobs, it was bogging down a particular domain controller.
However the job was not configured to specifically connect to the bogged down Domain Controller, so I'm trying to figure out why it was bogging it down.
The DC is in another physical connection that I do not want it being connected to from the physical site that the job server is in.
What's the best way to prevent that?
I created a new subnet in AD sites and services that the job server is in, and associated it to the same physical site.
Would this be the fix?
Also do I need to create an Inter-Site Transport between the site A and site B?
Right now I only have one called "DEFAULTIPSITELINK" in Inter-Site Transports, and it contains every site.
Do I need to create a new site link between site A and site B with a higher cost?
However the job was not configured to specifically connect to the bogged down Domain Controller, so I'm trying to figure out why it was bogging it down.
The DC is in another physical connection that I do not want it being connected to from the physical site that the job server is in.
What's the best way to prevent that?
I created a new subnet in AD sites and services that the job server is in, and associated it to the same physical site.
Would this be the fix?
Also do I need to create an Inter-Site Transport between the site A and site B?
Right now I only have one called "DEFAULTIPSITELINK" in Inter-Site Transports, and it contains every site.
Do I need to create a new site link between site A and site B with a higher cost?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Also would moving a subnet to another site cause problems? It has probably 20 servers on it and I'm not sure if it would cause any problems.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
What it is, is that there are servers in 10.3.6.0/24 subnet, but they are associated with "Site A".
Thing is in terms of physical network, "Site B" is where that 10.3.6.0 network is actually at. So logically itd make sense to reassign the subnet from Site A to Site B. Just don't know if that would cause issue since I'm not changing the subnet or IP addresses of the servers.
Thing is in terms of physical network, "Site B" is where that 10.3.6.0 network is actually at. So logically itd make sense to reassign the subnet from Site A to Site B. Just don't know if that would cause issue since I'm not changing the subnet or IP addresses of the servers.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Does the site link only take care of replication costs or does it also influence where computers connect to by default when logging in, or connecting to domain.com to run queries, etc.?
My understanding is that member guests/servers will connect to a Domain Controller that's in the same site as itself, assuming the member and DC are both in subnets that are associated to the same Site?