Solved

Private links routing in SBS2003

Posted on 2004-10-13
9
316 Views
Last Modified: 2013-11-21
Two servers, Two ADSL connections

Have two servers (SBS2003 with ISA and 2003 Terminal Server) One ADSL for internet connection and the other ADSL is a private link to remote offices.

This is how I have it setup:

Remote workstations 192.168.1.101 (gateway 192.168.1.1)
       |
Private links remote ADSL 192.168.1.1
       |
      ISP
       |
Private links head office ADSL 192.168.16.1 (no gateway)
       |
   Switch
     /   \
    /     \___ Terminal Server 192.168.16.3 (gateway 192.168.16.2)
   /
1st NIC in SBS2003 192.168.16.2 (no gateway)
   ISA
2nd NIC in SBS2003 192.168.0.3 (gateway 192.168.0.1)
   |
Internet ADSL 192.168.0.1
   |

Now for the problem.

If I remove the SBS2003 box everything works as it should. Remote workstations can terminal server in to head office and I can remote administer the workstations.

Add the SBS2003 back in, it all falls over.

If I do a tracert from 192.168.16.3 (TS) to 192.168.1.101 it goes straight to 192.168.16.2 (SBS) first hop and that’s it.

As I see it, I need to add some routing to the SBS2003 box to send any packets destined for 192.168.1.101 back to 192.168.16.1 but have no idea how to do this.
Maybe it's an ISA issue, just don't know.

Regards
Bazoz
0
Comment
Question by:bazoz
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
9 Comments
 
LVL 4

Expert Comment

by:sriwi
ID: 12296955
type "print route" in command prompt and post your result here, i think your computer doesn't the ip route

Cheers
0
 
LVL 1

Author Comment

by:bazoz
ID: 12297181
Hi sriwi

From TERMINAL SERVER

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 e0 81 2a cc 8a ...... Broadcom NetXtreme Gigabit Ethernet
===========================================================================
===========================================================================
Active Routes:
Network Destination           Netmask            Gateway             Interface    Metric
                0.0.0.0                0.0.0.0     192.168.16.2       192.168.16.3       1
             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.3       192.168.16.3     20
       192.168.16.3   255.255.255.255          127.0.0.1            127.0.0.1     20
   192.168.16.255   255.255.255.255     192.168.16.3       192.168.16.3     20
             224.0.0.0            240.0.0.0     192.168.16.3       192.168.16.3     20
  255.255.255.255  255.255.255.255     192.168.16.3       192.168.16.3       1
Default Gateway:      192.168.16.2
===========================================================================
Persistent Routes:
  None
 
From SBS 2003 (I did have another NIC in the Terminal Server 192.168.0.3 but have since disabled it - it still shows below)
 
IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 e0 81 2b 06 15 ...... Intel(R) PRO/100 S Server Adapter - Packet Scheduler Miniport
0x10004 ...00 e0 81 2b 06 5a ...... Broadcom NetXtreme Gigabit Ethernet - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination           Netmask           Gateway           Interface   Metric
                0.0.0.0                0.0.0.0      192.168.0.1       192.168.0.3     20
             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.3       192.168.0.3      20
         192.168.0.3  255.255.255.255          127.0.0.1           127.0.0.1     20
     192.168.0.255   255.255.255.255      192.168.0.3       192.168.0.3     20
       192.168.16.0      255.255.255.0     192.168.16.2     192.168.16.2     20
       192.168.16.2   255.255.255.255          127.0.0.1          127.0.0.1     20
   192.168.16.255   255.255.255.255     192.168.16.2     192.168.16.2     20
            224.0.0.0             240.0.0.0       192.168.0.3      192.168.0.3      20
            224.0.0.0             240.0.0.0     192.168.16.2     192.168.16.2     20
  255.255.255.255  255.255.255.255       192.168.0.3      192.168.0.3       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
0
 
LVL 1

Author Comment

by:bazoz
ID: 12297390
Oops, Sorry the other NIC was 192.168.0.4 in the Terminal Server - Since been disabled
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 4

Accepted Solution

by:
sriwi earned 250 total points
ID: 12298587
On your sbs you need to add a route that is going from 192.168.16.x to 192.168.1.x through 192.168.16.1

otherwise the packets just get to the internet and never comes back.

on command prompt:

route -p add 192.168.1.0 255.255.255.0 192.168.16.1 20 IF 1

for example:
http://www.computerhope.com/routehlp.htm
0
 
LVL 1

Author Comment

by:bazoz
ID: 12307041
Hi sriwi

I couldn't get you route to work, but I could get this onto the Terminal Server box.

route -p add 192.168.1.0 mask 255.255.255.0 192.168.16.1

and now it nearly all works except I had to disable the ISA client on the TS box.

What do I need to add to ISA on the SBS2003 box so I can enable the ISA client. Because now the TS box cannot reach the internet.
0
 
LVL 4

Expert Comment

by:sriwi
ID: 12309287
you need to put the proxy on your internet explorer, after it should work, remember to put your isa ip address on the proxy address
0
 
LVL 1

Author Comment

by:bazoz
ID: 12312837
When you run \\SBS2003computername\connectcomputer from clients, ISA client and proxy settings get added by default.

But the only way I could get the clients to remote desktop into the TS box was to disable ISA client on the TS
0

Featured Post

Use Case: Protecting a Hybrid Cloud Infrastructure

Microsoft Azure is rapidly becoming the norm in dynamic IT environments. This document describes the challenges that organizations face when protecting data in a hybrid cloud IT environment and presents a use case to demonstrate how Acronis Backup protects all data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Internet Business Fax to Email Made Easy - With  eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, f…

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question