Re: Cross Forest Trust

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

So if I do an nsloookup from my domain trying to resolve for the domain I'm
trying to create the trust with should it resolve to thier DC's as well?

Would I need to do a zone transfer in DNS from thier windows DNS to our UNIX
dns?


--
Thanks!

Crisoft



"Paul Bergson [MVP-DS]" wrote:

Pinging the domain name is going to resolve to a dc, this is expected. Do
an nslookup on your domain name and it should return all the dc's within
your domain.

If I recall correctly I don't believe 137 and 138 are needed, I believe 445
is what is used.

Are high ports available both ways?

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Crisoft" <ccisat1crc@xxxxxxxxxxx> wrote in message
news:09B9EF85-8B99-485C-A6E3-70EBD46A4FDA@xxxxxxxxxxxxxxxx
I've used portquery to test connectivity to ports and everything looks
good.
Are you supposed to be able to telnet into netbios ports 137,138? These
won't even answer on the localhost.

I noticed that when I ping the domain name that I'm trying to establish
the
trust with it replies with the IP of the PDC which is the DC that I've
opened
up the connection to use for creating the trust. Would that cause a
problem?

Here's my port query.

=============================================

Starting portqry.exe -n ckent -e 135 -p TCP ...


Querying target system called:

ckent

Attempting to resolve name to IP address...

Name resolved to 192.168.5.18

querying...

TCP port 135 (epmap service): LISTENING

Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:

UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076
ncacn_ip_tcp:192.168.5.18[1152]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncacn_np:\\\\CKENT[\\PIPE\\lsass]

UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
ncalrpc:[LRPC00000124.00000001]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncacn_np:\\\\CKENT[\\PIPE\\lsass]

UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
ncalrpc:[LRPC00000124.00000001]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\CKENT[\\PIPE\\lsass]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[LRPC00000124.00000001]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_np:\\\\CKENT[\\pipe\\WMIEP_124]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:192.168.4.108[1026]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_ip_tcp:192.168.5.18[1026]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncalrpc:[NTDS_LPC]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncadg_ip_udp:192.168.4.108[1028]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncadg_ip_udp:192.168.5.18[1028]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:192.168.4.108[1029]

UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
ncacn_http:192.168.5.18[1029]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncacn_np:\\\\CKENT[\\PIPE\\lsass]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncalrpc:[LRPC00000124.00000001]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncacn_np:\\\\CKENT[\\pipe\\WMIEP_124]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncacn_ip_tcp:192.168.4.108[1026]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncacn_ip_tcp:192.168.5.18[1026]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncalrpc:[NTDS_LPC]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncadg_ip_udp:192.168.4.108[1028]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncadg_ip_udp:192.168.5.18[1028]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncacn_http:192.168.4.108[1029]

UUID: f5cc5a7c-4264-101a-8c59-08002b2f8426 MS NT Directory XDS Interface
ncacn_http:192.168.5.18[1029]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\CKENT[\\PIPE\\lsass]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[LRPC00000124.00000001]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_np:\\\\CKENT[\\pipe\\WMIEP_124]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_ip_tcp:192.168.4.108[1026]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_ip_tcp:192.168.5.18[1026]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncalrpc:[NTDS_LPC]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncadg_ip_udp:192.168.4.108[1028]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncadg_ip_udp:192.168.5.18[1028]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_http:192.168.4.108[1029]

UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface
ncacn_http:192.168.5.18[1029]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\CKENT[\\PIPE\\lsass]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[LRPC00000124.00000001]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_np:\\\\CKENT[\\pipe\\WMIEP_124]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:192.168.4.108[1026]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_ip_tcp:192.168.5.18[1026]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncalrpc:[NTDS_LPC]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncadg_ip_udp:192.168.4.108[1028]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncadg_ip_udp:192.168.5.18[1028]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:192.168.4.108[1029]

UUID: 12345678-1234-abcd-ef00-01234567cffb
ncacn_http:192.168.5.18[1029]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncalrpc:[LRPC000004ec.00000001]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_ip_tcp:192.168.4.108[1079]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_ip_tcp:192.168.5.18[1079]

UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:\\\\CKENT[\\PIPE\\atsvc]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncalrpc:[LRPC000004ec.00000001]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_ip_tcp:192.168.4.108[1079]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_ip_tcp:192.168.5.18[1079]

UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:\\\\CKENT[\\PIPE\\atsvc]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:192.168.4.108[1082]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncacn_ip_tcp:192.168.5.18[1082]

UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
ncalrpc:[LRPC000004a0.00000001]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:192.168.4.108[1082]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncacn_ip_tcp:192.168.5.18[1082]

UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
ncalrpc:[LRPC000004a0.00000001]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:192.168.4.108[1082]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncacn_ip_tcp:192.168.5.18[1082]

UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
ncalrpc:[LRPC000004a0.00000001]

UUID: 4da1c422-943d-11d1-acae-00c04fc2aa3f
ncacn_ip_tcp:192.168.4.108[1092]

UUID: 4da1c422-943d-11d1-acae-00c04fc2aa3f
ncacn_ip_tcp:192.168.5.18[1092]

UUID: 130ceefb-e466-11d1-b78b-00c04fa32883 NTDS ISM IP Transport
ncacn_ip_tcp:192.168.4.108[1117]

UUID: 130ceefb-e466-11d1-b78b-00c04fa32883 NTDS ISM IP Transport
ncacn_ip_tcp:192.168.5.18[1117]

UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_ip_tcp:192.168.4.108[1127]

UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_ip_tcp:192.168.5.18[1127]

UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncalrpc:[LRPC0000063c.00000001]

UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe
ncacn_np:\\\\CKENT[\\pipe\\WinsPipe]

UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_ip_tcp:192.168.4.108[1127]

UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_ip_tcp:192.168.5.18[1127]

UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncalrpc:[LRPC0000063c.00000001]

UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45
ncacn_np:\\\\CKENT[\\pipe\\WinsPipe]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000006e4.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:192.168.4.108[1135]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:192.168.5.18[1135]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000006e4.00000001]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:192.168.4.108[1135]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:192.168.5.18[1135]

UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncalrpc:[LRPC000006e4.00000001]

.

Relevant Pages

  • Re: Cant join a domain
    ... Attempting to resolve name to IP address... ... TCP port 42: NOT LISTENING ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cant join a domain
    ... Attempting to resolve name to IP address... ... TCP port 42: NOT LISTENING ...
    (microsoft.public.windows.server.active_directory)
  • DCPromo and VPN fails
    ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 135: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add a new DC to a new branch
    ... A Cisco router serves as DHCP server ... Querying target system called: ... Attempting to resolve IP address to a name... ... TCP port 135: ...
    (microsoft.public.windows.server.active_directory)
  • RE: Trust relationship betwen Win2003 & WinNT 4.0 Server
    ... regarding the LSA RPC port and the NetLogon RPC port (and the other RPC ... The directions said that the registry settings were located in place X. ... "RPS.LOCAL" in the Trusting Domains section of the Trust Relationships ... from the Win2003 server I can ping qtech1 without issue. ...
    (microsoft.public.windows.server.dns)