AD Connection to SBS 2003 W/SP2

DBrxb · 08-11-2008, 01:39 PM

Hi.

I am banging my head on this. I have setup many UT servers and all have attached to the AD seamlessly, however, I have one that just doesn't want to work for me.

I have a customer running Small Business Server 2003 Premium and has a dual NICs handling the traffic.

Internal - going to all workstations - 192.168.16.x
External - going to internal port on the UT Edgeguard - 192.168.2.xx

UT Edgeguard - Internal port 192.168.2.x
External - 64.x.x.x - having external IP address to the cloud.

When trying to connect to the AD on SBS 2003, no matter what I do, I cannot get it to connect.

Here is what I have tried and it should work:
AD Server IP - 192.168.2.xxx (I have also tried the internal: 192.168.16.x)
Port -389
Login - Administrator (also have a Admin account set up called 'ADAdmin' with no luck)
Password: xxxx
AD Domain: SxxxxxxxPxxxxxxxxx.local

I keep getting 'Connection Failed'. Has anyone had this problem?

Much Thanks
Don

SirBC · 08-11-2008, 03:22 PM

Before I went from 2 NIC's to 1 NIC on my SBS box I think I had to open port 389 in RRAS. Try forwarding the port and see if that works.

DBrxb · 08-12-2008, 12:04 PM

In scanning the forum, I didn't see this one...
http://forums.untangle.com/directory-connector/3499-issues-ad-2-nic-setup.html
Referencing 2 NICs

Perhaps this is the same issue. SBS2003 has a form of ISA Server running inside and is performing NAT. - Not a fan of ISA!

I will try a change in configuration since how the UT Edgeguard is the Perimeter F/W in this case. NAT should happen at the UT.

Any other information would be appreciated.

Thanks
Don

sky-knight · 08-12-2008, 12:12 PM

If you have RRAS running on the SBS box all you should have to do is configure DHCP to use the UT as the gateway and unplug the "wan" nic on the SBS server. It will still route... but your network will bypass it.

Anyway your in good company with me around. I hate small business server. It should be renamed to rape small business server... the money it saves on the license is far exceeded by the extra maintainance and piles of work required to migrate off it when the company gets bigger.

YeOldeStonecat · 08-13-2008, 01:23 PM

I'd make a decision..either use ISA, or use Untangle. ISA is just doing its job..that WAN NIC of the SBS box is locked down, as it should be with ISA running.

Uninstall ISA...disable 1 NIC...run the CEICW to reconfige SBS single homed..and use UT.

Personally I love SBS....have tons of clients on it. The one client that is getting close to outgrowing it..there's an easy "Transition Pack" to move seamlessly to the full Windows Server products.

08-11-2008, 01:39 PM	#1 (permalink)
DBrxb Newbie Join Date: Aug 2008 Posts: 2	AD Connection to SBS 2003 W/SP2 Hi. I am banging my head on this. I have setup many UT servers and all have attached to the AD seamlessly, however, I have one that just doesn't want to work for me. I have a customer running Small Business Server 2003 Premium and has a dual NICs handling the traffic. Internal - going to all workstations - 192.168.16.x External - going to internal port on the UT Edgeguard - 192.168.2.xx UT Edgeguard - Internal port 192.168.2.x External - 64.x.x.x - having external IP address to the cloud. When trying to connect to the AD on SBS 2003, no matter what I do, I cannot get it to connect. Here is what I have tried and it should work: AD Server IP - 192.168.2.xxx (I have also tried the internal: 192.168.16.x) Port -389 Login - Administrator (also have a Admin account set up called 'ADAdmin' with no luck) Password: xxxx AD Domain: SxxxxxxxPxxxxxxxxx.local I keep getting 'Connection Failed'. Has anyone had this problem? Much Thanks Don

08-12-2008, 12:04 PM	#3 (permalink)
DBrxb Newbie Join Date: Aug 2008 Posts: 2	Update In scanning the forum, I didn't see this one... http://forums.untangle.com/directory-connector/3499-issues-ad-2-nic-setup.html Referencing 2 NICs Perhaps this is the same issue. SBS2003 has a form of ISA Server running inside and is performing NAT. - Not a fan of ISA! I will try a change in configuration since how the UT Edgeguard is the Perimeter F/W in this case. NAT should happen at the UT. Any other information would be appreciated. Thanks Don

08-12-2008, 12:12 PM	#4 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 8 Posts: 15,454	If you have RRAS running on the SBS box all you should have to do is configure DHCP to use the UT as the gateway and unplug the "wan" nic on the SBS server. It will still route... but your network will bypass it. Anyway your in good company with me around. I *hate* small business server. It should be renamed to rape small business server... the money it saves on the license is far exceeded by the extra maintainance and piles of work required to migrate off it when the company gets bigger. __________________ Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879

Protect

Filter

Perform

Connect

Manage

Add-Ons

08-11-2008, 03:22 PM	#2 (permalink)
SirBC Master Untangler Join Date: May 2008 Location: San Carlos, CA URLs submitted: 3 Posts: 101	Before I went from 2 NIC's to 1 NIC on my SBS box I think I had to open port 389 in RRAS. Try forwarding the port and see if that works.

08-13-2008, 01:23 PM	#5 (permalink)
YeOldeStonecat Join Date: Aug 2007 Posts: 1,391	I'd make a decision..either use ISA, or use Untangle. ISA is just doing its job..that WAN NIC of the SBS box is locked down, as it should be with ISA running. Uninstall ISA...disable 1 NIC...run the CEICW to reconfige SBS single homed..and use UT. Personally I love SBS....have tons of clients on it. The one client that is getting close to outgrowing it..there's an easy "Transition Pack" to move seamlessly to the full Windows Server products.