AD domain visible to NT 4 domain

[covski]

Hi,

I have 2 domains on seperate subnets connected via a router. Both can ping each other happily yet I can't get them to see each others domain via network neighborhood/places. One is a 2000 server with AD, the other is an NT4 server in its own domain. On both I've amended the lmhosts to contain each other as below.

194.129.nnn.nnn optadm02 #PRE #DOM:GXxxxx on the 2000 server
where optadm02 is the PDC in the other domain

192.168.nnn.nnn ukcexc01 #PRE #DOM:UKxxxx on the NT4 PDC to one of the 2 2000 server in the AD.

Any pointers as to what else I need to do to make them visible to one another.

Cheers.

 

[allenEd]

Hi,

Is this a new problem, or are you setting this up from new? Have you set up "trusts" between the domains?

 

[allenEd]

Also the 194.129.nnn.nnn address is public, so I would guess that some VPN solution may be requird. This is done through RRAS on the W2000 PDC. (better to run off a member server, rather than exposing a PDC).

Hope this helps, or am I barking up the wrong tree?

Allen

 

[covski]

Hi,

The 194.129 address is actually private (No idea why the previous admin set it up like this).

this is a new project connecting the 2 together.

I have now added a 1 way trust so that the NT 4 domain is trusted by the 2000/AD domain. However, I still can't see them.

Any further suggestions would be appreciated.

 

[allenEd]

I dont know what impact having the 194.129.nnn.nnn address will have, but assuming its ok, are any firwalls or packet filters in operation?

Can you supply me with a "route print" from PDC

Allen

 

[covski]

Allen no firewalls or packet filters. The router between simply provides NAT. Here is the route print fromthe PDC

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 194.129.255.222 194.129.255.72 1
10.14.0.0 255.255.255.0 194.129.255.222 194.129.255.72 1
10.15.0.0 255.255.255.0 194.129.255.201 194.129.255.72 1
10.100.100.0 255.255.255.0 194.129.255.106 194.129.255.72 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
158.43.192.1 255.255.255.255 194.129.255.248 194.129.255.72 1
172.30.20.0 255.255.255.0 194.129.255.250 194.129.255.72 1
192.168.73.0 255.255.255.0 194.129.255.222 194.129.255.72 1
192.168.100.0 255.255.255.0 194.129.255.228 194.129.255.72 1
194.129.248.0 255.255.255.0 194.129.255.249 194.129.255.72 1
194.129.255.0 255.255.255.0 194.129.255.72 194.129.255.72 1
194.129.255.72 255.255.255.255 127.0.0.1 127.0.0.1 1
194.129.255.255 255.255.255.255 194.129.255.72 194.129.255.72 1
205.227.137.57 255.255.255.255 194.129.255.248 194.129.255.72 1
224.0.0.0 224.0.0.0 194.129.255.72 194.129.255.72 1
255.255.255.255 255.255.255.255 194.129.255.72 194.129.255.72 1
===========================================================================

C:\WINNT\system32\drivers\etc>tracert 192.168.73.141

Tracing route to UKCEXC01 [192.168.73.141]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 194.129.255.222
2 <10 ms <10 ms <10 ms UKCEXC01 [192.168.73.141]

Trace complete.

Cheers

 

[yanks2112]

Try accessing either server by ip i.e start|run \\149.129.x.x\ and see if you can get there. Also make sure that NetBios over TCP/IP is enabled on the NICs. It should be but I found this to be the case when I had this issue
Hope this helps.

 

[covski]

Net Bios over TCP/IP is enabled. If I enter the \\192.nnn.nnn.nnn into either server (Start-Run) I get prompted for a username and password. If I enter a valid one I can see the available shares.

Could it be that I have to tell the cisco router inbetween to allow netbios over tcp/ip?

Thanks

 

[covski]

The cisco router has

permit ip any any

on the access list thats used. Any other ideas?