Two subnets, two servers, one application to be shared on both

Discussion in 'Windows Networking' started by Joe, Oct 1, 2005.

  1. Joe

    Joe Guest

    I have a need to temporally tie two networks togeter to
    share one application.

    I have two networks behind one firewall. This firewall has one ethernet port
    and handles DNS and runs DHCP. The switches for these networks are split
    into 2 vlans. moving users between networks is just a matter of changing to
    another port.

    One network is a large peer-to-peer workgroup setup with 30 users on one
    2000server (let me call it server A)that is not a DC. It currently has one
    database application that is used by about 20 users.

    Inside of this subnet is another network using an SBS2003 server premiun
    running ISA. It has about 10 users and a windows2003 member server that is
    not a DC (let me call it server X). I would like to move my application on
    server A to server X. I want to move everyone to the SBS2003 network
    eventually but can't do to all at once.

    Can I safely move the application on server A to server X, install a second
    NIC in server X and allow users in both subnets access this application? This
    application requires a shared folder that must be set up as mapped drive to
    its client that resides on each workstation. I do not want in any way want
    to route
    these 2 subnets together which would bypass the ISA server in SBS2003 . If I
    can do this, it would allow me to start moving users one at a time and work
    out the "bugs" as I go.

    This would seem doable but I suspect there is a hidden flaw in there
    somewhere!
     
    Joe, Oct 1, 2005
    #1
    1. Advertisements

  2. Joe

    Bill Grant Guest

    How would routing between these subnets bypass the ISA server? It is not
    hard to have two subnets talking to each other but both behind a firewall.
    If you put two NICs in server X you could use it to route between the
    subnets, rather than moving the application on to it.

    Is the sbs server running NAT or are you using it as a proxy server?
     
    Bill Grant, Oct 2, 2005
    #2
    1. Advertisements

  3. Joe

    Joe Guest

    Server X is in the SBS domain. Both Server A and the SBS server are behind
    the same hardware firewall. The SBS server WAN NIC connects to the orginal
    network thru ISA. It started out as one network. There are actually about 40
    PCs and 10 networked printers in this network going out on the orginal
    firewall via DSL. The SBS has been added along with a 2003 member server X.

    The application is going to be moved to server X as part of the upgrade as
    well as joining everyone to the SBS . This one application is the only hold
    up. Manpower constrains make it very hard to move everyone at once.

    The internal SBS network is a DHCP, DNS, NAT, Full blown SBS, etc

    Here is a "Diagram". I believe you can see why routing can't be done on
    server X between the two networks. If I could open server X for a short
    period of time to both networks it would make thing easer.

    Internet via DSL Internet
    ---------------Cisco Firewall -----------------------
    Old Peer-to-peer net work 40 users/ Server A
    SBS server "WAN NIC" Private
    network 1
    ---------------SBS ISA fire Wall -------------------
    SBS "LAN NIC" , 10 PCs, Server X Private
    Network 2
     
    Joe, Oct 2, 2005
    #3
  4. Joe

    Bill Grant Guest

    In theory, putting the server in both networks with no routing enabled
    should work. I know that lots of places run setups like that, although I
    have never done it myself. The problem is that the server now has two IP
    addresses, one in each subnet. This can cause name resolution and browsing
    problems. You would need to stop the computer browser service on this server
    (so it can't be a master browser in either segment) and make sure you don't
    get the "wrong" IP registering in the DNS on the SBS server. And if this
    server needs Internet access, the default gateways allocated by the two
    different DHCP services could be a problem. You may need to configure its
    NICs manually to have a default gateway to the firewall only.

    Putting the original network "inside" the new network behind the SBS
    server would be difficult because it would no longer be able to see the
    firewall directly, and would be a major reconfig (not worth the effort).
     
    Bill Grant, Oct 3, 2005
    #4
  5. Joe

    Joe Guest

    Thanks for the assistance. I am going to try it first in a offline setup in
    my shop and I will use your tought on brousing (had not even tought about
    that aspect). Do you agree that in this setup that routing would not be
    appropiate?
     
    Joe, Oct 3, 2005
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.