Knowledge base
I could not get an access to the server. How to detect the problem?
Posted by Pomoc Oktawave on 17.05.2014 21:18

Internet connection verification

In case of the problems with connection to the OCI instance it is strongly recommended to verify a transmission quality from another location. The aim of this is to determine, if the problem did not result from a network provider failure or if a current IP address was not blocked by a firewall. There is also a need to check, if mtr tool displays loss of the packets.
In case the connection is established form a company network, be aware that local settings could limit RDP connection (3389 port).

Operating system verification (Linux)

It could be also needed to determine, if there is any information regarding the problem in the instance logs. Server logs could be found here:

/var/log/syslog

and kernel logs here:

/var/log/kern.log

User should also make sure if a local firewall rules does not obstruct the traffic. To determine this you should log into the instance. In order to do it, try to establish a connection with the firewall switched out. You could do it using a following command:

/etc/init.d/firewall stop

Restart would follow after typing the command:

/etc/init.d/firewall start

Please keep in mind that the commands listed above results in enabling previously blocked IP addresses.

It is recommended to add to the whitelist IP addresses that are often used to establish a connection. The whitelist could be find as shown below:

/etc/init.d/firewall

This step would prevent repeating of the obstructions in the future.

Please also notice that a firewall is our own-developed tool so adjusting it to your specific needs is strongly recommended. A configuration could be accessed as below:

  • Linux (without CentOS): /etc/init.d/firewall,
  • CentOS: /etc/sysconfig/iptables i /etc/sysconfig/ip6tables, firewall deactivation: iptables -F,
  • FreeBSD: /etc/pf.conf.

Remote desktop connection verification (Windows)

During RDP connection the problem may result both from a firewall settings on the server (you should verify this from the operating system), or a connection settings on the local PC.

 

 

It could be also helpful to check the suggestion regarding terminal service:

http://www.siteventures.com/blog/item/windows-2008-r2-remote-desktop-services-keep-alive-configuration

In order to run it, you should perform in Windows Run | gpedit.msc, and complete all the steps mentioned in the article till an option keep alive would be set.

Remote console connection verification

In this case, apart from checking local environment (firewall, Java plugins), in some circumstances terminating a current connection and establishing a new one in Oktawave administration panel is needed.

 

(0 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below. This is required to prevent automated registrations and form submissions.