Connecting SQLBase Server running on Virual Machine - sqlbase

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)

Related

remote desktop vinagre and vnc connection

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

Newbe problems and first steps

I just start with MongoDB.
I have installed it on Win Server 2008 R2 and hosted it in a win Service, worked.
I tried to connect from a Client using an app, but can't connect.
I checked the Connection string twice, correct (isn't that hard) and I stopped the Firewalls on both machines, nothing helped. The machines were part of a private Network, no Routers in between.
I also used mongo Shell (mongo.exe) on the Server, and I was able to connect.
So, it must be some issue with the Client machine or the Network.

Browser can't access MongoDB on 27017

I have some issues with MongoDB (or Linux security, perhaps):
1 I am runing MongoDB 3.0 in an OpenSuSE 13.1 machine (which acts as the data server). I have a local network of 4 computers with different OSs.
2 I can connect from a Windows 8.1 Laptop using the mongo command, using the pymongo Python library, or Robomongo. Everything works just fine: I can query the server and insert things.
3 However, when I try to access port 27017 to see the "It looks like you're accessing..." message, the browser says "The connection was reset".
4 SuSe's Firewall and AppArmor are disabled.
QUESTION: There is one computer that can't access the address of the local server. Said computer is in the same local network and is running Windows 8.1. I tried with many other devices and OSs (see miniupdate in comments) and they all managed to access the 27017 port on the server. Of course, the server simply displayed the message "It looks like you are trying to access MongoDB over HTTP on the native driver port.". Do you have any ideas as to why the browser in the problematic computer keeps saying "Connection was reset" instead of showing the message mentioned above? Please note that this computer can do everything I mentioned in point 2. It's the browser thing that is puzzling me.
MongoDB's default port doesn't speak the http protocol. Which is what a browser can speak (among a few others). If you're looking for the web based status page, then that should be on port 28017 (27017 + 1000).
See http://docs.mongodb.org/manual/reference/default-mongodb-port/ for more details.
Found the solution on my own: disable the "Web shield" of Avast Antivirus. It somehow resets the browser's connection to Mongo.
Again, I realize that Mongo doesn't talk HTTP on that port, but still the fact that all other devices but this one were able to connect (to simply get a message) was bugging me.

How can i know if someone in the network connected to the SQL Express 2008 on my system

I have installed a SQL Express 2008 Server on my Desktop for some local work. This has mixed authentication. I have enabled TCP/IP connection so that one colleague can connect to this server. However, this exposes the server to everyone in the network. How do i keep track of which PC in the network connected to this server and when ? This would just help me audit the usage of the server.
Well you can get information about current users, sessions, and processes in an instance by using
sp_who;
MSDN Documentation

Can't connects XenCenter with XenServer

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