I have 2 Informix databases running in parallel in a network. One is the primary server database and another one is the secondary server database. I need to create 2 DSN in client systems. one DSN is pointing to Primary anotherone pointing to secondary.From the client node, while saving the second DSN Automatically first DSN IP is changing into second DSN IP. So not able to connect two server at the same time.
Please help me to solve this issue...
Related
I've configured MariaDB to allow my LAN to access my Maria DB via IP addresses (e.g. 192.168.1.%). However, when my apps make a call to the db from a remote machine, I'm getting rejected because Maria is getting the requesting machine's DNS name (e.g. foo.attlocal.net), NOT its IP address. So, I added that DNS name as well. Now, when I access Maria from the same machine the DB is running on, Maria is getting the DNS name foo (without the attlocal.net). How can I stop playing wack a mole with all the DNS name combinations and just deal with IP addresses?
You need to turn on system variable skip_name_resolve.
Since it can't be changed after server start, you need to set the value either in your configuration file or pass the parameter to mysqld in start script.
I have an Oracle Database 11g data on my local PC.
Now I want to import this data to Oracle VirtualBox machine where I also have Oracle Database 11g.
Can somebody suggest me the procedure how can I do it?
I have my solution for my problem. In the virtual box, when I create a new connection in oracle database, I place my local IP address instead of localhost, username and password as it is in my local PC. And it works !
I am Connected to our VPN and I would like to RDP to a Server that is on the network that is currently connected to a different VPN. What do we need to do? If I RDP to a different server and then RDP from that server to the one connected to a different VPN, it works. I just can't directly. Is there something that we need to set up on that server, my computer or the network?
Actually you can be connected to other remote server as well with your machine as VPN client so now will be vpn client to two different vpn server
for doing this you need to perform following steps
1.Create a new client1.conf file for the new remote server
2.copy the content of already present client.conf to client1.conf file
3.now change the value of ca, cert and keys in client1.conf file to the respective values as per to those needed to connect other remote server
4.establish vpn connection with other remote server as follows
openvpn client1.conf
The command used above are for linux to establish vpn using openvpn, For windows, please find same command for windows from openvpn site might be client1.conf in linux corresponds to client1.opvf or something... However this would be the step to be performed in general
I have three systems, Sql Server Express only on one. I would access sql server on main pc from the other two to enter data into a database using a winform application. all three pcs are on LAN. what do i have to do establish connection with sql server on the main pc from the other two pcs? That is, how do i network my sql server express so that it is installed only on one machine but used by two other machines also. What protocols would i have to turn on or off?
All 3 pcs are in a same room. Also, sql remote connection means connecting via internet?
I'm trying to connect from my ms windows 7 via the odbc administrator to a remote
sybase sqlanywhere 11 database server.
But I get not connection, I'm not sure which configure option I have to specify.
server-name = ip address of remote database server?
startline ?
portnummer ?
Thank you, best regards, Alex
By default the SQL Anywhere server process dbsrv#.exe listens for incoming connections on port 2638.
Make sure your firewall allows outbound connections to that port.
Assuming you have a database running on your server as follows:
-x tcpip
-n my_server_name
"[DIR]\database_main_file.db" -n my_database_name
The server will broadcast on the tcp/ip layer on the default port (2638) under the name "my_server_name" and the database will be accessible under the name "my_database_name" via ODBC
Creating an ODBC entry for your new database to connect from a client (adjust for Windows 7)
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\myodbcentry]
"Driver"="C:\\PROGRA~1\\SQLANY~1\\Bin32\\dbodbc11.dll"
"DatabaseName"="my_database_name"
"ServerName"="my_server_name"
"LINKS"="TCPIP(IP=SERVER_IP_ADDRESS;PORT=2638)"
There are other parameters available for LINKS (HOST, etc). Take a look at http://dcx.sybase.com/index.html#1101en/dbadmin_en11/da-using-tcpip.html
I've seen some rare issues with UDP broadcast packets. See the docs at
http://dcx.sybase.com/1101en/dbadmin_en11/broadcastlistener-connection-conparm.html and check with your network administrator.
You can also use the dbping.exe utility to troubleshoot networking issues.
BTW, you may want to cross-post your question at http://sqla.stackexchange.com. It's full of SQL Anywhere buffs