Seems like it initiated the download but failed due to proxy settings by chance? Seems like a bug that several U3 problems have been posted on this forum now.
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
Ok update, I am using port 80 and I've changed the Default Website on IIS to 81
I can scan all the hosts ok, it returns them as being all compliant. I'm using ESX Update 2 with VC Update 3
When vc.integrity runs it gets to 60% then fails, I can access the internet easily on the server, and the proxy test option passes.
Im at an absolute loss why I keep getting metadata download failed its driving me nuts on both Virtual Centers
Arghhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
During the installer I am pointing the prgram to an e drive and the patch repository to e drive also.
does the installer need to go on c: ? because I know its ok to have the patch repository on another drive as I am doing it elsewhere without issue
Hi Zippy, i am having the same issue. What exactly on your firewall was being blocked (which ports etc) to cause this problem ?
If you want to see what connection is having trouble getting established start the operation to download the updates at the same time goto the command line on the VC box and type in: netstat -an | find "SYN_SENT"
you can keep repeating the command this shows you what TCP connections the host is attempting to setup, if the connection stays in this state no reply is being received from the responder to setup the TCP connection. If you don't see this at all the problem may be DNS resolution. Also, sometimes firewalls will actually reset the connection if it's not allowed but most times the above will give you an idea of where the TCP traffic is going. Failing that you can always capture packets to see what traffic is not being allowed, look for a SYN packet being sent by the VC box and nothing or a RST being received.
There was a restriction placed by the firwall administrator on the size of downloads + ALL .zip file extensions had been blocked...