I am trying to connect to a jprofiler server running on linux 64 machile, from windows xp,
It connects for the first client, but when I try to connect from another windows client to that server it just keeps trying to connect , but never succeeds.
please let me know how I can enable the jprofiler sever allow multiple client connections.
Unfortunately, that is not possible. The profiling agent in JProfiler only works in a one-to-one connection mode.
Related
Trying to setup an ODBC connection for UPS to access our SQL server, from our shipping client computer.
I have scoured as much as I can an ran across:
runas /netonly /user:domain\account "c:\windows\system32\odbcad32.exe"
Now, using this method, on my current client computer, I was able to setup an odbc connection successfully using SQL Native Client 11 (5058). I am using Win 10. Our shipping computer, with multiple manifest systems on it, is still using Win 7, but otherwise is setup the same on the domain.
Using the same process as above, the connection ultimately times out, and states that the server is not online/not available/not allowing remote connections.
Is there a step I'm missing? Both clients have same rules for firewall, both are using the same user/password in the runas cmd. The only difference between the two clients is Win 10 vs. Win 7, and the current logged in user is different (but that shouldn't matter with the runas cmd?)
Thanks!
So after several days/hours of trying various solutions and suggestions from all over the interwebs, I came across this solution/tips.
In SQL Server Configuration, checking the network configuration protocols/clients/aliases. In my case, there was an aliases established for 32-bit, and not 64-bit. I disabled the 32-bit one.
I then found suggestions to us the ip (which I had tried in the past, with no success), but this time, after ensuring all the tcp/ip protocols were enabled and the 32-bit aliases was disabled, I was able to connect the 32-bit to the 64-bit SQL server, using the xxx.xxx.xxx.xxx address of the server.
Test came back successful!
After upgrading a Windows 10, cannot connect to any remote db in this case using SSMS
I have installed TMG client and the port are open, other developers with Windows 7 can connect to the database, this only happens to the developers that have Windows 10
Any idea about this issue?
From my googling, a common theme for this is that when the connection to the remote database is in the format {Server Name}\{Instance Name}, Windows 10 throws a fit and won't allow the connection.
Instead, try {Server IP Address}\{Instance Name}.
i've just bought a DELL PowerEdge T110 II with Microsoft Windows Small Business Server 2011.
I've installed PostgreSQL (latest version 9.1) and i've made the pg_hba configuration for access the DB from other LAN PC.
Here is my problem, if i try to connect to PGServer with PGAdmin from LAN PC quickly after the bootup of the server i can connect without problems.
After few minutes (2-3) i cannot connect anymore to the PGServer. If i connect to the server with PGAdmin local there is no problem and only after that i can successfully connect to the PGServer w/o problems.
Another solution is to remove the LAN Cable from the server and plug-in again. In this way the PGAdmin from other LAN PC gets back to work.
Here the message i get
Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "192.168.4.10" and accepting TCP/IP connections on port 5432?
Is some sort of standby of the Postgres process?
(I know my english is not wonderful, if you don't understand something, ask and i'll explain better)
Edit: The same thing happens with remote desktop so this does not seem to be a PostgreSQL issue.
Hello all I have a backed up about 30 servers using disk2vhd and now I have built my first of many hyper-v severs I did not realize this is all command line I did download CoreConfigurator and that does have some functionality I have been looking for. My question is how do I get the VHD files to run a Vitual Machines? its all command line I tried via vbs to mount the VHD's and I have not been able to any help on this would be great!
Thanks!
If you are using servercore, You maybe can do everything from the command line but I always prefer to have one computer running a Non server core version of windows 2008 to be the management server. You will load up Hyper-V manager on the non server core box and manage your Hyper-V server.
To have no "management" servers or desktops on your network will be a big pain IMO for management.
Using Hyper-V Manager you can quickly load the VHD's as VM's.
So load up Hyper-V Manager on a desktop PC on your localnet, and use its connect option to connect to your servercore. (Make sure your firewall settings are ok on servercore using coreconfig)
I have VS 2008 and SQL Server 2005 Developer edition installed on my desktop. I have a instance of XP running in Virtual PC and want to connect to the dev instance. I am logged on as a domain user on both the desktop and the Virtual instance of XP. When I try to connect I get a message saying "Server does not exist or access denied". What do I need to do to connect. I am using trusted connection and the userid has privileges on the DB.
Paul
Make sure that the VPC is not using NAT for its network connection.
Also check your configuration to be sure remote connections are allowed. Remote connection is turned off by default.
Have you tried pinging your desktop from the virtual instance? I had the same problem and figured out that the firewall was preventing any kind of communication between both machines.
I found out that you have to go into the SQL Server Surface Area Configuration tool and set "Remote Connections" to "Local and remote connections". Apparently the default is "Local connections only".
I encountered the same thing, sort of - MS Server 2003 and SQLServer 2008 Ent running on VMWare, and get the "Server does not exist or access denied" when trying to connect from host machine (on Vista x64).
SO, do you reckon changing to "Local and remote connections" via the SQL Server Surface Area Configuration tool will do the trick?
For me despite configuring the SQL server for Remote Connections also, I could not access the sql server from Win XP VM.
So when I disabled the windows firewall from host machine, it worked fine!!