[p4] Dial-up - Steve Smythe - com.perforce.perforce-user

5 messages in com.perforce.perforce-user[p4] Dial-up

From	Sent On	Attachments
Hemantharaju Subbanna x4832	05 Dec 2002 10:48
Todd Short	05 Dec 2002 11:22
Dave Foglesong	05 Dec 2002 11:26
Steve Smythe	05 Dec 2002 11:28
Timmy Nguyen	05 Dec 2002 13:20

Subject:	[p4] Dial-up
From:	Steve Smythe (ssmy...@docent.com)
Date:	12/05/2002 11:28:21 AM
List:	com.perforce.perforce-user

Check out http://www.speedguide.net for their tuning tool. I've used it at home on my cable modem connection. Works great! I haven't used their tuning on dialups, but they have a lot of information on tuning and tweaking.

Steve

-----Original Message----- From: Dave Foglesong [mailto:dfogleso at adobe.com] Sent: Thursday, December 05, 2002 11:26 AM To: Hemantharaju.T.Subbanna at nsc.com; Perforce UserGroup Subject: RE: [p4] Dial-up

Are they using some kind of VPN client? I've seen behavior like this that has been solved by lowering the MTU value in the VPN client being used.

-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Hemantharaju Subbanna x4832 Sent: Thursday, December 05, 2002 10:49 AM To: Perforce UserGroup Subject: [p4] Dial-up

Hi, I have attached a mail from one of our users. Any input is greatly appreciated.

----

One thing that is particularly troublesome while using Perforce

from my home PC (over a 56K dialup >connection) is that it will not allow me to submit updates exceeding a certain number of files or a certain >number of bytes (and just what that magic number is I don't know). That is, if I've opened a large number >of files for edit, and then submit them later on, it will actually disconnect from the dialup

server. It will >proceed for some time as if it is checking the files

back in, but then, towards the end, it hangs up the >connection. I can get around this by breaking the submission into several smaller submissions. Am I >violating some Perforce rule or something??

----- First shot I thought that is would be due to some default time-out set

somewhere and peforce has nothing to do with this. I still believe so.

Thank You Raju