HOSTNAME problems after VZ update

[HoracioS]

I´m using Windows 2008 R2 datacenter (6.1.7601 Service Pack 1 Build 7601
) with Parallels Virtuozzo Containers 4.6.490.12

I was updated VZ with the last patch and now, all the containers with Plesk, experiencing the same FTP access problem withe Plesk 10.3.1 and 10.4.4:

Connected to xxx.xxxx.net.
220 Microsoft FTP Service
Name (xxx.xxxx.net:root): XXXXXXXXXX
331 Password required for XXXXXXXXXX.
Password:
530 User cannot log in, home directory inaccessible.
ftp: Login failed
ftp>

I tried all the solutions in KB and always has the same problem.
I can see the HOSTNAME is the HARDWARE NODE hostname, not the VPS hostname!!!!!
When check the IIS FTP binding address, the only option is the HARDWARE NODE IP address, not the VPS address.

Please help!

Best regards,
Horacio

[figjam]

Hi Horatio,

Did VZU460034 (http://kb.parallels.com/en/113820) fix the problem?

Cheers,


Andrew

[HoracioS]

No, it has not fixed the problem.

Only this article fixed the problem. I cannot believe Parallels not reply this thread before...
Support people don´t know about it yeat....

http://kb.parallels.com/en/113779

Container hostnames changed after installing hotfix KB2653956 to the Hardware Node
Article ID: 113779
Last Review: May, 3 2012
Views:
APPLIES TO:
Parallels Plesk Panel
Parallels Virtuozzo Containers
Symptoms
Note: The issue occurs only on Parallels Virtuozzo Containers, not on physical servers.

After installation of the Microsoft hotfix KB2653956, all containers' hostnames are changed to the hostname of the Hardware Node. As a result, the following issues occur:

- FTP stops working -- error "530 User cannot log in, home directory inaccessible."

- RDP stops working
Resolution
The issues will be fixed in a future update. You may subscribe to the Parallels Virtuozzo Containers Update mailing list if you wish to receive notifications about the latest product updates, new version announcements, and promotions for Enterprise applications of Parallels Virtuozzo Containers.

Workaround
1. Get the containers' original hostnames from configuration files (it is necessary to perform this command on the HW Node):
vzlist -Hao ctid,hostname > C:\hostnames.txt

2. Reset all containers' hostnames:
for /f "tokens=1,2" %i in (C:\hostnames.txt) do vzctl set %i --hostname %j --save

3. Restart all containers:

Note: This step will cause service downtime.

for /f %i in ('vzlist -Ho ctid') do vzctl restart %i