An Unexplained Error Occurred Vmware
Contents |
on host--work aroundSo, the situation: Last night I was called by our head practice manager preparing for a sales demo today; he was in a panic (well, he was calm and collective, I was paniced)--the virtual machine we created for his demo was broken.Everything a general system error occurred vmware had started ok: he got the virtual image started on his laptop, and was able a general system error occurred vmware converter to get to the console. But then... he closed his laptop cover with the VM running, and then when he opened it back a disk read error occurred vmware up, he started getting this message when opening the VMWare console:Error opening the remote {machine name}:8333\16: An unexplained error occurred.A couple reboots later, he called me. We went through all sorts of troubleshooting, even created a new virtual,
Error An Ssl Error Occurred Vmware View
with no success--until I asked if he had Internet connectivity. Turns out the laptop coming out of hibernation did not automatically connect to the wifi network, or there were additional steps at the hotel, but regardless, he didn't. A few Google searches turned up this life saver: http://amritbera.blogspot.com/2009/03/vmware-remote-console-unexplained-error.htmlSo, I had him powered off the non-functional machine, got his wifi going, opened a browser, and verified his Internet connectivity. And then, he powered up the machine again, and, viola, it worked.The issue is that the VMWare Ethernet adapter must have a DNS entry or it gets all hosed up. So, answer is vmnet1 network adapter (an adapter that is installed automatically when VMWare installed) needs to have it's DNS entry configured to be the same as it's IP address to work when Internet connectivity is unavailable.Since I didn't think any of our sales team would know what the heck that meant, I wrote up some instructions with screenshots to make these adjustments on a Windows 7 host:Workaround for "Unexpected Error" when starting VMWare console and NOT connected to a network: Go to Control Panel / Network and Sharing :Click on Manage network connections- You may have to change to detail view and expand the device name so you can see the whole name:- Right click on the one that is VMWare Virtual Ethernet Adapter for VMnet1- Select Properties- Click Internet Protocol Version 4 (TCP/IPv4) and select PropertiesLeave the top part alone, but under DNS server addresses, enterCopy whatever is in IP Address to the Preferred DNS server:In my case, I am copying 192.168.207.1, but this may be different for you.That should do it, and is sufficient to solve the problem for all virtual machines running on the host. Thanks to Amrit Bera for the solution!! Posted by Derek Sanderson at 10:39 AM Em
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “An unexplained error ocurred” when connecting on ISO cd up vote 0 down vote favorite While using http://dereksan.blogspot.com/2010/06/vmware-unexplained-error-when-opening.html vSphere vCenter client, I try to connect to a local or network ISO cd and I get "an unexplained error ocurred". If I connect directly to the ESXi host I can use the ISO image. So the problem is related on vCenter. Any ideas? vcenter share|improve this question edited Jul 6 at 11:06 Hennes 50.7k775120 asked Mar 2 '10 at 14:16 jorgitogutier add a comment| 1 Answer 1 active oldest votes up vote 1 down vote make sure the host http://superuser.com/questions/115308/an-unexplained-error-ocurred-when-connecting-on-iso-cd has a DNS defined I set the DNS entry in the network device configuration to 127.0.0.1 and it helped share|improve this answer answered Jan 17 '11 at 12:03 springcomet 111 add a comment| You must log in to answer this question. asked 6 years ago viewed 201 times active 2 months ago Related 1Creation of Virtual Machine fails using 'VMWare vCenter Convertor Standalone'0Accessing vCenter Server from Internet (remote network)0Creating Linked Clones in vSphere/vCenter w/ PowerCLI1Virtual SAN not recognizing any disks1VMWare vCenter Solutions and Applications Icon Missing - Update Manager0ESXi + VCenter 5.1 Refresh Networks Hot Network Questions Did Morpheus not know Agent Smith before the bathroom fight? Dungeons in a 3d space game Why does a "parent" generate a "sister"? So sayeth the Shepherd Can you make rainbow dye in Terraria? Do you use the plural "-j" when the quantity is zero ("nul"/0)? Does the verb 'to busy' require a reflexive pronoun? What is going on grammatically with "Xを嫌いになる"? When to summon Uber: travel from Opera to CDG How does Coruscant get food? What's the right way to pronounce "why"? Scientific Notation Question What is induction-induction? \makeindex's "title" option from imakeidx ignored if tcolorbox' indexation is used Does mean=mode imply a symmetric distribution? Coin cell regulation required? What is a dormant black hole? Now I know my ABCs, won't you come and golf with me? How do cheap phone chargers charge li-ion batteries? How to pluralize "Stat
Remote Console Error opening the remote virtual machine localhost:8333\80: An unexplained error occured. ネットワークに接続していない環境で起きる場合があるようです。 プレゼンの際にあたふたしなくもいいように対処方法を覚えておきましょう。 ホスト側の VMnet1 の DNS サーバーの IP アドレスを自分に設定するとよいらしいです。 http://pooh.gr.jp/?p=6121 スタート > コントロールパネル > ネットワーク接続 > VMware Network Adapter http://blog.pcfreak.de/2010/08/31/vmware-remote-console-does-not-open-an-unexplained-error-occured/ VMnet1 を選択 > ファイル (または右クリック) > プロパティ > インターネットプロトコル (TCP/IP) > プロパティ > 次の DNS サーバーのアドレスを使う の 優先 DNS サーバー の値に 次の IP アドレスを使う の IP アドレス の同じ値を入力 This entry was posted in Windows. Bookmark the permalink. error occurred Post navigation ← FBI が捜査にスパイウェアを活用 (;´Д`)スバラスィ …ハァハァ Oracle が Sun を買収 ( ゚∀℃( `Д´)マヂデスカ!? → Search for: Categories Linux (171) Mac (27) Pooh (24) Unix (46) Windows (85) ニュース (2,265) Archives Archives Select Month March 2015 (3) January 2015 (8) April 2014 (2) March 2014 (2) February 2014 error occurred vmware (1) January 2014 (11) October 2013 (1) January 2013 (1) October 2012 (1) August 2012 (3) July 2012 (3) June 2012 (1) May 2012 (12) April 2012 (15) September 2011 (4) August 2011 (44) July 2011 (32) June 2011 (36) May 2011 (37) April 2011 (34) March 2011 (31) February 2011 (29) January 2011 (32) December 2010 (42) November 2010 (30) October 2010 (34) September 2010 (31) August 2010 (33) July 2010 (33) June 2010 (39) May 2010 (34) April 2010 (34) March 2010 (35) February 2010 (29) January 2010 (34) December 2009 (38) November 2009 (38) October 2009 (20) September 2009 (10) August 2009 (1) July 2009 (27) June 2009 (30) May 2009 (33) April 2009 (31) March 2009 (31) February 2009 (28) January 2009 (32) December 2008 (36) November 2008 (32) October 2008 (32)
Internet iPad iPAQ iPhone iPod IPv6 KDE Kubuntu Links Linux Mac Malware Microsoft Monitoring OpenVMS PRISM Privacy Security Smartphone Software TopApp Twitter Überwachung Ubuntu Uncategorized Virtualisierung Windows Meta Anmelden Beitrags-Feed (RSS) Kommentare als RSS WordPress.org VMware Remote Console does not open - An unexplained error occured Posted August 31, 2010 Comments(1) [Click here for english version]. Heute hatte ich eine interessante Fehlermeldung beim Öffnen einer VMware Remote Console über die VMware Infrastructure Web Access Homepage. Immer wenn ich versucht habe die Remote Console zu öffnen, erhielt ich folgende Fehlermeldung: Error opening the remote virtual machine 192.168.178.253:8333\16: An unexplained error occured. Zunächst wurde vermutet, dass es am Betriebssystem (Server 2008 R2), den Sicherheitseinstellungen des Internet Explorers (Enhanced Security Configuration on) bzw. an der Installation des „VMware Remote Console Plugins" liegt - Fehlanzeige. Ich mache es kurz, das Problem tritt immer dann auf, wenn auf dem Rechner, auf dem man den Browser und somit auch das „VMware Remote Console Plugin" startet keine DNS-Server in den TCP/IP-Einstellungen konfiguriert ist (z.B. bei einem Testsystem). Also DNS-Server eintragen (zur Not geht auch 127.0.0.1) und schon klappt das Öffnen der Remote Console problemlos. 1 Comment so far Tasko on Juni 23rd, 2011 ROTFL Danke für's Ersparen weiterer Experimente…:-) Posting your comment. Leave a Reply name (required) email ( will not be shown ) (required) website CAPTCHA Code* Theme by easternwest and Stephen Reinhardt