Problem with FTP ?

[#1]

Thanks Paul and Chris!

[#2]

We are PlusNet broadband users who have not been able to use ftp at all for the last few weeks, until we just found about using "ftp2.plus.net" instead of "ftp.plus.net".
We are happy to use this as a temporary workaround, but we are greatly concerned that whatever has affected the "ftp.plus.net" server may also affected the "ftp2.plus.net" servers at some point.
Could we therefore please ask the PlusNet team whether any progress has been made with this fault ?
We have experimented with four client ftp methods...
1 - FTP from the DOS command line - "ftp ftp2.plus.net" and "ftp ftp.plus.net"
2 - FTP from DreamWeaver
3 - FTP from Internet Explorer - "ftp://ftp2.plus.net/htdocs/" and "ftp://ftp.plus.net/htdocs/"
4 - FTP from Globalscape's CuteFTP
We have found that all of these methods connect successfully to the "ftp2" server, but they all fail to connect to the "ftp" server, even on the PC that is connected to the PlusNet Broadband Router. We also tried it on a selection of other PCs, and strangely a small subset of them work successfully when connected to either "ftp" pr "ftp2" - even though these PCs are not on PlusNet Broadband.
However, the vast majority of the PCs fail with "ftp" but work with "ftp2".
It is all very worrying, and suggests that something subtle changed on the "ftp" server one weekend a few weeks ago.
When we do an nslookup on these servers, we get...
ftp.plus.net - 212.159.9.131
compared to their second ftp server…
ftp2.plus.net - 84.92.0.98, 84.92.0.97    - (Two servers)
Any reason why they appear to be on an entirely different network ?
If the PlusNet team are still having difficulty reproducing this ftp problem, we can volunteer as guinea pigs.
We have a broadband router with a PC directly connected to it at our Liverpool home.
The failure on this machine is absolutely solid.
Also, could you please give us all the ticket numbers for the open incindent(s) or job(s) for this ?
Thanks,
Rod Wilson and Shaun Wilson (Username rlwilson409)

[#3]

Quote

Could we therefore please ask the PlusNet team whether any progress has been made with this fault ?

Yes, we've investigated a number of reasons for this, from looking at the config of the servers themselves, through to the loadbalancers and the individual account profiles of those people affected. It's still being looked at and I'm intending to get a service status update out this pm.

Quote

It is all very worrying, and suggests that something subtle changed on the "ftp" server one weekend a few weeks ago.

We have a system which captures all changes made to live systems and servers and no reference can be found in them to the ftp servers.

Quote

If the PlusNet team are still having difficulty reproducing this ftp problem, we can volunteer as guinea pigs.

Thanks for the offer, we've actually been able to reproduce this here though.

Quote

Also, could you please give us all the ticket numbers for the open incindent(s) or job(s) for this ?

Not quite sure what you mean by this? Our internal problem ID is 50115.

[#4]

According to the latest service status this has now been fixed as a rsult of the latest load balancer maintenance. Can people try with ftp.<vISP>.net and report back.
FTP timeouts (50115) - RESOLVED

[#5]

Not working last night - now OK

[#6]

Working OK now
David