Unable to connect to Domain Controller

[jlpk007]

I am unable to connect to my Domain Controller(win2k3)

Domain controller(DC) is behind wingate and the machine(A) connecting to it is outside of wingate.

Rough sketch
DC<--------------->WINGATE<------------->Machine A
machine A and wingate is connected via same switch.I am able to ping DC from Machine and vice versa.

Port Open:
135/TCP
53/TCP
88/TCP
389/TCP
445/TCP

Thank You

[adrien]

Hi

You need to add

53/UDP (for DNS to domain controller)

137/UDP (for netBios name resolution)
138/UDP (for SMB)
139/TCP (for SMB)

Also this traffic needs to be routed, without translating addresses (i.e. NAT won't work).

Adrien

[jlpk007]

Hi

You need to add

53/UDP (for DNS to domain controller)

137/UDP (for netBios name resolution)
138/UDP (for SMB)
139/TCP (for SMB)

Also this traffic needs to be routed, without translating addresses (i.e. NAT won't work).

Adrien

Hi Adrien,

Just to check,do i just open the above port u stated or is it additional port i had to open on top of mine?
traffic need to routed mean i need to redirect packet to my domain controller right.?Thanks.

Thank You
jeffrey

[jlpk007]

does wingate supports a machine to connect to a domain controller behind it.like my first post,

thx..

[jlpk007]

I have tried to open the following port but it doesnt work...any additional port or is ad using random port to connect ?

53/UDP (for DNS to domain controller)
137/UDP (for netBios name resolution)
138/UDP (for SMB)
139/TCP (for SMB)
135/TCP
53/TCP
88/TCP
389/TCP
445/TCP

Thank You.

[jamesc]

*Just want to add some minor comments.

1. For Machine A to know where to log into the domain, it needs to have the AD DNS Server setup for its DNS.

2. If you are not sure what ports to open, then check the firewall tab in WinGate after Machine A tries to login.
GateKeeper --> View menu --> Firewall.