Re: Connecting satellite locations via the Internet

Our clients have had good success connecting satellites via the
internet.

The key has been understanding how the internet works.

If home office has ISP abc and satellite has ISP xyz there is no way of
determining the number of hops and lag time in advance for planning
purposes.

For example, we have a client which has a static IP address provided by
their ISP, connected via ISDN 2 channel basic service.  The remote
office uses the same ISP and has very few hops. (pings average 40-50ms)

Anther client has two different ISP's, 21 hops with 10-210ms per hop.

Personally I would stick with a backbone provider and not just a channel
provider.  The clue is .net instead of .com

Roger Pence wrote:
> 
> Gary--
> 
> >So, what's the verdict?? Private lines at sometimes unbelievably high costs
> >(which are declining....slowly) or access to the Internet at each site
> >reducing on going operational expenses.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---