SBS 2003 Premium, Multi-Homed, Problem with OMA

Here is my setup, I have a T1 connected to a firewall router, the only
LAN port in use on that router is the SBS 2003 Premium box. Standard
SBS ports are open, 21, 25, 80, 443, 444, 4125 and a few others for a
remote backup service I provide. I installed a 2nd NIC in the SBS box
that connects to a wireless firewall router attached to a Cable Modem,
this router has my workstations attached to it. This was done so that
my LAN traffic would not use any bandwidth on the T1. The SBS box is
setup to host my domain and Exchange. All workstations are joined to
the domain which is why I would like to maintain the multi-home setup
so they can use DNS for authentication to each other for drive and
printer shares. The workstations have static IP's and list the SBS 2nd
NIC as primary DNS with the wireless router as secondary DNS. This is
the address that connects the SBS box to the wireless router they are
connected to.

SBS box Internal NIC is 192.168.0.2 and gateway of 192.168.0.1 for T1
router. Secondary NIC is 192.168.1.2 with no gateway. Both addresses
are outside the DHCP scope on each router. Local traffic on
192.168.1.* can hit Exchange with Outlook just fine and AD services, I
see the activity on 2nd NIC when LAN traffic is retrieving mail for
example.

Treo 700w, running WM5 (Verizon) device can hit
mailserver.domain.com/exchange web address and log in to OWA just
fine.

Laptop using a Verizon data card can connect with Outlook 2003 via RPC
over HTTP with both Basic and NTLM authentication (laptops NTLM level
was raised to 3) just fine.

I have run CEICW on the SBS box and designated the internal NIC as
the ISP and 2nd NIC as the LAN. DNS settings in the CEICW are the two
provided by T1 provider and gateway is the T1 routers address. When I
view the two NIC's after CEICW has run, they are both setup to use
192.168.1.2 for DNS which is the secondary NIC's address. Phone still
will not synchronize. I even changed both DNS settings to use
127.0.0.1 and 192.168.0.2 which is the address of the NIC attached to
the T1 where all inbound mail traffic is coming.

If I disable the 2nd NIC the phone will start to synchronize, as soon
as the LAN NIC is re-enabled the phone fails again with the status
code 0x85010014.

If I re-run CEICW and check off that I use a single NIC for ISP and
LAN traffic and designate it to be the T1's NIC, the phone will synch
again. Side note- every time CEICW is run I am allowing all services
and keeping the SBS firewall disabled. ISA 2004 was not installed.

Now, when CEICW has configured the box to use only the T1 NIC for ISP
and LAN traffic, the phone will synch but I get Userenv 1030 and 1058
errors in the Event Viewer/Application logs every 5 minutes and errors
in System logs for Netlogon event ID 5774, and in the DNS Server for
DNS event ID 6702. Same errors occur if I run CEICW and configure the
machine to use both NIC's and manually disable the LAN NIC.

I have tried removing the field for forms authentication in System
Manager Servers/Server/Protocols/HTTP/Exchange Virtual Server.

I have tried adding and also not using any headers for the Default Web
Site in IIS (restarting IIS after changes each time).

I have tried specifying the ISP NIC for the Default Web Site to listen
on.

I know my certificate is fine because when I am only using the ISP NIC
on the SBS box the phone synchronizes fine.

I have also manually configured the ISP NIC as interface metric 1
instead of Automatic metric. I also added the LAN router GW address
and set it to a metric of 2 after the ISP router GW address (metric
1). Same gateway configuration was done for the LAN NIC except it's
Interface metric was set as 2.

Thank you in advance for any suggestions you may have.

Craig
.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... Les Connor [SBS Community Member - SBS MVP] ... No DNS Name Resolution If DHCP Client Service Is Not Running ... You have a full-time broadband connection. ... Next I Select a local router device with an ip address. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Go back to pointing the external NIC DNS Servers to the SBS server IP ... make sure the DHCP Client Service is running on the server. ... Next I Select a local router device with an ip address. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... In the TCP/IP properties for the external NIC, you need to specify an external DNS server for DNS, instead of the server's own IP address. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Merv Porter [SBS MVP] ... dish that I have currently plugged into the router. ... IP it means that your problem is now DNS. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: CEICW Network Error
    ... both NICs on SBS should get DNS from the 'internal' SBS NIC. ... The SBS DNS Server service can then be told to use the router or your ISP's DNS Servers as forwarderby submitting such during the CEICW or manual adjustment, OR you can leave the DNS setting blank during CEICW and SBS DNS will resolve using 'root hints'. ...
    (microsoft.public.windows.server.sbs)