Re: SQL*Net through the modem
From: Chris Little <clittle_at_valueamerica.com>
Date: 1996/08/20
Message-ID: <01bb8eb4$02b38ec0$83e863ce_at_pc001.valueamerica.com>#1/1
Date: 1996/08/20
Message-ID: <01bb8eb4$02b38ec0$83e863ce_at_pc001.valueamerica.com>#1/1
I have done this myself and agree with Chuck. When connected via modem, the home PC is just another node on the network. I had SQL*Net V1 running VERY slowly from home over 14400 and 28800 baud modems. When I upgraded the network to SQL*Net V2, it didn't work anymore -- no errors, just a time-out. I've a feeling that the overhead associated with V2 was too much for the modem connection.
-- Chris Little Value America clittle_at_valueamerica.com http://www.valueamerica.com/ Chuck Hamilton <chuckh_at_dvol.com> wrote in article <3219c4d6.4851799_at_n5.gbso.net>...Received on Tue Aug 20 1996 - 00:00:00 CEST
> "Scott T. Johnson" <sjohns6_at_ibm.net> wrote:
>
> >I would like to be able to work with Developer/2000 at home. The Server
> >at work has Oracle and SQL*Net. Can SQL*Net be configured to answer
> >the modem and accept a connection. What would I need on the client
> >(home) side?
> >
> >Thanks,
> >Scott
>
> I haven't done this myself, but I don't think it's even a SQL*Net
> configuration question. The physical connection should be handled at
> the network layer (TCP, IPX), not the application layer (SQL*Net). If
> it's tcp/ip, you need to run either PPP (point to point protocol) or
> SLIP (serial line IP). As far as SQL*Net's concerned, it's just a plan
> old TCP/IP connection.
> --
> Chuck Hamilton
> chuckh_at_dvol.com
>
> Never share a foxhole with anyone braver than yourself!
>