in win3.1x
main/control panel/ports/select port/settings/
set speed to 19200... windows comm.drv doesnt understand largrer than
19200
flow control to hardware at the bottom....
dont forget some modems are RPI... then you need rpi stuff from
rockwell...
the same needs to be done for win95 people...
start/settings/control panel/system/ports(com and lpt)/whatever
ports/device manager/port settings/
set speed at top and use hardware flow control on the bottom...
ymmv, yet its always worked for us...
--->
Robert H. Hanson LAN/WAN Consultant - Internet Service Provider
Otis Orchards, Wa. Cutting Edge Communications www.cet.com
(509) 927-9541 finger: info@cet.com or email: roberth@cet.com
On Wed, 4 Sep 1996, John Storms wrote:
> When I worked as an ISP I noticed this as well. At the time our users used
> Trumpet Winsock exclusively and we were able to correct the problem by
> changing the configuration in Trumpet Winsock to use hardware handshake
> (this is a check box under file | setup).
>
> At 10:15 PM 9/3/96 -0400, you wrote:
> >I repeatedly probe this list to see if anybody has any ideas as to what
> >could be happening to me. Here's another shot.
> >
> >Users to my system can't seem to upload large files outbound from the local
> >network to the internet when connected via dial-up. All our dialup ports are
> >through Livingston PM's and 2 USR Netserver/16's.
> >
> >Folks can download like snot, but when they try to send data outbound
> >transfers die after a very short duration. (between 10k and 100k)
> >
> >I suspect either the packet filtering that our Cisco 2501 is doing or
> >something in the PM's. Users who FTP to one of our local machines FIRST and
> >then use the local FTP from the Unix box can upload outbound without
> >problems however.
> >
> >Any ideas ?
> >
> >-Kurt
> >
> >
> >
>
> ---
> jstorms@livingston.com
> The poor seek food, the rich seek an appetite. -- fortune cookie
>