I have a virtual machine created from an linux image (and powered on). I want to be able to access its console in VCenter, but right now I am getting this error:
"A secure connection to the host could not be established"
The console is a black screen with nothing on it and no interaction. This happens for any VM in VSphere. Bizarrely I can telnet in to the console port 902, but there doesn't even appear to be any attempt to connect to the console (checking tcp/ip traffic in Task Manager).
SSHing in is not possible because the reason I wanted console access to begin with was to run commands to set up an IP address for this machine.
Some facts: Opening an external console window does nothing (same error). I'm running Windows XP Professional (out of VirtualBox if it matters). My colleague on the exact same setup (same version of XP, same version of VCenter) can connect to the console just fine.
Does this problem happen when you connect directly to the ESX/ESXi ?
if not you have connection problem beetween esx and vcenter.
you can find here a list of common ports :
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1012382&sliceId=1&docTypeID=DT_KB_1_1&dialogID=312218113&stateId=1%200%20312216906#vCenter 4.x
Turns out that when connecting to vcenter I needed to use https instead of http. Boy howdy, do I feel smart now.
Related
I have a server Google Cloud, it has been good working some years, but recently there was a problem, after restart server, I can not connect to its remote desktop, the prompt messagebox content is as follows:
Remote Desktop can’t connect to the remote computer for one of these reasons:
1.Remote access to the server is not enabled
2.The remote computer is turned off
3.The remote computer is not available on the network
But i check it is still on and has network connection, anybody help me?
update 1: I found the reason is port 3389 could not connect, but I tried the commands on command line still can't open port 3389
update 2: my team decided to destroy this server, close topic
I have successfully built the client and server modules from the Getting Started with Winsock tutorial.
I have a desktop and a laptop both connected to my wireless router – both running Windows 10.
Running the client module on the laptop, I am able to successfully transmit data back-and-forth to the desktop (running the server module) using the desktop's IP address.
Running the client module on the desktop with the laptop's IP address as the command line argument, I get an "Unable to connect to server!" message after a ten second delay.
If I try to run both modules on the desktop in separate console windows using the "localhost" command line argument, the client console displays "Bytes sent: 14" and hangs waiting for a response from the server – however this works if I use either the desktop name or the desktop IP address in place of "localhost".
I am able to run both modules on the laptop using either "localhost", the laptop name, or the laptop IP address as arguments.
I have gone through the same motions with port 27015 forwarded on the router and incoming and outgoing firewall exceptions added to both the desktop and the laptop – there is no difference either way.
Any assistance would be greatly appreciated as I cannot figure out why this works in one direction but not the other.
Thank you for the suggestions Karsten and Andriy. I first tried getting the two computers to ping each other and neither was successful. After researching online, I was able to get them to ping after turning on "echo requests" in the firewall settings, but my original problem persisted. I then tried turning off both firewalls and I was able to get my server and client programs to work both ways. That wasn't a great long-term solution, so I tried selectively disabling the firewalls and realized it was an issue on the laptop's end. I noticed that my "server.exe" program was in the allowed apps list twice – one instance granting private access and one granting public access – but only one instance was active. I deleted both and added "server.exe" again with both public and private access boxes checked, which solved my issue.
I red lot of post about this question without find the good answer. The situation is simple, I have a server (Go) running on Ubuntu 14.04 (VMware Workstation 12.1.0 Pro). It listens on the 8001/8002 ports. From the host of the VM (Windows 10), I can access it from the host (Windows 10) but from my Xamarin Application or the others computers, I can't access this server.
I tried lot of things such as port transfer, edit of the NAT propreties (of the VM) and edit of the vmnetnnat.conf file as well. I tested about bridge connection but I didn't find the way to make it works with this way. etc
I also did transfer port from my internet box to get the access by IP instead of private network address (192.168.XXX.XXX) but it didn't works too.
If anyone can help, thank !
By default your Workstation configures your VM in either NAT or Host-only or event in Custom network configuration what means your host computer (you Windows 10) is the only endpoint which can access this box without any additional configuration in your router.
I would suggest you the easiest way is to use "Bridge" configuration what you mentioned below by getting (perhaps DCHP) IP schema from your parent router (the one gives your Windows 10). Thus your VM will be available across your "Home network", Once done, check your ICMP (pings) from Windows 10 to your VM, make sure you can see it.
Second point is that your 8001/8002 ports might be closed by firewall (iptables) in your ubuntu / Windows 10. You probably want to check your both firewalls as your traffic is being routes by "Virtual router" of Workstation.
I want to know the difference between application started directly on the machine and the application started using remote desktop connection.
Whether both the application are same or will have different privileges.
For example, i had an opengl based application which take higher version of opengl 3 or 4 when started directly on the machine. But when i start the same application from remote desktop connection, it takes only base opengl version 1.1.
One more observation is:
We have a service application which will launch a graphics (OGRE based) application based on request. Request is set from client using web-socket communication.
When we start this service directly in a server, it works fine. But when this service is started from a RDP connection, the graphics application is crashing when user sends request after RDP connection is closed.
IT works if I keep the RDP connection on.
It may loose the graphics driver when you are logged in through RDP.
If you look in the launch the Ogre 'setup' dialog when RDP is enabled it will not list the graphics card - but a different 'RDP driver'.
Also - when you log on\off it might 'reset' the device (since the RDP graphics driver is enabled\disabled) causing your window get loose the device, and then crash.
One way to get around all this - is to use a VNC (for example tightvnc), this does not cause the issues that standard RDP does, since it does not use the RDP graphics drivers and such.
I'm running a client/server application locally on my Windows XP PC and for testing purposes I want to run multiple clients.
The server has a configuration file containing the IP addresses of the clients that can connect; in the real world, these would all be on separate hosts with separate IP addresses.
Currently I am able to test locally with a single client which binds to 127.0.0.1 however because I can only have one client-IP mapping in the server configuration (that's how the system works and can't be redesigned!) I can only run one client on my development PC.
I've tried to start another client application bound to 127.0.0.2 connecting to the server which is bound to 0.0.0.0 however the server thinks that the client is connecting from 127.0.0.1 again and so rejects what it believes is a second connection from the first client.
Can anyone suggest a way to get around this problem? I believe I could run one more client bound to the external IP address of the PC but I'd really like to be able to run multiple.
I know I could use VirtualBox or similar to run new instances but I'd like all of the client applications to be running in the Visual Studio debugger.
Any help greatly appreciated!
Nick.
PS. Not sure if it matters but the applications are written in C++ using standard winsock sockets.
You might be able to create more loopback interfaces. See the chosen answer to How do you create a virtual network interface on Windows?
AFAIK Windows 7 (maybe Vista too) lets you add multiple IP addresses to a single interface (card).