Computing.Net > Forums > Networking > 3com OCR 812 Problem FTP timeouts

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

3com OCR 812 Problem FTP timeouts

Reply to Message Icon

Name: Anni
Date: June 11, 2003 at 07:16:53 Pacific
OS: WIN xp
CPU/Ram: 1.7gb 1024 ram
Comment:

Hi
I have been getting major timeouts when ftping to a particular site in America since 27th May. I assumed the problem was at their end and asked them to investigate. They said their was no problem but that they were getting ICMP timeouts when they tried doing a traceroute to the IP address I was connecting from, and started getting ICMP timeouts when it started polling the routers on my DSL providers network. I have since been able to replicate the issue from some other US based servers doing a traceroute from CALIFORNIA US to 81.86.161.58 (Traceroute attached below). I have never previously experienced these problems and have been ftp'ing to these servers weekly since I had my ADSL installed almost 2 years ago so the problem is new and started around the 27th May. I have tested with the following set ups:

Used Pipex dial and 56k modem, no router, FTP and US Tracert's - no problem
Used a different pipex dsl account and line (we have 2) with router and current network setup - FTP and US Tracert's - problem still exists
Used Zoom DSL modem to connect to pipex dsl account - FTP and US Tracert's no problem.
Therefore the problem has to be either with my router setup or my network setup...
But I just can't see what it can be as I haven't changed anything that I know of and it used to work fine..

The timout only happens with certain FTP servers based in the US. I have tried a number of servers in the US and a number of FTP clients including ftp.exe from the command line - all with the same problem.
I don't have a firewall. I do have a dsl router 3com ocr 812 I have tried with and without filters to no avail.
I have had the router set up for almost 2 years and have not changed any settings. The particular FTP server that I am most concerned about accessing in the US is that of my webhost. Again I have been accessing them with no problems for 3 years or more.

So, I haven't changed any of my settings, or hardware etc (that I can think of) and am not trying to access the FTP server for the first time. I had my webhosts check their end and they were the ones who told me about the tracert problem. But the tracert problem only shows up when it is performed from certain servers in the US.
If it is done from with in the UK, it is fine.

I did the dsl tweaks ages ago, but redid them yesterday to be doubly sure... I have speeds of 477 down and 246 upstream.
My webhost suggested my NAT tables might be full, but I can't see anyway of checking or changing this, so I can't follow through on that possibility...

My router is set up as a dhcp server for 2 pcs (1 XP Home and 1 Win98) connected by Cat C ethernet Belkin USBs and 1 wifi AP with laptop (XP Pro) connected.
System Summary
IP Routing: Enabled
IPX Routing: Disabled
DHCP: Server
Bridging: Disabled
DNS: Enabled
Filtering: Enabled
Remote Sites: 1 Configured
Remote Site Settings (X = Checked and - = unchecked)
Remote Site Name Remote_Site
Enable Remote Site X

Network Service PPP over ATM (PPPoA) X
User Name XX
Password XX

VC Parameters VPI 0 VCI 38

Quality of Service: Unspecified Bit Rate X Constant Bit Rate - Constant Cell Rate -

Enable Bridging - Enable IP Routing X Enable IPX Routing -

Address Translation =NAT
Default Workstation: 0.0.0.0
Accessible LAN Servers: Static Ports None defined
Static IP Routes none defined

Routing Information Use this connection as default gateway
RIP None

DNS Pass DNS requests to domain name servers whose addresses have been dynamically learned from this remote site. X have also tried specifying the DNS and it makes no difference
Security Verify that incoming packets can be routed back to the packet's source address using Source Address Validation. -
Enable the "Protect Files and Printers" filter to prevent outsiders from accessing your internal printers and files (recommended). X (Note I have tried deselecting this to no avail)
Remote Site IPX
Routing Information IPX Routing: Listen
Routes / Services None defined

IP LAN Settings
IP LAN Network NAME: ip
IP Address: 192.xxx.xxx.254
IP Mask: 255.255.255.0
RIP: None

DHCP Use this IP network as the DHCP server X
Domain Name: dummy.net
IP Start: 192.xxx.xxx.1
# Addresses: 4
Lease Timeout: 4800
WINS: 0.0.0.0 0.0.0.0

EXAMPLE bad tracert's from US:
Traceroute to 81.86.161.58
01:30:20 PDT (-0700) Wed May 28, 2003 from davespeed.com server in Fremont, CA


1. 216.65.7.157 (216.65.7.157) 0.840 ms
2. 209.25.128.37 (209.25.128.37) 0.504 ms
3. 66.40.24.101 (66.40.24.101) 0.723 ms
4. 66.40.24.110 (66.40.24.110) 0.931 ms
5. sntcca2lce1-gige.wcg.net (64.200.150.33) 0.838 ms
6. sntcca2lce2-pos6-0.wcg.net (64.200.151.130) 0.899 ms
7. bpr2-ge-4-3-0.PaloAltoPaix.cw.net (206.24.241.245) 0.905 ms 8. dcr2-as0-0.SantaClara.cw.net (208.172.147.65) 2.611 ms 9. bcr1.Frankfurt.cw.net (166.63.194.61) 162.141 ms 10. zcr2-so-1-2-0.Munich.cw.net (166.63.195.182) 168.171 ms 11. so-0-2-0.TR2.FFT1.ALTER.NET (146.188.6.113) 168.754 ms 12. so-1-0-0.TR1.LND9.ALTER.NET (146.188.15.29) 166.998 ms 13. so-5-0-0.XR2.LND9.ALTER.NET (146.188.15.38) 167.035 ms 14. pos2-0.gw1.lnd9.alter.net (158.43.150.146) 166.778 ms 15. PIPEX-gw3.customer.ALTER.NET (146.188.56.98) 166.999 ms 16. 62-241-161-2.dsl.pipex.com (62.241.161.2) 167.269 ms 17. * 18. * 19. * 20. * 21. *

Halted after 5 nonresponsive hops
Traceroute to 81.86.161.58
01:31:18 PDT (-0700) Wed May 28, 2003 from davespeed.com server in Fremont, CA

1. 216.65.7.157 (216.65.7.157) 19.761 ms
2. 209.25.128.37 (209.25.128.37) 0.574 ms
3. 66.40.24.101 (66.40.24.101) 0.893 ms
4. 66.40.24.110 (66.40.24.110) 0.990 ms
5. sntcca2lce1-gige.wcg.net (64.200.150.33) 1.088 ms
6. sntcca2lce2-pos6-0.wcg.net (64.200.151.130) 0.831 ms
7. bpr2-ge-4-3-0.PaloAltoPaix.cw.net (206.24.241.245) 1.222 ms 8. dcr2-as0-0.SantaClara.cw.net (208.172.147.65) 4.013 ms 9. bcr1.Frankfurt.cw.net (166.63.194.61) 162.461 ms 10. zcr2-so-1-2-0.Munich.cw.net (166.63.195.182) 168.629 ms 11. so-0-2-0.TR2.FFT1.ALTER.NET (146.188.6.113) 168.757 ms 12. so-1-0-0.TR1.LND9.ALTER.NET (146.188.15.29) 167.013 ms 13. so-5-0-0.XR2.LND9.ALTER.NET (146.188.15.38) 166.935 ms 14. pos2-0.gw1.lnd9.alter.net (158.43.150.146) 167.491 ms 15. PIPEX-gw3.customer.ALTER.NET (146.188.56.98) 167.153 ms 16. 62-241-161-2.dsl.pipex.com (62.241.161.2) 167.212 ms 17. * 18. * 19. * 20. * 21. * 22. * 23. * 24. * 25. * 26. * 27. * 28. * 29. * 30. *

I appreciate your help


Anni




Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: 3com OCR 812 Problem FTP timeouts

3COM switch duplex problem www.computing.net/answers/networking/3com-switch-duplex-problem/14310.html

Linksys router FTP problem www.computing.net/answers/networking/linksys-router-ftp-problem/10812.html

3com 4228g Switch problem www.computing.net/answers/networking/3com-4228g-switch-problem/23830.html