Re: SBS 2003 + TS. HELP needed URGENTLY please!

Is the ISA client installed on the TS? If so, no matter (maybe little matter) about the routing table the ISA client will be intercepting calls.

However, even without the ISA client on the TS (and depending on use it may be unneccessary) operation isn't going to be optimal.

Another consideration is that you are effectively providing a path into your network which bypasses ISA.

Really, the corrrect way to do this is to use a dual WAN capable router in front of ISA. In normal operation (both DSL services working) the router does what it does best (route), ISA does it's bit (firewall), and the protected system don't need any special configuration. This has the added advantages that should one of the services be down the router may be able to redirect traffic through the other connection (failover). You may also be able to do some bandwidth sharing.

There are some very reasonable cost dual interface routers.

--
SBS remote support services. (Fees apply)
mickm at mickmalloy dot dyndns dot org

"David" <David@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:773B1479-537C-422D-8F12-98B334F2708C@xxxxxxxxxxxxxxxx
I ha
ve removed the DG on the ADSL nic, added the persistent route, rebooted the TS
and now we have the same condition ,no access using remote desktop on the
ext TS nic. Now
I am more confused. Any ideas Merv

Stuart
"Merv Porter [SBS-MVP]" wrote:

I believe you can only have one default gateway per computer. I would try
removing the DG on the TS external NIC and adding a persistent static route
to the TS:

route p add 192.168.168.0 255.255.255.0 192.168.168.168

--
Merv Porter [SBS-MVP]
============================


"David" <David@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CEC9A7C5-6A0D-48A8-A3F3-0447F4F9A87C@xxxxxxxxxxxxxxxx
> Hi All,
>
> I have posted here as we have an SBS network in which we want to > install
> a
> terminal server and I need help with what I think is an IP/routing > issue,
> but
> I don't have enough experience to figure it out.
>
> We have a Dell 2900 terminal server in our SBS 2003 Premium (with ISA
> 2004)
> domain.
> The SBS server has 2 nics configured with ISA and a public IP I shall > call
> extIP1. The internal SBS nic is configured with 192.168.16.2/24.
> The external nic is configured with 192.168.0.1/24.
>
> The TS also has 2 nics, nic1 is configured with the same IP range as > the
> internal SBS nic, 192.168.16.26/24 and the second nic is connected
> to a second ADSL line with a public IP IP2, the nic having address
> 192.168.168.65/24, via a sonicwall at 192.168.168.168.
>
> So we have
>
> Internet
> ADSL2---IP2<---Sonicwall<------------------------>TS----------------->SBS
> int
> LAN------------------------------->SBS ext------>IP1---->Internet ADSL1
> 81.xxx.xxx.xxx 192.168.168.168 192.168.168.65 192.168.16.26
> 192.168.16.2 192.168.0.2
>
> We have set up the TS in this configuration to make use of the second > ADSL
> line as the SBS ADSL1 line is currently used by 47 users on the SBS > LAN.
> Our problem is loss of remote desktop connection from IP2 on ADSL2, and > I
> would be very grateful for advice from people with with more knowledge > of
> routing than
> I have. When the connection from IP2 is lost, if we disable the lan > side
> nic on the TS (192.168.16.26) we can connect and get a login screen to
> logon
> locally
> to the TS but as soon as the nic is enabled there is no connection at > all
> from IP2.
>
> I have looked at the routing tables for both TS and SBS boxes and it > seems
> to me that the routing table and ipconfig details for the TS are not > setup
> correctly, but
> I am not sure where.
> We have made no changes to this table, it is in the state that was > created
> after first booting the TS and I include both tables and the ipconfig
> listings
> for both TS and SBS boxes below.
> We have had numerous connection failures to the TS via IP2 on ADSL2. We
> thought we had the problem solved when we disabled the Broadcom nics on
> the TS
> in the BIOS and uninstalled the Broadcom management software having > seen
> the many networking issues that these nics can introduce, indeed we
> rebuilt
> the TS
> from scratch with 2 Intel pro gigabit adapters. At first boot > everything
> went well until I added the Microsoft security updates, rebooted and no
> connection
> was possible from IP2 on ADSL2. That was when I decided to look at the > ip
> and routimg table configs.
>
>
>
>
> TS ROUTING TABLE
>
> IPv4 Route Table
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 15 17 a6 cb bc ...... Intel(R) PRO/1000 PT Server Adapter
> #2
> 0x10004 ...00 15 17 a9 a6 da ...... Intel(R) PRO/1000 PT Server Adapter
> ===========================================================================
> ===========================================================================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 192.168.16.2 192.168.16.26 > 10
> 0.0.0.0 0.0.0.0 192.168.168.168 192.168.168.65 > 10
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 > 1
> 192.168.16.0 255.255.255.0 192.168.16.26 192.168.16.26 > 10
> 192.168.16.26 255.255.255.255 127.0.0.1 127.0.0.1 > 10
> 192.168.16.255 255.255.255.255 192.168.16.26 192.168.16.26 > 10
> 192.168.168.0 255.255.255.0 192.168.168.65 192.168.168.65 > 10
> 192.168.168.65 255.255.255.255 127.0.0.1 127.0.0.1 > 10
> 192.168.168.255 255.255.255.255 192.168.168.65 192.168.168.65 > 10
> 224.0.0.0 240.0.0.0 192.168.16.26 192.168.16.26 > 10
> 224.0.0.0 240.0.0.0 192.168.168.65 192.168.168.65 > 10
> 255.255.255.255 255.255.255.255 192.168.16.26 192.168.16.26 > 1
> 255.255.255.255 255.255.255.255 192.168.168.65 192.168.168.65 > 1
> Default Gateway: 192.168.168.168
> ===========================================================================
> Persistent Routes:
> None
>
> TS IPCONFIG/ALL
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : xxxxxxxxxxxx
>
> Primary Dns Suffix . . . . . . . : xxxxx.local
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
> DNS Suffix Search List. . . . . . : xxxxxx.local
>
>
>
> Ethernet adapter ADSL:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Server > Adapter
> #2
>
> Physical Address. . . . . . . . . : 00-15-17-A6-CB-BC
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 192.168.168.65
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 192.168.168.168
>
> DNS Servers . . . . . . . . . . . : 192.168.168.168
>
>
>
> Ethernet adapter LAN:
>
>
>
> Connection-specific DNS Suffix . : xxxxxxxxxx.local
>
> Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Server > Adapter
>
> Physical Address. . . . . . . . . : 00-15-17-A9-A6-DA
>
> DHCP Enabled. . . . . . . . . . . : Yes
>
> Autoconfiguration Enabled . . . . : Yes
>
> IP Address. . . . . . . . . . . . : 192.168.16.26
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 192.168.16.2
>
> DHCP Server . . . . . . . . . . . : 192.168.16.2
>
> DNS Servers . . . . . . . . . . . : 192.168.16.2
>
> Primary WINS Server . . . . . . . : 192.168.16.2
>
> Lease Obtained. . . . . . . . . . : 06 March 2009 11:02:06
>
> Lease Expires . . . . . . . . . . : 14 March 2009 11:02:06
>
> SBS ROUTING TABLE
> IPv4 Route Table
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 18 8b 3f df b0 ...... Intel(R) PRO/1000 PT Server Adapter
> #2
> 0x10004 ...00 15 17 a9 a6 da ...... Intel(R) PRO/1000 PT Server Adapter
> ===========================================================================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 > 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 > 1
> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 > 20
> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 > 20
> 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 > 20
> 192.168.16.0 255.255.255.0 192.168.16.2 192.168.16.2 > 10
> 192.168.16.2 255.255.255.255 127.0.0.1 127.0.0.1 > 10
> 192.168.16.255 255.255.255.255 192.168.16.2 192.168.16.2 > 10
> 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 > 20
> 224.0.0.0 240.0.0.0 192.168.16.2 192.168.16.2 > 10
> 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 > 1
> 255.255.255.255 255.255.255.255 192.168.16.2 192.168.16.2 > 1
> Default Gateway: 192.168.0.1
> ===========================================================================
> Persistent Routes:
> None
>
> SBS IPCONFIG /ALL
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : xxxxxx
>
> Primary Dns Suffix . . . . . . . : xxxxxx.local
>
> Node Type . . . . . . . . . . . . : Unknown
>
> IP Routing Enabled. . . . . . . . : Yes
>
> WINS Proxy Enabled. . . . . . . . : Yes
>
> DNS Suffix Search List. . . . . . : xxxxxxx.local
>
>
>
> Ethernet adapter Server Local Area Connection:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Server > Adapter
>
> Physical Address. . . . . . . . . : 00-18-8B-3F-DF-B0
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 192.168.16.2
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . :
>
> DNS Servers . . . . . . . . . . . : 192.168.16.2
>
> Primary WINS Server . . . . . . . : 192.168.16.2
>
>
>
> Ethernet adapter Broadband:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Server > Adapter
> #2
>
> Physical Address. . . . . . . . . : 00-10-18-26-31-02
>
> DHCP Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 192.168.0.2
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>
> Default Gateway . . . . . . . . . : 192.168.0.1
>
> DNS Servers . . . . . . . . . . . : 192.168.16.2
>
> Primary WINS Server . . . . . . . : 192.168.16.2
>
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
>
>
> SBS Routing table
>
> IPv4 Route Table
> ===========================================================================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10003 ...00 18 8b 3f df b0 ...... Intel(R) PRO/1000 PT Server Adapter
> #2
> 0x10004 ...00 15 17 a9 a6 da ...... Intel(R) PRO/1000 PT Server Adapter
> ===========================================================================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 > 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 > 1
> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 > 20
> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 > 20

.

Relevant Pages

  • Re: 45 days STUCK LIKE CHUCK. DNS / Mx record cant recieve emails
    ... Is this SBS Premium, and if so, in ISA, is the "SBS SMTP Server Access Rule" ... like Exchange not listening on the Internet NIC. ... Nics Cards internal / externally.. ... You can test the connection from within the LAN, ...
    (microsoft.public.windows.server.sbs)
  • Re: Funky mouse behavior on a TS session
    ... The issue surfaced a little more than a year ago, first with Broadcom NICs, as they were the first to come out with task offloading and recieve side scaling and in the very popular 2900 series servers. ... The error conditions weren't widely seen with WS SP1, as an update needed to be applied in order to enable the features in the OS. ... The issues are far wider than with SBS, they were first discovered on non-SBS systems. ... the resolution set at the connecting PC will be used by 'full screen' RDP sessions but during the remote connection procedure you can set the resolution to be used. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 + TS. HELP needed URGENTLY please!
    ... matter) about the routing table the ISA client will be intercepting calls. ... even without the ISA client on the TS (and depending on use it may ... SBS remote support services. ... The SBS server has 2 nics configured with ISA and a public IP I shall ...
    (microsoft.public.windows.server.sbs)
  • RE: Server with 3 NICs
    ... 3 NICs on SBS 2k3 system scenario is not a recommended configuration. ... the 3 NICs with 2 network segments on your SBS server will cause lots of side issues. ... Server Local Area Connection is ...
    (microsoft.public.backoffice.smallbiz)
  • Re: External Firewall with SBS 2003
    ... The pfSense device is running version 1.2 and it has 5 NICs. ... We'll certainly terminate the VPN connections at the pfSense and not SBS as it is now. ... 2004 and twin NICs for my setup. ... the Firewall do the PPTP connection. ...
    (microsoft.public.windows.server.sbs)
Loading