dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2132
share rss forum feed

Rebellious

join:2008-05-28

BellSouth FTP server down

No more personal web pages in home.bellsouth.net?

I have very modest requirements. Where can I get some free online storage? OR

How hard is it to install a server on one of my Linux machines, and host my own?


IndyPremTech

join:2013-08-01
Indianapolis, IN

Do you have static IP's? Do you know how to install and configure apache? If so, piece of cake!


Rebellious

join:2008-05-28

No I have TW cable, I believe IP changes every 24hrs. Is there a way around that?


Rebellious

join:2008-05-28
reply to Rebellious

BTW home.bellsouth.net says -- Connection attempt failed with "ENETUNREACH - Network unreachable".



BellSouthPWP

@comcast.net
reply to Rebellious

I have five home.bellsouth.net PWP sites, and three pwp.att.net sites and I uploaded updates to all of them using FTP early this morning (~4 AM) with no problems. I also just now logged into all of them with CuteFTP and had no problems.

Either there is a problem with your BellSouth PWP account, a problem with your FTP client or network settings, or a temporary problem with your connection.

As for your other question about setting up an FTP server on a Linux box, that is not all that difficult. I think that most (if not all) Linux distros come with at least one FTP server daemon. But that question would probably be better asked in the »All Things Unix forum.

FWIW, I run a Pure-FTP server on openSUSE with no problems. Your biggest config/setup problem will probably be the port forwarding config for a NAT router. And with a NAT router, you will also likely need to setup the FTP daemon and the NAT router to use PASV for the FTP server (which means extra firewall rules on the server box, and extra port forwarding rules in the NAT router).

I do not have a public static IP address, but I use Namecheap as my domain registrar, and they support their own DDNS service (I use Lynx in a cron script to sync with the Namecheap DDNS service because I am syncing multiple domains and hostnames, but ddclient also works well if you only have a single hostname to sync). Namecheap also has a FreeDNS service, but I think using their FreeDNS service requires you to already have a valid domain registration. Since DynDNS stopped allowing new free dynamic DNS registrations, the availability of free DDNS services has gotten slim. If you happen to have a relatively new D-Link router, you may be able to use the free Dlink DDNS service in your router (it actually is a DynDNS service, but D-Link has an agreement with DynDNS to allow D-Link customers to still get a free DDNS account). Otherwise, if you need a "free" DDNS client, I suggest doing a Bing, Google, or Yahoo! search for "free DDNS".


Rebellious

join:2008-05-28

1 edit

Thank you, BellSouth server is back up.

I see Pure-FTP in Synaptic, the rest is too complicated for me. You could make a lot of money if you can package & market this (and it will help the Linux platform as well). There are millions that would prefer to host their own videos instead of using youtube, no need to upload, convert etc., also youtube has censorship, and why should youtube be selling advertisements on my videos. But then browsers are setup for Adobe Flash and not good at playing raw video formats. Just an idea

BTW, I use a Linksys WRT54GL Router but I have a spare D-Link DSL-2640B that I can piggyback, does that have Dlink DDNS service?



BellSouthPWP

@comcast.net

said by Rebellious:

Thank you, BellSouth server is back up...

BTW, I use a Linksys WRT54GL Router but I have a spare D-Link DSL-2640B that I can piggyback, does that have Dlink DDNS service?

I can't answer that question since I don't have a DSL-2640B available to look at the DDNS menu. The D-Link on-line emulator for that router does imply that it has a built-in DDNS client, but that part of the emulator does not work for me, so I don't know if it natively supports the dlinkddns.com account with DynDNS. It might possibly work even if it only has a generic DynDNS client if you go to »www.dlinkddns.com/ and setup an account (click the [New D-Link Users: Get started!] link), then manually enter the appropriate user and host name into the DSL-2640B's DDNS client setup.

Rebellious

join:2008-05-28

Thank you, I'm sure this will help many others reading the forum, for me it seems like too much work.

For the big picture, are you saying that namecheap is a free service that will emulate a static IP in any Linux box?



BellSouthPWP

@comcast.net

No, it is not entirely free. The DDNS service is provided at no additional charge to customers who use Namecheap as their domain registrar, and they do provide a FreeDNS service at no charge for those who use another domain registrar. You will have to either pay someone for a domain registration or find a free service (if such a service exists). FWIW, you can get a domain registered with Namecheap for ~10.00 per year (you can see the exact price for any TLD on their web site). You can probably find domain registrars that are even cheaper if you do a Bing, Google, or Yahoo! search for "domain registrar" (but not all domain registrars provide DDNS services, so simply registering a domain name is not always sufficient).


Rebellious

join:2008-05-28
reply to Rebellious

Same problem again: no FTP access to my home pages, intermittent login failure:

Status: Connecting to [2001:1890:1c01:2::40]:21...
Status: Connection attempt failed with "ENETUNREACH - Network unreachable".
Error: Could not connect to server

The server is not down however , pages are browse-able. So what's up?



BellSouthPWP

@comcast.net

said by Rebellious:

Same problem again: no FTP access to my home pages, intermittent login failure...

The server is not down however , pages are browse-able. So what's up?

At this point, the several pwp.att.net and home.bellsouth.net accounts that I still have are also unreachable via ftp (and have been that way all evening).

I suspect that the cause this time may have something to do with enabling IPv6 for those servers:
C:\>ping pwp.att.net
 
Pinging pwp.att.net [2001:1890:1c01:2::20] from
2601:5:c80:a9:e291:f5ff:fe95:beac with 32 bytes of data:
 
Reply from 2001:1890:1c01:2::20: time=34ms
Reply from 2001:1890:1c01:2::20: time=34ms
Reply from 2001:1890:1c01:2::20: time=34ms
Reply from 2001:1890:1c01:2::20: time=33ms
 
Ping statistics for 2001:1890:1c01:2::20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 34ms, Average = 33ms
 
C:\>ping -4 pwp.att.net
 
Pinging pwp.att.net [216.77.188.33] with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 216.77.188.33:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
C:\>ping home.bellsouth.net
 
Pinging www.att.net [2001:1890:1c01:2::40] from
2601:5:c80:a9:e291:f5ff:fe95:beac with 32 bytes of data:
 
Reply from 2001:1890:1c01:2::40: time=35ms
Reply from 2001:1890:1c01:2::40: time=56ms
Reply from 2001:1890:1c01:2::40: time=34ms
Reply from 2001:1890:1c01:2::40: time=34ms
 
Ping statistics for 2001:1890:1c01:2::40:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 56ms, Average = 39ms
 
C:\>ping -4 home.bellsouth.net
 
Pinging www.att.net [216.77.188.73] with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 216.77.188.73:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 

The AT&T PWP service has never been very reliable and it has always been given a low priority by AT&T when problems occurred. Now that new accounts are no longer being accepted, and only legacy accounts that met their announced usage requirements are still allowed, that unreliability factor is likely to get even more noticeable. I am surprised that AT&T has not simply shut that service down given that they have never been very enthusiastic about supporting it. I continue to use the PWP accounts that I have, but I certainly don't depend on them being available at any given time.


dtm0

join:2008-09-08

I have been unable to access my PWP for the last 2 days. I also can't ping home.bellsouth.net Is there a new trick to get the FTP server to work? Anyone else having a problem?



BellSouthPWP

@comcast.net

said by dtm0:

I have been unable to access my PWP for the last 2 days. I also can't ping home.bellsouth.net Is there a new trick to get the FTP server to work? Anyone else having a problem?

Both the pwp.att.net and home.bellsouth.net ftp servers are up and down like yo-yos lately. Currently, I also have no ftp access to those servers, nor a response to an IPv4 ping (but an IPv6 ping does work).

C:\>ftp home.bellsouth.net
> ftp: connect :Connection refused
ftp> quit
 
C:\>dig home.bellsouth.net
 
; > DiG 9.9.2 > home.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADERdig -taaaa home.bellsouth.net
 
; > DiG 9.9.2 > -taaaa home.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADERftp 216.77.188.73
> ftp: connect :Connection refused
ftp> quit
 
C:\>ftp 2001:1890:1c01:2::40
> ftp: connect :Connection refused
ftp> quit
 
C:\>ping 216.77.188.73
 
Pinging 216.77.188.73 with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 216.77.188.73:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
C:\>ping 2001:1890:1c01:2::40
 
Pinging 2001:1890:1c01:2::40 with 32 bytes of data:
 
Reply from 2001:1890:1c01:2::40: time=51ms
Reply from 2001:1890:1c01:2::40: time=34ms
Reply from 2001:1890:1c01:2::40: time=34ms
Reply from 2001:1890:1c01:2::40: time=35ms
 
Ping statistics for 2001:1890:1c01:2::40:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 51ms, Average = 38ms
 

The only "trick" is to be patient (or find an alternative public ftp server).


dtm0

join:2008-09-08

Thanks for the reply. Actually I want to redirect users to another host and shut the darn thing down but can't even upload the files. All I can say for AT&T on this is that it sure is a piss-poor way to run a railroad!



BellSouthPWP

@comcast.net

said by dtm0:

Thanks for the reply. Actually I want to redirect users to another host and shut the darn thing down but can't even upload the files. All I can say for AT&T on this is that it sure is a piss-poor way to run a railroad!

In the case of the PWP servers, AT&T officially shut down that service for new users over a year ago, and only kept it active for legacy users who had a history of actively uploading and downloading via ftp. I suspect that they are now not even interested in keeping it alive for the active legacy users (but it would be nice if they admitted that instead of just neglecting the site and letting it die).

FWIW, I can use a web browser and still access all of the files I have previously uploaded (http still works, only ftp is dead). If you setup your site's folders to be browseable, you may be able to access them with a web browser to retrieve them and copy them to another site.


dtm0

join:2008-09-08

Thanks. What I want to do is replace them with pages directing people to the new site.



tamasic1

@sbcglobal.net
reply to BellSouthPWP

I'm definately a legacy user and was able to upload several files on July 07, 2013. However the past few days I've not been able to attach. One thing I have noticed. If I put ftp.bellsouth.net into whois, I get a return of 205.251.137.82. When I put that into CoreFTP it actually attaches but says my password is incorrect. Previously the address showed as 216.77.188.73. When it was that, CoreFTP couldn't talk to the server.



BellSouthPWP

@comcast.net

said by tamasic1 :

I'm definately a legacy user and was able to upload several files on July 07, 2013. However the past few days I've not been able to attach. One thing I have noticed. If I put ftp.bellsouth.net into whois, I get a return of 205.251.137.82. When I put that into CoreFTP it actually attaches but says my password is incorrect. Previously the address showed as 216.77.188.73. When it was that, CoreFTP couldn't talk to the server.

The IPv4 address 205.251.137.82 does indeed belong to ftp.bellsouth.net. However, for accessing the BellSouth PWP server you should be using the hostname home.bellsouth.net which is assigned to the IPv4 address 216.77.188.73.

C:\>dig -ta home.bellsouth.net
 
; > DiG 9.9.2 > -ta home.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADERdig -ta ftp.bellsouth.net
 
; > DiG 9.9.2 > -ta ftp.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER- opcode: QUERY, status: NOERROR, id: 16846
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;ftp.bellsouth.net.             IN      A
 
;; ANSWER SECTION:
ftp.bellsouth.net.      10229   IN      CNAME   att.autocalendarupdate.net.
att.autocalendarupdate.net. 1229 IN     CNAME   lb-acu.com.
lb-acu.com.             60      IN      A       205.251.137.82
 
;; Query time: 140 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Sun Aug 25 13:31:54 2013
;; MSG SIZE  rcvd: 123
 

The hostname ftp.bellsouth.net is a totally different server and it is not associated in any way with the BellSouth PWP service. Based on the cname entry att.autocalendarupdate.net for ftp.bellsouth.net, my guess would be that it is used for automatic firmware updates in DSL modems.


BellSouthPWP

@comcast.net

I don't know what happened to the dns lookup information in my previous post. It looked ok when I previewed it, but it was garbled after it was posted. Since I have no way to edit the previous post, here is the same information again (hopefully it will display properly this time):

C:\>dig -ta home.bellsouth.net
 
; > DiG 9.9.2 > -ta home.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADERdig -ta ftp.bellsouth.net
 
; > DiG 9.9.2 > -ta ftp.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER- opcode: QUERY, status: NOERROR, id: 4913
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
 
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;ftp.bellsouth.net.             IN      A
 
;; ANSWER SECTION:
ftp.bellsouth.net.      1902    IN      CNAME   att.autocalendarupdate.net.
att.autocalendarupdate.net. 1332 IN     CNAME   lb-acu.com.
lb-acu.com.             60      IN      A       205.251.137.82
 
;; Query time: 80 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Sun Aug 25 15:50:42 2013
;; MSG SIZE  rcvd: 123
 
 


BellSouthPWP

@comcast.net

Nope, it still appears to be garbled after the actual post is made. Here is the information again, but this time done using different html code for the display:


C:\>dig -ta home.bellsouth.net

; <<>> DiG 9.9.2 <<>> -ta home.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4172
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;home.bellsouth.net. IN A

;; ANSWER SECTION:
home.bellsouth.net. 1726 IN CNAME www.att.net.
www.att.net. 38 IN A 216.77.188.73

;; Query time: 10 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Sun Aug 25 15:50:28 2013
;; MSG SIZE rcvd: 85

C:\>dig -ta ftp.bellsouth.net

; <<>> DiG 9.9.2 <<>> -ta ftp.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4913
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;ftp.bellsouth.net. IN A

;; ANSWER SECTION:
ftp.bellsouth.net. 1902 IN CNAME att.autocalendarupdate.net.
att.autocalendarupdate.net. 1332 IN CNAME lb-acu.com.
lb-acu.com. 60 IN A 205.251.137.82

;; Query time: 80 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Sun Aug 25 15:50:42 2013
;; MSG SIZE rcvd: 123


BellSouthPWP

@comcast.net
reply to dtm0

Well, perhaps there is some hope on the horizon that AT&T may get the PWP FTP servers operational again. I just tried accessing my pwp.att.net and home.bellsouth.net sites and now AT&T has made home.bellsouth.net a CNAME alias for pwp.att.net (it was previously a CNAME alias for www.att.net).




C:\>dig pwp.att.net

; <<>> DiG 9.9.2 <<>> pwp.att.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40231
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;pwp.att.net. IN A

;; ANSWER SECTION:
pwp.att.net. 463 IN A 216.77.188.33

;; Query time: 100 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Tue Aug 27 16:08:55 2013
;; MSG SIZE rcvd: 56

C:\>dig home.bellsouth.net

; <<>> DiG 9.9.2 <<>> home.bellsouth.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20322
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;home.bellsouth.net. IN A

;; ANSWER SECTION:
home.bellsouth.net. 8216 IN CNAME pwp.att.net.
pwp.att.net. 448 IN A 216.77.188.33

;; Query time: 100 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Tue Aug 27 16:09:10 2013
;; MSG SIZE rcvd: 85

C:\>ftp 219.77.188.33
> ftp: connect :Connection timed out
ftp> quit



FTP access still does not work, but at least this may be a sign that they are working on it instead of deliberately making it inaccessible.


BellSouthPWP

@comcast.net

Oops, my previous FTP access example did not work because I fat-fingered the IP address. However, even when it is done properly, it still does not work (but hopefully a fix is now possibly on the way).




C:\>ftp 216.77.188.33
> ftp: connect :Connection timed out
ftp> quit



tamasic1

@sbcglobal.net
reply to BellSouthPWP

home.bellsouth.net - although I get a couple error messages, it does now connect and I can upload via CoreFTP. Thank you so much with this, you are totally awesome in the help you give us!



BellSouthPWP

@comcast.net

said by tamasic1 :

home.bellsouth.net - although I get a couple error messages, it does now connect and I can upload via CoreFTP. Thank you so much with this, you are totally awesome in the help you give us!

I had nothing to do with it; AT&T just finally got the ftp service back on-line again:


C:\>ftp home.bellsouth.net
Connected to pwp.att.net.
220-Bellsouth Personal Pages FTP server v1.0 (12)
220-===================================================================
220- Welcome to Bellsouth Personal pages Ftp Service v1.0 (12)
220-===================================================================
220-No Anonymous connections. This is a private ftp server. Users who connect
220-more than 6 times within a minute will be blocked for 10 minutes. Any
220-unauthorised use will be prosecuted to the fullest extent of law.
220-===================================================================
220-
220-
220-===================================================================
220-Important Notice:
220-===================================================================
220-On or after September 12, 2012 the att.net Personal Web Page feature will be restricte d.
220-1.It will no longer be possible to create a new Personal Web Page.
220-2.Users with Personal Web Pages that have been actively managed or
220-viewed since March 10, 2012 will be able to continue updating their established pages.
220-3.Message Board features will no longer be available or functional.
220-4.Active users should bookmark the "Personal Web Page" management page for future refe rence and use.
220-5.Visit »www.att.com/esupport for additional information.
220 ======================================================================
User (pwp.att.net:(none)): myname@bellsouth.net
331 User name okay, need password.
Password:
230 User logged in, proceed.
ftp> dir
200 PORT Command successful.
150 Opening ASCII mode data connection for /bin/ls.
drw-rw-rw- 1 user group 0 Apr 25 10:31 .
drw-rw-rw- 1 user group 0 Apr 25 10:31 ..
drw-rw-rw- 1 user group 0 Nov 1 2009 FBI_eyes
-rw-rw-rw- 1 user group 3191 Apr 27 2011 TOSindex.html
drw-rw-rw- 1 user group 0 Nov 1 2010 alcatel
-rw-rw-rw- 1 user group 6158 Apr 27 2011 calvin-piss-att.jpg
drw-rw-rw- 1 user group 0 Oct 20 2012 digcon
drw-rw-rw- 1 user group 0 Apr 25 10:31 dlink
drw-rw-rw- 1 user group 0 Jan 22 2012 dslrbb
drw-rw-rw- 1 user group 0 Jan 22 2012 dslricons
drw-rw-rw- 1 user group 0 Mar 1 2009 faces
-rw-rw-rw- 1 user group 1078 Nov 14 1995 favicon.ico
drw-rw-rw- 1 user group 0 Jan 17 2012 image
drw-rw-rw- 1 user group 0 Oct 20 2012 images
-rw-rw-rw- 1 user group 4208 Sep 21 2011 index.html
drw-rw-rw- 1 user group 0 Nov 11 2010 motorola
drw-rw-rw- 1 user group 0 Oct 20 2012 nature
-rw-rw-rw- 1 user group 164 Jul 12 2011 robots.txt
drw-rw-rw- 1 user group 0 Oct 20 2012 rws
drw-rw-rw- 1 user group 0 Jul 17 2012 security
drw-rw-rw- 1 user group 0 Jan 17 2012 smiley
226-Maximum disk quota limited to 10240 Kbytes
Used disk quota 5200 Kbytes, available 5039 Kbytes
226 Transfer complete.
ftp: 1351 bytes received in 0.11Seconds 12.28Kbytes/sec.
ftp> quit
221 Thank you for using Bellsouth Ftp service.



trparky
Apple... YUM
Premium,MVM
join:2000-05-24
Cleveland, OH
kudos:2

For those that have web pages on this service, get something up there to direct people to a new location for your web page. Don't pass Go, don't collect $200, get something up to direct visitors to somewhere new now.
--
Tom
Tom's Tech Blog



dtm0

join:2008-09-08

I did get the redirect pages up!



sloe

join:2007-11-09
San Antonio, TX
Reviews:
·ooma
·AT&T U-Verse
reply to Rebellious

I just wanted to chime in with something - I recently set up a free DDNS account with freedns.afraid.org - the catch is if you're not registering your own domain, you have to piggyback off of one of the ones available there. I used the to.us domain for mine. My Buffalo router had the capability of keeping it updated, but the NVG589 doesn't have this feature that I can locate. I'm currently using a Windows client on my laptop to keep it updated until I get a more permanent solution in place.



dtm0

join:2008-09-08

Is this a spam message? It has zero relevancy to this topic.



sloe

join:2007-11-09
San Antonio, TX
Reviews:
·ooma
·AT&T U-Verse

No, it is not spam, and it has perfect relevancy to the topic.

Rebellious asked in the OP how hard it would be to set up his own FTP server. BellSouthPWP then addressed one of the issues with running your own FTP server at home, the dynamic IP address issued by just about every residential broadband ISP.

Conversation then proceeded regarding registering a domain name and setting up a dynamic DNS service to always point that name to the correct IP address.

What I was trying to disclose is that freedns.afraid.org provides this service for free using one of their domains, or another that was set up there and opened for use. You could pay them and they would gladly take your money to set up your own, non-piggybacked domain.