I am running two Windows Servers 2012 R2 with SQL Server 2014 Standard Edition. I have strange issue on mirroring. I configured mirroring on for 15 databases, no Witness server. The Principal server show all database is Principal, Synchronized and the Mirror is Mirror, Synchronized/Restoring. When I open Database Mirror Monitor I see Role Principal is in Mirroring State Synchronized but the Mirror's Role is not connected. I have fail over in both directions and the database came up on the mirror server normally. data is replicating for troubleshooting purpose I have done below steps. 1. I have seen in error log in principle nothing is related to mirroring traced I can see most of the errors in principle are Error: 18456, Severity: 14, State: 38. 2. I have seen errors in mirroring server for all the databases are Database mirroring connection error 4 'An error occurred while receiving data: '10054(An existing connection was forcibly closed by the remote host.)'.' for 'TCP://server.company.com:5022'. Error: 1474, Severity: 16, State: 3. I have tried to resolve by stop and start the endpoint its was not resolved. 4. I have tried pause and resume it is also not resolved. 5. I have verified TCP/IP it is enabled on both the servers. 6. I have tried to configure alias it is also not resolve. 7. I have telnet from each other, it seems have no communication issues 8. I have verified connect rights to domain level same service account for both principle and mirror. 9. Earlier it is SQL server 2014 sp2 ,today I have updated with latest service sp3 even though still I can see same in mirror monitor Not connected to mirror. Please help on this issue, how to resolve this?

This isn't a duplicate; my scenario is different from others I've found: https://dba.stackexchange.com/q/61923/63237 https://blogs.msdn.microsoft.com/sql_pfe_blog/2016/10/05/tcp-port-is-already-in-use/ https://support.plesk.com/hc/en-us/articles/213409409 Differences: - Neither cls & netstat -oanb -p tcp nor TCPView reveal anything listening on port 1433 - According to the EventLog message, this is occurring on IPV6 - The problem doesn't manifest for two named instances running on the same machine—only the default instance To my knowledge, I'm not using IPV6 in any way, shape or form. I certainly haven't configured it. The service will start when I make any of these configurations: - Disable TCP/IP in SQL Configuration Manager - Enable TCP/IP but turn off **Listen All** in **TCP/IP Properties** - When **Listen All** is off, disable all IPs on the **IP Addresses** tab If I do either of these, the service fails to start: - Turn on **Listen All** - Enable any IP address This has got me pulling my hair out. What's gone wrong here?

I am using SQL Server 2022 and the "SQL Server configuration manager" is not visible. Further more I opened "Services and Applications" and in computer management and SQL Server is not showing even though I have multiple instances of SQL Server 2022 installed on my system. I have tried to remove the servers but it says I don't have apps associated with sql server so I can't uninstall it. I have searched everything on the web for last 2 days but of no use. Please someone help me in this regard. In SQL Server Management Studio, the server is connected but due to no part available, the backend of my express.js is not connecting to the server.

I have a named instance installed and have it set to use TCP port 1433 instead of Dynamic ports. The SQL browser is running and TCP IP is enabled. I have to put the port number 1433 on ssms and without including the port number it wont connect. Please advice what am I missing here. Is this a firewall issue or am I missing something.

All I want to do is to connect to SQL Server though Named Pipes **without** using an explicit way like *NP:ServerName* because mentioned *approach works*. **I want to connect through Named Pipes using just ServerName** and give a SQL Server a chance to choose the right network protocol. So I have **3** VMs: What I did step by step: 1. In **Server Configurations** of **SQL Server A** I enabled all network protocols. 2. I am also familiar with the Order column, however, changing it appears to have no affect. I swapped the order of **TCP/IP** and **Named Pipes**: 3. I tried to connect from **SQL Server** B into **SQL Server A** using **Computer Name**(**WIN-VKHOKLJ3IJG**) and I hoped that it will use Named Pipes protocol but unfortunately it chose TCP/IP as a connection protocol: Could someone explain why TCP/IP was chosen instead of Named Pipes? According the order, SQL Server should choose Named Pipes but it rather preferred to use TCP/IP.

I am aware that this or similar has been asked in other places. None of the other answers have worked for me. Machine is a Macbook Pro 2014 / OS X Yosemite 10.10 with Postgres 9.3.5 installed via Homebrew. I can only connect to my local postgres instance if I do NOT specify a host. This works: psql -Umyuser -d mydb sql (9.4.4) Type "help" for help. myuser=# -h localhost does not: psql -Umyuser -d mydb -h localhost psql: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. It pauses for a long time before I get this message. I am trying to set up a third party tool that seems to want to specify localhost, so it is not an option just to leave that off. If I understand what I've read correctly elsewhere, postgres behaves differently if you're using TCP/IP, and specifying -h localhost forces that. Accordingly I have added the following in pg_hba.conf: local all all trust # IPv4 local connections: host all all 127.0.0.1/32 trust host all all localhost trust # IPv6 local connections: host all all ::1/128 trust (127.0.0.1 AND localhost seems redundant but desperation drives superstition) ... and in postgresql.conf: listen_addresses = 'localhost' port = 5432 netstat confirms that Postgres is listening to that port: ☁ ~ netstat -an | grep 5432 tcp4 0 0 127.0.0.1.5432 *.* LISTEN tcp6 0 0 ::1.5432 *.* LISTEN d8d7c0e31d5add1d stream 0 0 d8d7c0e326b18a1d 0 0 0 /tmp/.s.PGSQL.5432 All permissions are set on the socket file: ~ ls -l /tmp/.s.PGSQL.5432 srwxrwxrwx 1 fritz wheel 0 12 Jul 13:27 /tmp/.s.PGSQL.5432 /etc/hosts has an entry for localhost: 127.0.0.1 localhost ::1 localhost psql and pg_ctl are pointing to the same installations: ~ which psql /usr/local/bin/psql ~ ll /usr/local/bin/psql /usr/local/bin/psql -> ../Cellar/postgresql/9.4.4/bin/psql ~ which pg_ctl /usr/local/bin/pg_ctl ~ ll /usr/local/bin/pg_ctl /usr/local/bin/pg_ctl -> ../Cellar/postgresql/9.4.4/bin/pg_ctl There's nothing named psql elsewhere on my system that seems like it could be hijacking this process: ~ sudo find / -name psql /Applications/pgAdmin3.app/Contents/SharedSupport/psql /Users/fritz/devtools/phantomjs/src/qt/config.tests/unix/psql /Users/fritz/Qt/5.3/Src/qtbase/config.tests/unix/psql /Users/fritz/Qt/5.3/Src/qtbase/src/plugins/sqldrivers/psql /Users/fritz/Qt/5.3/Src/qtbase/src/sql/drivers/psql /usr/local/bin/psql /usr/local/Cellar/postgresql/9.4.4/bin/psql UPDATE: telnet connects to localhost 5432 for a while and then is disconnected: ~ telnet localhost 5432 Trying ::1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. UPDATE 2: I used wireshark to spy on tcp localhost port 5432. Trouble is, I don't know what I should see and whether/how the results are wrong. Hoping someone out there can make something of this capture file .

I am using oracle database 12c and would like to setup TCP SSL connection to be able to connect using the same machine where the database is hosted. So, connection would be from database machine to itself using SSL. I believe there has to be some setup to the oracle wallet file but not quite sure what is the proper way to create the certificates since it will be on the same machines. Most tutorials show steps for a client to server setup, but I want a local setup. Any help/guidance is appreciated. Thanks!

Does any one know why the port my SQL Server is listening on would not be recorded in my errorlog? TCP/IP is enabled and default listening port 1433 configured. I have this issue on two servers: - one with a SQL 2008 configured - I can connect remotely to the instance from the management server using SSMS. However, I am unable to connect from the application I am testing connectivity from - the other is a SQL 2016 - I can also connect remotely to this from the management server and from the application I am testing connectivity from. Port 1433 is open on both host machines - netstat -na I expect to see an entry for listening port in my errorlog, would anyone know why it could be missing? thank you

I have installed an Enterprise version of DB2 on my local Windows 11 pro laptop for some development tasks. Installation proceeded without errors but, it seems I cannot connect using TCP. If I try to stop/start from the admin console, it says I do not have set the environment variables even if I try to printout it works. This is what I can see with db2set -all C:\Windows\System32>db2set -all [e] DB2PATH=C:\Program Files\IBM\SQLLIB [i] DB2INSTOWNER=LAPTOP-HBU9NEC4 [i] DB2PORTRANGE=20000:20005 [i] DB2INSTPROF=C:\PROGRAMDATA\IBM\DB2\DB2COPY1 [i] DB2COMM=TCPIP [g] DB2_EXTSECURITY=YES [g] DB2_COMMON_APP_DATA_PATH=C:\ProgramData [g] DB2SYSTEM=LAPTOP-HBU9NEC4 [g] DB2PATH=C:\Program Files\IBM\SQLLIB [g] DB2INSTDEF=DB2 [g] DB2ADMINSERVER=DB2DAS00 When I try to stop the DB I get C:\> db2stop SQL1390C The environment variable DB2INSTANCE is not defined or is invalid. I tried to print the DB2INSTACE and I get this: C:\>echo %DB2INSTANCE% DB2 This is what I get if I try to create a sample DB C:\>db2 create database TEST001 SQL1032N No start database manager command was issued. SQLSTATE=57019 Any clue? Thanks

I have a SQL server names as MS8AT09\AT09. I am able to login to the server through Microsoft SQL server Management studio. While trying to login to same server through JDBC I am facing the error as > "The TCP/IP connection to host XXXXXX, Port 1433 has failed. Verify > the connection properties. Make sure that an instance of SQL Server > is running on the host and accepting TCP/IP connections at the port. > Make sure that TCP connections to the port are not blocked by a > firewall". Please help.

In our Vb.net application(userd within a local network connection inside a office), which is used from long time now some of the users get the errors only sometimes a day > A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host. I have already checked following 1. All databases are set to autoclose OFF 2. Didn't find much network problems and network speed is good. 3. When I checked in SSMS the under server properties remote query time-out set to 600 seconds 4. I checked sql server log and no errors found relating to it or same error message So what may be the reason for this error? And how to troubleshoot it?

Simply to avoid many problems in the first place I do not want my postgres server program to accept/listen to anything from any network (i.e. TCP/IP 4/6) connections. My setup is a *Postgres 9.1* on an *Ubuntu 12.04* box and I thought tweeking /etc/postgresql/9.1/main/pg_hba.conf to not include those lines which commented out (see below) would cause postgres to "please not listen on network TCP/IP devices"

local   all             postgres        trust

# TYPE  DATABASE        USER            ADDRESS                 METHOD
# "local" is for Unix domain socket connections only
#local   all             all                                     md5
# IPv4 local connections:
#host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
#host    all             all             ::1/128                 md5

Also I know that there is the -i command line to start the postgres server with if we YES want to listen on TCP/IP . I actually seek for the opposite thing a -??? meaning NO please do NOT listen on TCP/IP. I used a netstat -utap | grep post and it shows that postgres besides my settings in /etc/postgresql/9.1/main/pg_hba.conf is still listening on TCP/IP. ## QUESTION ## What did I do wrong here? How can I shut off this TCP/IP listening attitude of my Postgres server? Having only unix socket listening I am happy to the max ;) Thank you Addition: I also perceive that postgres establishes a **UDP** connection to this 127.0.0.1:38860, what would this be about?

Is there a possible way to connect to a local SQL server on a static global IP? Let me elaborate. Assume that there is a server with a static global IP of 12.345.678.90 which refers to a certain windows based PC which in turn hosts a Microsoft SQL Server. Said server can be accessed remotely. The issue is the need to connect to another SQL server hosted on another PC on the same network with a "static local IP" of 192.168.1.100. Is there a way to connect to that server using a similar syntax to 12.345.678.90/192.168.1.100?

Imagine the following situation: You have a MySQL server S and two clients, A and B. Both clients connect to S (e.g. using the CLI). A starts a transaction and then locks a table with WRITE permissions and inserts a row into the table. Now B tries to select all rows from the table and - of course - has to wait until A has committed AND unlocked the table. Imagine that A's connection is interrupted before it is able to commit or rollback. In my special use-case, the connection might be interrupted at any point in time. I tested this scenario using three virtual machines which are connected to a common virtual bridge. Using brctl I can simply remove individual VMs in order to simulate connection interruptions. ### The result Client B is stuck, because it waits for the table to get unlocked. Typing SHOW PROCESSLIST in the CLI of the server shows me this:

+----+------+-----------------+----------+---------+------+---------------------------------+----------------------------+----------+
| Id | User | Host            | db       | Command | Time | State                           | Info                       | Progress |
+----+------+-----------------+----------+---------+------+---------------------------------+----------------------------+----------+
|  8 | root | B:38129         | foo      | Query   | 1676 | Waiting for table metadata lock | select blockname from root |    0.000 |
|  9 | root | A:54806         | foo      | Sleep   | 1679 |                                 | NULL                       |    0.000 |
| 12 | root | localhost       | NULL     | Query   |    0 | init                            | show processlist           |    0.000 |
+----+------+-----------------+----------+---------+------+---------------------------------+----------------------------+----------+

So the server thinks that the connection from A is still alive, while it already was lost _minutes_ ago. Having a look at netstat also tells me that the connection is still considered to be ESTABLISHED and still alive. I also observed the bridge: Not a single packet from S to A. Client B is stuck forever. I have to restart the whole server to unlock the table. ### What I expected I want my server to detect (after some predefined time) that the connection to A is lost even if A did not send any more queries. Then I want my server to rollback any uncommitted transactions and finally to unlock the table. How can I realise this? Why aren't there any TCP keepalives from S to A? Is it possible to define any kind of timeouts? --- I played around with the variables wait_timeout, innodb_lock_wait_timeout, and interactive_timeout. * interactive_timeout is not interesting because my productive system will not use the CLI. * innodb_lock_wait_timeout seems not to be respected in any way. * wait_timeout indeed improves my situation: idling sessions are killed after the timeout. But I only want them to be killed in case of connection interruption. I want to keep the connection alive to improve performance (save tcp handshakes, SQL logins, db selection...)

I have SQL SERVER 2008 R2 installed on windows Server 2016, it runs smoothly on a LAN network interface. I Added a USB MODEM (4G) to the server and went to the IP Addresses tab in network configuration to Adjust its IP Settings (enable the IP and set the port for listening) but it is not shown in the IP Addresses tab, I tried to restart the SQL services and restart the server but it is not showing. I searched the web but couldn't find an answer, what is the problem with it ?

I've configured a remote Sql server on host machine. I have performed the follwing steps : Under Remote Server Connections, check the box against "Allow remote connections to this server". Make sure that the TCP/IP Protocol Name is Enabled. Navigate to the IP Addresses tab and scroll down to the section named "IPAII". If the TCP Dynamic Ports is set to 0 (indicates the Database Engine is listening on dynamic ports), then remove the 0 and set it to blank. Update the value for TCP Port to 1433. Restart the service.  Windows Firewall setting inbound rule TCP, port 1433 , Allow the connection  Using this setup I'm able to connect from SSMS using aa.aaa.aa.aaa\SQLEXPRESS and from c# app using the following aa.aaa.aa.aaa\SQLEXPRESS,1433. I would like also to be able to connect using the host name instead of ip address. Is this possible? I have tried in SSMS using hostname\SQLEXPRESS or hostname\SQLEXPRESS,1433 but it doesn't connect and an error is shown saying : A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed out.) (Microsoft SQL Server, Error: 258) I should be able to connect also via the machine name. For local sql server it works to connect via hostname\sqlinstance.

I'm writing some test code that is required to connect to a local SQL Server instance (SQL Server 2017 - Developer Edition) by IP address. I have the SQL Server instance up and running on my machine, but can't figure out the correct IP + Port to use for my connection string's Server property. As a starting point, I'm trying to at least manually connect to my server instance with SQL Server Management Studio (via the IP address) but I can't seem to figure it out. 1. How do I find the IP Address and Port of my local SQL Server instance? 2. What is the correct format I should be inputting the IP Address and Port into the Server Name field of SSMS (and is it the same format as a connection string Server property)? I've tried locating the IP address executing the following SQL code on it: SELECT CONNECTIONPROPERTY('net_transport') AS net_transport, CONNECTIONPROPERTY('protocol_type') AS protocol_type, CONNECTIONPROPERTY('auth_scheme') AS auth_scheme, CONNECTIONPROPERTY('local_net_address') AS local_net_address, CONNECTIONPROPERTY('local_tcp_port') AS local_tcp_port, CONNECTIONPROPERTY('client_net_address') AS client_net_address But the local_net_address and local_tcp_port fields are NULL and the client_net_address is set to ``: I've also tried going into the SQL Server Configuration Manager, under the SQL Server Network Configuration section, and enabling TCP/IP. Then I tried using a mix of the IP4 and IP6 addresses with Port 1433 (which is blank by default in the TCP/IP Properties, but I've tried leaving it blank and setting it to 1433) and that didn't work. (I made sure to restart the SQL Server service and SQL Server Browser service every time I made changes in here.) I've received the following errors when trying to connect via SSMS for the different combinations of the IP4 address with and without Port specified: **No Port Specified:** **Port Specified w/ Colon:** **Port Specified w/ Comma:** I've also tried connecting via 127.0.0.1 with the same combinations of Port 1433 above to no avail. (I receive similar errors except for the following combinations.) **127.0.0.1 w/o Port:** **127.0.0.1 w/ Port via comma:**

I am using Mongodb 3.6.3 on Centos 7. I am running the below command: sudo mongod --storageEngine wiredTiger --dbpath /data --bind_ip_all --logpath /var/log/mongodb/mongod.log --fork and everything will work just fine. Except, binding all is not secure enough. I used to received a logging error when I tried --bind_ip 127.0.0.1,privateIP but discovered that the error would disappear when I did bind_ip [127.0.0.1,privateIP]. However, when I tried to connect to mongo locally it would fail and through a my site, it would sit there until it timed out. I checked sudo netstat -plnt | egrep mongodand then nothing showed up, which although it successfully forked the mongod process, it did not bind to any of the specified ips. For reference, when I tried the same command on on the --bind_ip_all version it returned tcp 0 0 0.0.0.0:27017 0.0.0.0:* LISTEN 1645/mongod. My question is, why did --bind_ip ips fail to bind to the specified ips? Side Note - when binding ips, should I bind my elastic ip or my private one?

In SQL Server Configuration Manager on the Advanced tab in TCP/IP Protocol properties box there is an option Accepted NTLM SPNs. What is the use of that option and how it can be used?

Since TCP checksumming is not sufficient to detect/prevent all corruption , do modern database systems (e.g. SQL Server, MariaDB / MySQL, Oracle, etc.) use any additional checksumming of network traffic as part of their client/server protocol? I did some searching but wasn't finding anything which made me wonder if perhaps they don't and just roll the dice. Got a good answer on Oracle. Would like to hear about SQL Server and MariaDB / MySQL as well.