XPe logon on domain through NAT

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi.
I have a LAN with this config
Server1 1.2 ---- 1.201 Server2 100.1 ----- 100.2 Server3
| |
| |
| |
192.168.1.7 DHCP Client
Server4 Windows Embedded Client

Server1: NT4 Domain: ESA
Server2: 2k3 Ent. R2 NAT/DHCP Server. Domain: SCHOOL
Server3: 2k3 Ent. R2
Server4 2k3 Domain: MYSCHOOL

1.2 refers to 192.168.1.2 and so on


Server2 has two NICs with the IPs above.

Server2 is a 2k3 Ent. R2 NAT Server.
I can see all networks and shares from all networks (ping is OK).
Now,
In Server2 i can do RDP to Server4
In Server2 i can logon in domain ESA and MYSCHOOL as Administrator of
that domains.
In Server3 i can logon to MYSCHOOL domain.
But in Server3 i can't logon to NT4 Domain ESA ("(...) domain not
available"). I think it's something with NAT and NETBIOS. How can I
solve it? With a VPN???
I can't also to a RDP from Windows Embedded Client to ESA or MYSCHOOL
domains althought i can logon to a domain on network 192.168.100.x: it
says that i should be in the Remote Desktop Users Group or Allow
Access to Terminal Services Policy but it's the administrator and he's
already in that group naturally and that don't show up in MYSCHOOL
domain because i haven't installed Terminal Services in that Domain
Controller. From Windows Embedded Client i can choose all domains
(ESA, MYSCHOOL, etc.) because i've established all trusts correctly
and they are working.

What i want is:
To be able to logon to ESA or MYSCHOOL domain from my Windows Embedded
Client.
Sugestions?

Thanks :)), regards
António

.



Relevant Pages

  • Re: XPe logon on domain through NAT
    ... Server1: NT4 Domain: ESA ... Server4 2k3 Domain: MYSCHOOL ... Server2 has two NICs with the IPs above. ... In Server3 i can logon to MYSCHOOL domain. ...
    (microsoft.public.windowsxp.embedded)
  • XPe logon through NAT
    ... Server1: NT4 Domain: ESA ... Server4 2k3 Domain: MYSCHOOL ... Server2 has two NICs with the IPs above. ... In Server3 i can logon to MYSCHOOL domain. ...
    (microsoft.public.windows.server.general)
  • Re: missing netlogon & Sysvol Share
    ... There are currently no logon servers available to service the logon ... Something in between is not allowing replication (firewall, WAN link, ... problem is server2 is missing the Sysvol and Netlogon Shares. ... This event log message will appear once per connection, ...
    (microsoft.public.windows.server.active_directory)