From: "Jeff Middleton" <cfo...@compuserve.com>
Subject: Re: RRAS ISDN connecting two remote SBS 4.5 Servers
Date: 2000/01/07
Message-ID: <#5xB18SW$GA.265@cppssbbsa04>#1/1
X-Deja-AN: 569607886
References: <#HK00sSW$GA.221@cppssbbsa02.microsoft.com>
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-MSMail-Priority: Normal
Newsgroups: microsoft.public.backoffice.smallbiz

Normally, it doesn't make sense to have the links not function in the same
way.  If one end is set to nail up the connection, that's what it will do no
matter what the other end wants.  If the connection drops, it's gonna dial
back anyway.

If you have no long distance cost, then nail them up.

To troubleshoot your situation, you need to separate the issues on
establishing the link vs. getting traffic through....they really don't have
anything to do with each other.  Think of bringing the link up as like
placing a phone call to you mother: Just because the line is connected,
doens't mean you are communicating, right?  (sorry mom)

If you can get the line up and maintain the connections as you have
preferred (nail up or DOD), then you switch to the IP communications
problem.

Normally, if you can ping one way, but not back, this is because a gateway
or route is missing on one end...it's that simple.  Remember, a ping needs
to have a way over and back...it must make a complete circle.  Every
interface needs a gateway to the next hop out of the segment.  Establishing
a static route on each server is normally required for server to server
communications.  Did you enable routing on the RAS configuration and the
servers as well?

In the case of SBS servers, you need to make sure the IP ranges for all
segments are not in the Proxy LAT to allow direct communications.




Scott Austin <saus...@benchmarktape.com> wrote in message
news:#HK00sSW$GA.221@cppssbbsa02.microsoft.com...
> HELP!
>
> I am at my wits end!  My situation is that I have two SBS 4.5 (SP5)
servers
> running at 2 remote sites.  Up until a few days ago we had them connecting
> via RRAS over a modem connection and everything was fine (occasionally, I
> had to stop and re-start the RRAS service when the link went down, but it
> was liveable).
> Now, we have upgraded to an ISDN 128k US Worst link between the two sites.
> The hardware is a 3Com ISDN 128k Terminal Adapter on both ends connected
to
> the server on Com1.  NT recognizes the 3Com TA just fine on both servers.
> However, when I try to establish the connection via RRAS, it does not
work.
> As far as RRAS changes go, I have added Multilink functionality on both
> servers in both the RRAS service and RRAS specific interface and just
> changed the interface connection type from the original modem to the new
> 3Com ISDN TA so that all my IP settings and routes would remain the same.
> Since then, I have tried to completely re-create every aspect of RRAS
> including interfaces and static routes.  I have been through hundereds of
> TechNet searches but none seem to talk about this stituation specifically.
> I have verified with USW that their switch protocol is DMS-100 and have it
> set that way in the 3Com config.  I have a few specific questions...
>
> 1.  With the modem link before, we had one RRAS server connection set to
> persistent and the other RRAS server was set to dial-on demand.  With ISDN
> do you have to run in the same manner or do you need both set as
persistent?
> 2.  Do I need to have one or two dial-on demand interfaces defined on each
> server to handle multilink?  My guess is no but who knows.
> 3.  I did at one point get one Server A to run connect to Server B and
allow
> pings to it.  However, when I tried to ping back across the link (from
> Server B to A) it gave me a destination host unreachable error.  When I
went
> to look at RRAS on Server B, it's status was Unreachable with an error
> stating the modem device or port was busy.
>
> What am I missing here?  If you happen to have a specific Q article that
> covers this in detail, please direct me to it.
>
> THANKS!!
>
>
>
>