New ISP, slow Remote Desktop and FTP??

[Rob Phillips]

I recently was switched to a Comcast customer after they
bought out portions of my previoud provider. Since the new
ISP came in, my remote desktop and FTP server I use
between work and home has gone from about a 190 kbs.
average transfer spped to about 30 kbs. I can access the
internet fast as ever needed from the host PC via Internet
Explorer or other downlaoding programs. I ran some
bandwidth tests using several different sites/ methods.
They all return great speeds! However, when I remote in, I
get alot of lag like there's no bandwidth to be had. I
have the same problem with my BulletProof FTP server I
use. The kbs is horrible now. All other internet apps. run
fine/ fast. What could be the cause of this?? I haven't
changed anything at home w/ the exception of the IP
address through the new carrier, and adding thier DNS
information as I wasn't getting the speed I wanted overall
by allowing the PC to detect the network settings. I would
imagine if I can get great d/l speeds through one
application, I ought to be able to get fast connections
through all of them, right?

 

[Jeffrey Randow (MVP)]

What is your "upload" bandwidth? This typically is much slower than
the "download" speed... Since it affects all of the services - I
would tend to believe that Comcast may be capping your upload speed.
Do another speed test to compare your upload speed.

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Robbo]

I have had the upload test at 256 using
http://dfw.speakeasy.net/ , which is what the cable guy
used when he was here today. They can't find any problems
(of course) so I'm left to deal with it myself. I had a
friend in NY log onto my FTP and he could only pull 30.00
kbs max. I would think it wa a software issue if it were
only the FTP application. Remote Desktop is incredibly
slow, too, though, and that leads me to believe it's
something bigger.

 

[Bill Sanderson]

Have you done any testing--maybe using the tools at dslreports.com? Seems
like a stretch since your performance was fine with the previous ISP, but
maybe something'll show up.

 

[Jeffrey Randow (MVP)]

Maybe a MTU setting? If FTP is slow as well, it leads me to believe
it is an upstream bandwidth problem.

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Rob Phillips]

I checked the MTU using ping www.dslreports.com -f -l 1472
and got the following results. I couldn't make the packet
size any higher than 1472 without fragmenting. Is ths a
good result to get? I really don't know too aweful much
about packets and such.

Pinging dslreports.com [209.123.109.175] with 1472 bytes
of data:

Reply from 209.123.109.175: bytes=1472 time=51ms TTL=50
Reply from 209.123.109.175: bytes=1472 time=52ms TTL=50
Reply from 209.123.109.175: bytes=1472 time=50ms TTL=50
Reply from 209.123.109.175: bytes=1472 time=54ms TTL=50

Ping statistics for 209.123.109.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 54ms, Average = 51ms

I had also used the sdlreports "tweak tester" and got the
following:

1. Your Tweakable Settings:
Receive Window (RWIN): 64240
Window Scaling: off
Path MTU Discovery: ON
RFC1323 Window Scaling: OFF
RFC1323 Time Stamping: OFF
Selective Acks: ON
MSS requested: 1460
TTL: unknown
TTL remaining: 113

2. Test 146000 byte download
Actual data bytes sent: 146000
Actual data packets: 100
Max packet sent (MTU): 1500
Max packet recd (MTU): 1500
Retransmitted data packets: 0
sacks you sent: 0
pushed data pkts: 5
data transmit time: 0.437 secs
our max idletime: 161.5 ms
transfer rate: 140175 bytes/sec
transfer rate: 1121 kbits/sec
This is not a speed test!
transfer efficiency: 100%


3. ICMP (ping) check
Target unpingable




Notes and recommendations:
RWIN is in range
Looking good

Notes and recommendations:
Good data stream (no/few rexmits)

Notes and recommendations:
Become pingable
if you need basic packet loss tests done
Check tweak FAQ


Again, I have no idea if these are ideal or not. I have
made the changes to make the PC Pingable, but will not
reboot until I get home. (I did it through remote desktop
while I was @ work).

 

[Bill Sanderson]

1472 is exactly right. If you add in 28 bytes of overhead of various sorts,
this comes to a 1500 byte packet, which is standard.

So--this rules out MTU issues.

 

[Rob Phillips]

I have just ruled out the slowness being a problem with
the specific application I use for FTP, BulletProof. I
started another FTP program called SmartFTP and uploaded
some goods to my buddy in NY. It also maxed out at exactly
30.00kbs. There's some global setting somewhere that
limiting my upload on everything I need it for with the
exception of IE. That's the only app. that seems to be
able to break the unkwown barrier.

 

[Rob Phillips]

I just ran an upload to the same FTP server from an
Internet Explorer window while I was uploading to the same
server through an FTP program. I checked the total upload
speed using an application called NetStat Live. It was
reading upload speeds (combined) of over 175kbs while I
was using both applications to upload to the New York FTP.
Is there maybe something in IIS that would cause conflicts
for FTP or Remote Desktop?? That's he only thing I can
think of adding to the OS of my home PC that is related to
up/ downloading. (Note: I don't use the FTP from IIS.)