RWW Fails using Web Interface, but works using Remote Desktop Connection

Discussion in 'Windows Small Business Server' started by Stuart Mackie [MCP, MSP], Jul 20, 2004.

  1. Hi. We recently changed from a single nic to a dual nic setup. We ran the
    ICW to allow for both nics and have had no problems until today when we
    tried to use RWW through the web interface to access our serve within the
    internal LAN. On selecting the Server on the web interface it attempts to
    connect and then we get the error:

    "Connectivity to the remote computer could not be established. Ensure the
    remote computer is on and connected to the Windows Small Business Server
    Network"


    If instead we use the Remote Desktop Connection on a Windows XP workstation
    and connect to the server's internal nic on 10.0.0.10 it works without any
    problem. I haven't had any time or access to actually try connecting
    remotely from outside our network.

    I have also tested viewing the Performance and Usage Reports and they work
    fine. When we through the ICW we did select the options we required which
    included RWW, and we have no other problems with connectivity etc.

    External Nic:
    IP: 10.0.1.10
    Subnet: 255.255.255.0
    Gateway: 10.0.0.1

    Internal Nic:
    IP : 10.0.0.10
    Subnet: 255.255.255.0
    Gateway: blank
     
    Stuart Mackie [MCP, MSP], Jul 20, 2004
    #1
    1. Advertisements

  2. Hi Stuart,

    Something is not right in your external nic setup. IP and Gateway should be
    in the same subnet.
     
    Marina Roos [SBS-MVP], Jul 20, 2004
    #2
    1. Advertisements

  3. Hi Marina. I remember we spoke about this before and we did use the
    settings discussed to start with :) Once it was up and working we
    reconsidered what we needed to achieve, and using this configuraition still
    accomodated the different subnets and still gave us the network flexibility
    required.

    Unless I've worked this out wrong, a subnet mask of 255.255.255.0 starting
    with IP 10.0.0.1 makes subnet one (Internal Nic) 10.0.0.1-10.0.0.254 and
    subnet two (External Nic) 10.0.1.1-10.0.1.254
    If for example we set the external to 10.0.0.1 and the internal 10.0.0.2
    then it doesn't work, but the current configuration uses different subnets
    and we haven't had any problems with anything other than RWW. All other
    services such as VPN, OWA etc all work as expected.

    --
    Thanks,
    Stuart Mackie [MCP, MSP]
    www.stu.uk.com
     
    Stuart Mackie [MCP, MSP], Jul 20, 2004
    #3
  4. Hi Stuart,

    IP and Gateway should be in the same subnet. You have the gateway pointing
    to what????

    --
    Regards,

    Marina
    Microsoft SBS-MVP

     
    Marina Roos [SBS-MVP], Jul 20, 2004
    #4
  5. I'll need to double check, but the Gatway router should have the
    configuration below. It could be we've had a little over-sight on the
    external nic configuration :)

    Router:
    IP 10.0.0.1
    Subnet: 255.255.254.0

    What issues should arrise if we are using this configuration ?

    --
    Thanks,
    Stuart


     
    Stuart Mackie [MCP, MSP], Jul 20, 2004
    #5
  6. Stuart,

    If you have your Router at 10.0.0.1 and your internal nic on 10.0.0.10, you
    have a problem.

    --
    Regards,

    Marina
    Microsoft SBS-MVP

     
    Marina Roos [SBS-MVP], Jul 21, 2004
    #6
    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.