ADSL vs Modem.....short packet problem???

[medsun]

Folks, I'm no techie but I am having horrendous problems with my new ADSL connection and my ISP/Comms carrier don't seem to be close to solving this problem - so I have decided to turn to you in the hope that you will solve my problem and I can pass on your suggestions to them.

I have a PC configured with Windows 98 which I have used for months on a dial up service (56K) to my ISP. Since installing ADSL (via an Alcatel Speed Touch Home) I am experiencing a problem which appears related to packet sizes. I cannot send emails above approximately 1 line long in HTML format (a bit longer in Plain text). I am also unable to use Hotmail or other Browser based data input facilites where I send about a third of a page of data. With video conferencing I can receive but not send video pictures. I can download from Freedrive/Xdrive etc but cannot upload; same with Napster - I can download but if anyone tries to take MP3s off me they get transfer errors. My browsing works without a hitch (except fro the hotmail etc).

All of the above problems disappear when I disconnect my connection and reconnect with my dial up connection. When I swapped ADSL accounts (ie I borrowed a friend's) I got the same problems - whcih suggests an ADSL line problem on the upload with packets above a certain size. Net2phone works fine with ADSL - no 'upstream' problems there!

Any ideas folks????

Thanks

Julian

PS Ironically I had to reconnect with my dial up to submit this post cos the ADSL one timed out!!

 

[PreyTell]

In the client server world that you are in now, if you are connected there is not a short packet problem. Short packets would not cause single services not to work. So I think your problem is either your ISP/DSL provider blocking all but known ports to limit your traffic. Or the client software they provided you is buggy. What happens when you try to send more then one line emails, you A) lose connection? B) Get an error. or C) everything appeared to go fine but only one line shows up on the other side. The fact that "normal" browsing is not affected leads me to believe that it is your ISP messing with port numbers and protocol filters.
[sig][/sig]