08-17-2009 05:16 AM - edited 03-06-2019 07:16 AM
Hi All Pros,
I am just wondering if anyone faced this issue before where a host in another VLAN is unable to join Ms Windows domain which is in another VLAN? It does not have any access list because both are connected to the same switch (C3560). InterVLAN routing already enable. We have tested telnet to most of the ports involved in Active Directory from one host VLAN to Server VLAN. Server team checked that the Domain Controller and DNS is running FINE. Now we are stucked in between, not knowing what is the problem.
Host in VLAN 211 just unable to join domain to Server in VLAN 214. But host is able to join when in same VLAN 214.
Your help is very much appreciated.
08-17-2009 07:35 AM
Hello Chow,
try the following
int vlan 214
ip helper-address AD-server-ip-address
the difference when in the same ip subnet is that server can be discovered with a broadcast
Hope to help
Giuseppe
08-17-2009 06:10 PM
Hi Giuseppe,
The DHCP server is actually not in the Domain Controller. There is one WLC in the network working as DHCP for the entire network.
We have tried setting all IP in VLAN 214 or 211 manually to host but still not able to join domain.
08-17-2009 11:19 PM
Are the hosts in Vlan 211 are WLAN clients or connected on switches..??
08-18-2009 12:46 AM
All connected through LAN... There isn't any client in VLAN 214 ...We only did it for testing purpose..
08-18-2009 05:23 AM
can any hosts on vlan 211 ping the servers in vlan 214??
08-18-2009 08:17 AM
yes, PING and TELNET is working from VLAN 211 to VLAN 214..
08-18-2009 08:46 AM
Hi,
If hosts on vlan 211 able to ping hosts on vlan 214, then this is probably LDAP Protocol issue.
Could you confirm that port 389 TCP is not blocked any where?
HTH
Mohamed
08-18-2009 07:36 PM
Hi,
There isn't any access-list that block inter Vlan communication. However, I will try to do a telnet from VLAN 211 to DC through TCP 389 ... but i think if the DC is listening to this port, it shouldn't be any problem.
08-18-2009 10:41 PM
ok, i've tested and we are able to telnet from 211 to DC through TCP 389 ...
09-03-2009 06:40 AM
I have finally solved this issue. It is not due to any routing or configuration problem. The problem is from the Domain Controller's end.. It is due to "Single Label Domain" issue when they created the Domain Controller.
Below links as references;
http://support.microsoft.com/kb/300684
http://www.chicagotech.net/server/singlelabledns1.htm
How do we close or end this topic?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide