🚀 go-pugleaf

Sounds silly and maybe redundant, but did you verify your DNS as being set
upo correctly for your IE or Netscape?  You can also go into a DOS prompt ad
type PING plus the IP address of your FTP account.  That will verify if it
is your DNS or if it a problem elsewhere.  If you'd like to call, I can try
to help you check all of this.  I'll be in from about 7:30 am until about
6:30pm tomorrow

Dan McFarland
Nations Access
888-525-2721

Vince <vincei@swbell.net> wrote in message
news:38C44B88.ACA109E0@swbell.net...
> I am having trouble ftping to my web page that is hosted on Interland.
> I have been using swbell as my ISP for over six months and have also had
>
> this Interland account for a while, but have just been having problems
> the last few weeks.
>
> When I try to ftp to my server, it connects and list the directory
> contents, but then freezes.  Other ftp programs can't even connect.
> Others can ftp into this same server without problems.  The problem
> happens if I connect through my ADSL modem or if I dial in to my Dallas
> number.
>
> I can ftp into my Interland account if I connect with my gfs Internet
> America account, using my same home computer and the same other
> software.
>
> Tonight I tried to use a different swbell access number, a long distance
> number from McAllen,
> and I was also able to ftp into my account with trouble, but still
> couldn't from my Dallas dialup number or my ADSL.
>
> I think it is a routing problem with swbell somewhere.  I emailed
> support@swbell.net and was told to call Plant Operations, who told me to
>
> call the swbell ISP tech support people, who sent me to the DSL people,
> who sent me to the web hosting people (even when I told them that swbell
>
> wasn't hosting the ftp account).  The tech support guy at the web
> hosting number couldn't help me, but told me to talk to the ISP tech
> support again and get them to ping my IP address and do a trace route
> and if they weren't helpful to ask for a manager.  The ISP tech support
> suggested I email the homepage@swbell.net people and I asked to talk to
> a manager who said I needed to talk to the DSL tech support again and
> get them to upgrade it to the Network Operations Center, who I am
> waiting on.
>
> Each time you have to wait on hold for ten to fifteen minutes.  Very
> frustrating...
>
> I think the fact that others can use my ftp account and even I can use
> it if I use a different ISP or even a different (long distance) access
> number to swbell means that it is not a problem local to my computer or
> to my Interland ftp account.  It has to be a problem in the way swbell
> is routing my connection, doesn't it.
>
> Everything else works great with my ADSL connection.
>
> --
> VinceI
> http://www.keepkidshealthy.com
>
> --
>
> VinceI
> http://www.keepkidshealthy.com/
>

In article <38C44B88.ACA109E0@swbell.net>, vincei@swbell.net says...

>Everything else works great with my ADSL connection.


I had a similar problem when I changed from IA ISDN to Directlink ADSL.
I could not ftp into my web site anymore. I think it was some kind of DNS 
lookup problem that the ftp host was initiating but it was timing out, and 
log in failed. 

However, I could change the ws_ftp timeout parameter to 120 seconds, and it 
would then always work after about 65 seconds. Ater it timed out at 65 seconds, 
then the logon worked.  Frustrating, but it worked.  IA dialup continued to 
work fine and quickly while I had that available.  Other ftp sites were OK too 
via ADSL, no timeout, but not my own site.  I'm thinking the password logon 
works differently than anonymous login.

I fussed at both ends, with no luck, no one knew nothin', and it still took a 
minute to log in via ftp. Then after about a month, the problem mysteriously 
corrected itself, and its been fine since, no timeout anymore.  Still dont have 
a clue.

-- 
Wayne
fulton@scantips.com
http://www.scantips.com    "A few scanning tips"