dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
5
share rss forum feed


BellSouthPWP

@comcast.net
reply to dtm0

Re: BellSouth FTP server down

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!