HiddenAgenda
asked on
Terminal service client can't see the dc controler of a child domain.
Here is some more information about my environment.
Infrastructure:
I have a multiple domain in a single site.
DC controler 1: 192.168.3.10 - Domain: Photek.local (First installed server and converted to a DC controler)
Installed components: Primary DNS server service - photek.local on 192.168.3.10, DHCP server: Ip range 192.168.3.50 - 100., Terminal Server Service in Admin mode.
DC controler 2: 192.168.3.11 - Domain: Photek.local :backup DC controler.
Installed components: Terminal Server service in Admin mode
DC Conrtoler 3: 192.168.3.15 - Domain: Europe.photek.local
DNS: 192.168.3.10. Host added in de forward lookup zone on the primary DNS.
Installed Components: Terminal Server service in ADMIN mode.
Clients-
Windows XP Pro in Domain photek.local
Windows 2000 Pro client in Domain photek.local
Installed components on the clients:
Terminal Service client.
Problem:
When running teh Terminal Service client from both of the client computer in the photek.local domain, i can see only the DC and the backup DC. I'm unable to see the DC in de CHILD Domain europe.photek.local.
Using the FDQN in the Terminal Service Client works fine.
Question:
How can i view all the servers (on which Terminal server service is installed on) using the browse option in the Terminal service client ?
Infrastructure:
I have a multiple domain in a single site.
DC controler 1: 192.168.3.10 - Domain: Photek.local (First installed server and converted to a DC controler)
Installed components: Primary DNS server service - photek.local on 192.168.3.10, DHCP server: Ip range 192.168.3.50 - 100., Terminal Server Service in Admin mode.
DC controler 2: 192.168.3.11 - Domain: Photek.local :backup DC controler.
Installed components: Terminal Server service in Admin mode
DC Conrtoler 3: 192.168.3.15 - Domain: Europe.photek.local
DNS: 192.168.3.10. Host added in de forward lookup zone on the primary DNS.
Installed Components: Terminal Server service in ADMIN mode.
Clients-
Windows XP Pro in Domain photek.local
Windows 2000 Pro client in Domain photek.local
Installed components on the clients:
Terminal Service client.
Problem:
When running teh Terminal Service client from both of the client computer in the photek.local domain, i can see only the DC and the backup DC. I'm unable to see the DC in de CHILD Domain europe.photek.local.
Using the FDQN in the Terminal Service Client works fine.
Question:
How can i view all the servers (on which Terminal server service is installed on) using the browse option in the Terminal service client ?
ASKER
Hi PeteLong,
So does this means that i will not be able to see the CHILD DC server in my Terminal service client?
The answer give me an idea of the problem but how does this effect the browsing for Terminal servers?
Does browsing in the TS client use the DNS server to find the servers who have Terminal Server service installed on it?
Do i have to configure /add /remove or other action in the Inter-site-domain connections?
Thanks in advance.
HiddenAgenda
So does this means that i will not be able to see the CHILD DC server in my Terminal service client?
The answer give me an idea of the problem but how does this effect the browsing for Terminal servers?
Does browsing in the TS client use the DNS server to find the servers who have Terminal Server service installed on it?
Do i have to configure /add /remove or other action in the Inter-site-domain connections?
Thanks in advance.
HiddenAgenda
HiddenAgenda
hello again :0)
At this point i realise i only half read the question Doh!
>>CHILD DC server in my Terminal service client?
DO you mean the DC in a child domain, if you do then I would say not, for reasons that are obvious the TsInternetUser is a limited account. a VERY dangerous option would be to put the TsInternetUser\GCserver user in the domain admins group but this is a frightening can of worms to open :0)
if your terminaled (is that a word?) in what happens if you
start >run >cmd
\\ip-addressofchildServer\
just a thought :0)
Pete
hello again :0)
At this point i realise i only half read the question Doh!
>>CHILD DC server in my Terminal service client?
DO you mean the DC in a child domain, if you do then I would say not, for reasons that are obvious the TsInternetUser is a limited account. a VERY dangerous option would be to put the TsInternetUser\GCserver user in the domain admins group but this is a frightening can of worms to open :0)
if your terminaled (is that a word?) in what happens if you
start >run >cmd
\\ip-addressofchildServer\
just a thought :0)
Pete
ASKER
Hi Pete,
Thanks for the answer. I tried to find more information about the TsInternetUser on the internet. The first time you mentioned it, it was kind of a spooky thing.(I heard of it but never thought that it could be that dangerous)
I will continue to use the DNS name of the DC in de CHILD Domain.
I needed it to modify/test my GPO settings but I think i'm going to find an other way.
Tnx.
Cheers!
HiddenAgenda.
Thanks for the answer. I tried to find more information about the TsInternetUser on the internet. The first time you mentioned it, it was kind of a spooky thing.(I heard of it but never thought that it could be that dangerous)
I will continue to use the DNS name of the DC in de CHILD Domain.
I needed it to modify/test my GPO settings but I think i'm going to find an other way.
Tnx.
Cheers!
HiddenAgenda.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ThanQ
The TsInternetUser account is used by the Terminal Services Internet Connector License. When Internet Connector Licensing is enabled, a Windows 2000-based server accepts 200 anonymous-only connections. Terminal Services clients are not prompted with a logon dialog box; they are logged on automatically with the TsInternetUser account. =(
Cheers!