1 person found this helpful
Not too sure what is causing your specific issue however I was receiving NFC write timeout's a while back when trying to connect to Virtual Center however this turned out to be as a result of a database lock/stuck operation..
We had the DBA's clear the locks, then started the VI service and where able to log back in to Virtual Center.
Thought this may help in some way..
How are you trying to load the file's in to your datastore?
I ran into this recently and since I couldn't find anything online either I thought I would reply even though this is a bit old.
In my case my client does not sit on the same network as the ESX server. I found that in order to upload files using the Datastore Browser port 902 has to be opened between the client and the server. For me my sites' firewall between the networks was blocking port 902. Without port 902 being opened I would recieve the Failed to Log into NFC Server error message.
Hope that helps,
I received this error when i was trying to upload a large tar file (2Gb). While attempting to upload the file, it failed with an I/O error. I then attempted to upload it again and i received the "failed to log into nfc server". It looks like this error was generated as the file i was attempting to upload failed and must of been cached in some sort of memory so when i attempted to upload it again, there was a conflict.
Also....the reason my large file would not upload was with issues around the network connection (e.g network card set to 'auto negotiate'). Made this a fixed speed and works a treat now. No I/O error and no nfc error. Phew!
I have this problem. At first i thought it was an issue with the iSCSI datastore i added from FREENAS, but i've since tried to upload a vmdk to the primary ESX datastore and i'm getting the errors.
First error was an i/o error then unable to log into the NFS server after another try. I checked firewall ports and all relevant ports are open. I was able to upload a small file once, but that now does not work.
Has anyone cracked this mystery??
I've had this problem recently as well.
I was able to fix it in case, by making sure the service consoles default gateway was set correctly.
Hope this helps.
I had the same issue as Jimbo1011...
My workstation's NIC was set to Auto. Set it to 100full and the file uploaded to the datastore without issue. Way quicker than in the past too - for 600MB (Windows Server 2003 ISO), it took 1.5 minutes whereas before it would say 70 minutes remaining... and then fail.
I also encountered this problem. After verify that the VC Client and VC Server were on the same subnet (i.e. port 902 is not been blocked) and the NIC with fixed speed and duplex (i.e. not set to "auto-negotiate") I was still getting this error, even for a small file
So I tried running the VC Client connecting directly to the ESX server... and it works.
So I think this issue is with file been upload via the Virtual Center server.
I disconnected a host, then reconnected it again. All resource pools disappeared, all VMs are orphaned. When attempting to download any file from the datastore to the VI Client machine I get the "Failed to log into NFC server" message.
Port 902 is open, the VI client and Server are the same machine, the ESX host is on the same subnet, the operation proeviously worked on previous days.
I can recoved the VM by removing them for the inventory and addinig them again.
Any suggested to resolve the NFC issue?
Restarting VC service fixed this for me.
I initially had VC installed on XP. Things were working OK. I then moved VC to a W2003 system with the license server still on the XP system. I experienced the prblem on the W2003 system, everything else seemed to work OK.
I've gone back to VC on the XP system, and the problem has gone away. I don't know what the problem was, or why going back to the XP system fixed it. Perhaps it was a license issue.
I was experiencing this issue as well. I had open ports, so I knew that was not it. A restart of the VC server service did the trick for me.
Found that restarting the "VMware VirtualCenter Server " on the actual box i was running VC from fixed this issue.
The laptop I'm running VC client has 2 connections, one to the internal network that VC is on, and a connection to the "real" internet. I had to disable the NIC that has the real world IP address.
i had to login direct to the ESX server and upload it then, this solved the problem for me.