Announcement

Collapse
No announcement yet.

Routing Issue

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Routing Issue

    Not sure where to post this so here goes here..

    Ok interesting problem here..
    The Aim is to provide termminal servers to 4 users even if local Company B Internet is Down

    2 Offices

    Company A on 192.168.10.0 Range
    Company B on 192.168.11.0 Range

    Each company has it's own domain contoller
    192.168.10.15 Company A Domain Controller
    192.168.11.10 Company B Domain Controller
    Each Company Has a Sonic Firewall
    192.168.10.10 Company A Sonic (Leading to a ADSL) Fixed public IP
    192.168.11.5 Company B Sonic (Leading to a ADSL) Fixed public IP
    Each Company has a ISDN connection (Normally Switched off)
    192.168.10.1 Company A ISDN
    192.168.11.1 Company B ISDN
    Terminal Services is offered from Company A
    192.168.10.16 Company A Terminal Server


    Internet Fails on Company B:
    ISDN is Switched on in both companys
    On the Server of Company A
    ROUTE ADD 192.168.11.0 mask 255.255.255.0 192.168.10.1 -p
    On the server of Company B
    ROUTE ADD 192.168.10.0 mask 255.255.255.0 192.168.11.1 -p
    All local Company B PC's change their default gateway to 192.168.11.1
    and should now be able to connect to the terminal server on 192.168.10.16


    What actually happens is from Company B
    they can ping 192.168.10.1 (ISDN)
    they can ping 192.168.10.10 (Sonic - Lan Side Responding)
    they can ping 192.168.10.15 (Server)
    they cannot ping 192.168.10.16
    They can ping 192.168.10.160 (A printer)


    Why can they not see the terminal server on 192.168.10.16
    Localy the terminal server will respond to pings.

    Over to comments
    Regards
    Colin

    C.R.E JEWISON

  • #2
    Re: Routing Issue

    Did you check in the firewall policy that users able to connect to the TS? Is from the firewall in company B you can ping/telnet the TS?
    BTW - It will be more easy and smart that the firewall will manage all the routing and you wouldnt need to change settings manually.

    Regards,

    Yuval
    Last edited by yuval14; 25th October 2005, 20:48.
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: Routing Issue

      Doesn't matter about the firewall, the isdn is a site to site link both companys are part of the same comapany, so each isdn link is behind the firewall.
      Regards
      Colin

      C.R.E JEWISON

      Comment


      • #4
        Re: Routing Issue

        Ok I have a Fix


        Issuing the same routing command on the terminal server allows users to access the terminal server

        route add 192.168.11.0 mask 255.255.255.0 192.168.10.1 -p

        without this the replys from Terminal Services or a ping will not know how to get back to Company B

        Cheers
        Last edited by cjewison; 26th October 2005, 10:23. Reason: Spelling
        Regards
        Colin

        C.R.E JEWISON

        Comment


        • #5
          Re: Routing Issue

          do you have port 3389 open?
          terminal services requires port 3389

          You might test by running a telnet session using port 3389

          Comment

          Working...
          X