Potential DNS issue or something else??
We have split our domain locations into different subnets after relocating our servers to a colocation site
Head office 192.168.53.n
COLOCATION 192.168.0.n
The colocation site has a domain controller with no DHCP IE:DC01
The london subnet has a domain controller DC with DHCP IE:DC02
Logging on in London is fine & picks up domain shares etc no problem, but when browsing the network it is only picking up the local subnet not the whole domain.
From London, we cannot browse by name only ip address
our SQL server apps which rely on domain authentication cannot find the SQL server, but if we amend the connection string to the IP address we get the error that the login is from an untrusted domain & cannotbe used with windows authentication.
Head office 192.168.53.n
COLOCATION 192.168.0.n
The colocation site has a domain controller with no DHCP IE:DC01
The london subnet has a domain controller DC with DHCP IE:DC02
Logging on in London is fine & picks up domain shares etc no problem, but when browsing the network it is only picking up the local subnet not the whole domain.
From London, we cannot browse by name only ip address
our SQL server apps which rely on domain authentication cannot find the SQL server, but if we amend the connection string to the IP address we get the error that the login is from an untrusted domain & cannotbe used with windows authentication.
Are you saying from London you cannot access other site resources by name?
OR what?
OR what?
ASKER
sits are connected via VPN
Cannot access resources by name
Both Dcs are on the Same AD domain
Cannot access resources by name
Both Dcs are on the Same AD domain
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
1) How are the London and colo sites connected? Site to site VPN?
2) Are both DCs on the same AD domain? Or two separate domains with the same name?
3) Is the SQL Server at the colo site?