I am trying to connect XenCenter 6.0 to Server installed with XENSERVER 6.0 but i can't connect.
It give me error when i try to connect :
"Unable to connect to server '192.xxx.xxx.xxx'.
The connection was refused.
Check that Xenserver is configured correctly on '192.xxx.xxx.xxx'."
Also When i was using another computer for connecting xencenter, It was disconnecting automatically every time i connect
Examine some details:
List item
the server is power-on
the network configuration is right.(try to use "ping" or "ssh" to check)
the firewall setting
duplicate IP address which has been used
There are two possible scenarios in this case .
Either
1. The xenserver physical machine is powered off.
Or
2. The network cable is not connected properly.
If the server is pingable, make sure xapi and xapi-ssl are running.
ssh to the xen server and check the following:
/etc/init.d/xapi status
/etc/init.d/xapi-ssl status
If they are not running restart them
/etc/init.d/xapi start
/etc/init.d/xapi-ssl start
might require a xe-toolstack-restart
Related
I've installed vinagre on my system and setup necessary settings on my server that I want to connect I've move my server and now when I want to connect I see this error(connection closed)!
I check and understood vnc connection is not on my server anymore! I don't know what happen exactly but I've active vnc on my server but still have problem for connecting. (I used these steps
Do you know any help or resource for solving this problem?
Both of my systems are Linux
I did a fresh installation of curity 7.1.0 on a Linux VM. it installed without any issue and started fine. However I am not able to connect it using admin console.
error:
Secure Connection Failed
An error occurred during a connection to xx.xx.xx.xx:6749. PR_CONNECT_RESET_ERROR
A RESET_ERROR often indicates a problem with the infrastructure in my experience.
You can try the following
Clear the cache of your browser
Test with a different browser
Check network settings, i.e. firewall, VPN, proxies, port openings...
I am entering the ip of the machine I wanted to connect using vnc viewer but it's giving me this error:
So, that error means
No response was received from the specified IP address, even to reject
the connection.
Ways to fix this:
Check the remote computer is switched on. Ensure antivirus software lists VNC Server as an exception, and the firewall is configured to allow access on VNC Server’s listening port (5900 by default).
See if you are attempting to establish a direct connection over the Internet.
You can check any vnc error message from https://help.realvnc.com/hc/en-us/articles/360002254738-VNC-Connect-Error-Messages
I have a physical Window Server 2008 R2 machine running SQLBase 8.5 and I have no problem connecting to it. Recently I migrated this server to a virtual machine and the problem come up. Sometimes I am able to connect to the Server and sometimes not.
I can pin my Virtual Server but not able to connect to it through SQLTalk or any client application.
Is anyone having the same issue running SQLBase 8.5 on a Virtual Machine?
Thanks!
Check how many users connect at a time. SQLBase 8.5 have some limitation when maximum number of users/cilents exceedes.
Try to find whether the issue occurs when a large query is executed. If so then try to simplify it.
Check for blocking issues. Try to test its working when disabling Internet security applications\antivirus\Firewall for some time.
Check for port issues. Check the 'listenport' value of sql.ini file.
Check for SQLBaseConnection properties and cross check the parmeters like 'connection lifetime'.
SQLBase 8.5 was only ever certified up to Windows Server 2003, and is so old I'm amazed it runs at all. You should be running at least SQLBase v12 if you're on Window Server 2008.
Here is a compatibility matrix: SQLBase compatibility v6 to v12.2
So assuming your SQLBase instance is actually up and running at the time you can't connect, check the CLIENT side sql.ini , there will be an ip address e.g. .
On the CLIENT at command prompt, run: ping -t (ipaddressofserver in CLIENT sql.ini)
I have WAS MQ 7.1 Server installed in windows. My application running on unix is trying to connect to this server during which it gives the error "MQ Connect failed 2195" in the application logs. On debugging the code , i found it is while connecting to the q manager that it is throwing this error.
I tried to run a netstat on the MQ Server port no. and do a telnet to check if there is any connection being established . But I could not see any connection being established to the q manager .
The possible issues could be
1. Que Manager has not been started
2. Listener not started
3. Initiation queue not started or created or attached(usually optional depending on set up)
4. Listening to the wrong Port or IP
5. Firewall stopping traffic to Port or IP
6. Queue Manager not created on destination
7. Not authorized to Queue manager and/or channel and/or queue
8. Trial MQ copy expired.
9. Wrong Queue manager name
10. Wrong channel name or password or queue or queue type
Have done the following to check if it is working fine .
1. Tried to put a message from windows to the MQ Server which was successful.
2. Gave auth(setmqaut) permission to Request queue that was created.
3. There is no firewall between application and MQ Server.
4. Channel name , q manager , IP and port no.s are correct.
In my windows MQ Setup i have created the Server connection channel and Client connection Channel.
export the mqm lib to SHLIB_PATH.
Added the application user to mqm group and also the windows user through which I had created the MQ Server setup
Had copied the AMQCLCHL.TAB to the unix machine containing the client program.
exported MQCHLTAB to the table filename
exported MQCHLLIB to the path containing the table name
exported the MQSERVER=QMgrName/CHANNEL1/hostname from the client machine.
Please let me know if I am missing anything w.r.t connection of the application(in Unix) to the MQ Server(in Windows).
2195 is MQRC_UNEXPECTED_ERROR. It implies something that should not have happened, even if you set it up wrong. It may well be accompanied with an FDC file in the errors directory. You should raise a PMR with IBM Service.