DELL PowerEdge T110 - Unable to connect to Postgres Server - windows-server-2008

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.

Related

Connecting Oracle guest on VirtualBox to a macOS Host

I use oracle DB Developer on VirtualBox to create databases using SQLDeveloper. I use VirtualBox since I can't download SQL Developer on MacBook. I'm writing a Java code on eclipse with an SQL connection on the host machine. How can I connect establish a connection between the guest machine and the host machine?
I've tried to do the port forward option through VB's network adapter setting. When I tried localhost:8000, the page wasn't accessible. I'm honestly not sure if this is even a valid solution for my problem.
Anyone has a suggestion on how to connect my host machine to the database on the guest machine?

Linux SQL server windows SSMS connection

I have a Red HAT system on oracle virtual box that I've been trying to set a mssql server up.
-Also tried doing everything on SUSE vm but I've been probably doing the same thing wrong on that one aswell.-
I have the server up but was unable to connect the mssql server in linux from windows terminal or SSMS.
Get this as a terminal response on windows
ODBC Driver 13 for SQL Server does not support connections to SQL Server
2000 or earlier versions.
and below one on SSMS
Not associated with a trusted server connection
Not sure if I have some network configuration info wrong on vbox myb?
Might be using the wrong ip addr trying to connect aswell.
I use localhost to connect on virtual box.
Tried to connect by localhost ip, public ip and
sudo ip addr show eth0 | grep "inet"
command as well.
Any idea what could be the issue since I am quite sure both the sql server versions are up to date.
Solved upon changing network attached to on virtual box settings to bridged adapter with promiscuous mode on.
In case anyone gets stuck on this

Why can I connect to PostgreSQL server with PgAdmin from outside network, but not within it?

I have a PostgreSQL server set up on Ubuntu on a computer connected to my home WiFi. I also have a Windows machine with pgAdmin set up to connect to this server. However, I found that the windows machine is only able to connect to the PostgreSQL server when it's on a different network from my home wifi. When I try to connect to the server from the same wifi network, I get "server doesn't listen." Why does this happen, and how can I fix it?

Unable to connect to SQL Server 2005 installed on Win7 virtual machine

I am not able to connect to a SQL Server 2005 hosted on a Win7 virtual machine. I am new to VM, can someone help me locate the problem?
I am able to connect another SQL server which is installed on the local machine.
When you say you can't connect - that can mean a lot of things - really you need to be much more specific.
In addition to the comments and answers already here - If you're having trouble connecting to it in Sql Server Management Studio - you should open Configuration Manager on the VM itself and make sure that Shared Memory and Named Pipes are enabled (open the SQL Server Network Configuration node in the tree).
For example, SQL Server Express instances are configured by default to reject the kind of remote connection that SSMS wants to open by default.
first of all check your connection string (for reference):
http://www.connectionstrings.com/
Second you need to add an exception in the guest machine firewall or completely disable it (port 1433 is for sql tcp/ip access).
this works fine for me:
SQLConn.ConnectionString = "Network Library=DBMSSOCN; Data Source=xxx.xxx.xxx.xxx,1433;
Initial Catalog=mySQLServerDBName; User ID=myUsername;Password=myPassword"
good luck

How to solve sql server remote exe connection issue?

Sql server is installed in remote machine. When i connect that remote sql sever 2005 through code or run exe from my system, its working fine.Exe's are placed in remote machine and the sql sever also exists in that machine. When i try to open that exe from that remote system, i am getting sql server connection error.
The exe worked in windows xp without any issue, facing this issue only in windows 7.
Read an article in microsoft, it asks to add new rule under windows firefall, inbounds and outbounds. Added TPC, UDP port as mentioned.
Tried the below 2 links. Still i am in trouble.
http://www.sevenforums.com/system-security/58817-remote-access-sql-server-express-2008-windows-7-a.html
http://msdn.microsoft.com/en-us/library/ms190181.aspx
Can anybody guide me in this regards.
Is this the default SQL Server instance or have you given it a name? If you have named it, you should access it as ServerName\InstanceName
Is it using port 1433? If so, you must open TCP port 1433 in the firewall. If it is not the default instance it is possibly using dynamic ports which may not be open in your firewall. Also you may need to open the UDP port 1434 so the Browser Service can be accessed (essential if you are using dynamic ports).
Is TCP enabled or are you using the default Shared Memory (you said this worked fine from an XP client so I imagine this is OK).