I'm trying to setup SQL Server 2005 Express to communicate through a non standard port. I can connect to SQLServer on a remote machine using port 1433 when it is set as such but when I change the server to another port and try and connect using SSMSE I can't get through. I'm specifying the ip address and a colon followed by port number to connect.
For example: 123.123.123.123:1234
Any ideas?
----------------------------------
Standing on the shoulders of giants
I have to create a DSN for SQL-Server. Therefor I use the function "SQLConfigDataSource" from "ODBCCP32.DLL". But the problem is that the SQL-Server does not use the Standard-Portnumber 1433. I've tried to make the DSN with "SERVERNAME xxxx" where xxxx is the Portnumber, sometimes it works, but often it does not. When it does not work, then the Checkbox in the ODBC-Configuration-Tool is checked, so the connection is searching for the standard-port. How can I tell the system that it shall NOT use dynamic configuration?
I tried creating an alias to the server to get it to connect to analyze the server but it will not recognize the SQL 2000 server as a valid server to analyze. I can use the alias to connect in EM or SSMS. Any ideas? The server is not clustered and is at SP4. I've connected to several others in my environment but this one is causing me grief!
How do SQL 2000 service packs play a role in upgrading? That is, can SQL 2000 Standard with no Service Packs(SP) be upgraded to SQL 2005 Standard, or does SQL 2000 Standard have to have a certain service pack??
I have set up a new web server in my DMZ. This web server needs to "talk" to an application server located on my LAN. It communicates via a COM + Component.
I would like to keep the access that is open between the DMZ & LAN to minimal, obviously for security reasons. Does anyone know what port is used for COM + communication?
First of all I am planning to install sql 2005 standard and sql standard sp2 on vista ultimate professional using vs 2008 pro I have some questions about installing sql 2005 what is the best way to install sql 2005 on vista My article I got this from ms 403393 (upgrading sql standard 2005 to sql standard 2005sp2) 1 sql standard .(shortcut right click from cd/dvd not possible) I have heard command prompt start menu, click cmd type run D: cd/dvd exe From a wizard (sql sp2)
2. sql standard sp2 a. upgrade using a wizard b. open a command prompt (not sure if right click is best option) install dvd media example dqlserver2005sp2-kb921896-exe SKUUPGRADE=1(is run as administrator option on media) do I type run or what do I type ? c. go to system configuration page(where is this) you should see a single warnining you need to install sp2, the edition should say success if it does not please reapply d. on the registration page please enter your registeration number e. on the comments to install please enter database services, reporting services workstation components, books online and development tools( I wish to install all components)
f. on the instance page click default instance(default install) g. finish rest of wizard h. apply sql sp2
I also have of seperate question of upgrading sql from vista using a Configuring local admin account account (configuring administration from a wizard-will this notify me by default) I do not want my administrative priviledges elevated. I will be using default configurations for my installations......... I often wish there would a nice picture examples of doing this Please help
24/7 Production Call Centre server running NT4.0 and SQL 6.5 with all the latest service packs.
SQL mail fails(with dull regularity) and the SQL server services stop.
When the SQL server Services are restarted an error message appears stating that Port 1433 is in use after which nobody can connect via TCP/IP. Obviously the port believes the previous SQL session is still running, and won't release the port to the "New Application requesting it".
On a unix system you can force a port reset so you don't need to shutdown and restart the box. Can you do this from either SQL or NT?
Any solutions would be greatly appreciated the DBA's are 100 Miles from the Servers, so restarts are reliant on other people!
Does anyone have an idea on why when using IP with port 1433 that on the SQL 2000 Server a bind failure happens on port 1433 and are not able to get to the SQL using IP but you can use Named Pipes.
I've been diagnosing deadlocks for a last couple weeks at a client site and I understand the KEY: and TAB: locks issues. However, the client recently experienced a series of multi-branch deadlocks for which I can find no information. Attached is the deadlock text from the ERRORLOG. Any help would be much appreciated.
Iwant to know PORT number of B on A server. Iam following the following process to get B PORT number.
1) Loging to server A. 2)Opened SQL Server Configuration Manager. 3)Opened SQL Server 2005 Network Configuration. 4)Opened TCPIP properties of Protocol for B. 5)On that opened IP Address TAB 6)Got PORT number from TCP Dynamic Ports
Am i going n right way. If not please advice me the right way to get port numbers.
1. Is there a quick way to find out what port number SQL is listening to? I have 10 instances running on one server and I could find out by going to SQL log but it's bit time consuming.
Not sure how this particular topic should be labeled but I figured I would start here.
I have a third party Time and Attendance program that uses SQL 2000 and IIS on top of Win2003. It also uses a client side program that sits on an XP box that pulls Time clocks entries than passes that info to the SQL server. We recently needed to move to a different service, still utilizing the same Time and Attendance program but a different client utility that pulls the Time clocks. Both the client and Time and Attnedants program are developed by the same company. All that being said the new clock utility cannot connect to the SQL service. The difference between the 2 utilities is the first utility uses UDP, the second uses TCP and requires port 5405. Basically the way I€™m seeing things is that the server does not have port 5405 open this also confirmed by the company the wrote the program. There is no firewall on this server. RRAS is installed but does not have any filters enables which I believe means it will receive and pass all protocols to all ports. Using a port scan utility it shows port 5405 not to be open How can I get port 5405 open?
Just wanted to find out what port does SSIS utilizes when communicated with a remote SQL Server. Is it 1434, 1433 or something? I have a SSIS Package on Server 1, which which does inserts on SQL DB on Server 2. I think between Server 1 and Server 2, some ports are being blocked because the 2 servers are separated by a firewall. When SSIS makes connection to Server 2 (SQL), what ports does it use? Also, any other tips would also help. Here is the error I am getting:
Cannot connect to 10.xx.xx.xx.
===================================
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
I installed a new instance and changed the default tcp/ip port and configured the applications. based on request i have changed the port to default 1433. now the problem is, the instance is not coming up. Then I restored the port now its working fine. But the application user wants 1433. could you please tell me why the instances is not comming up if the port is 1433? Thanks in advance
The powers that be at my company have decided to redisign our network. The big change is that they are completely separating the two domains, whereas I guess right now one runs inside of the other.
What this means to me is that I need to get a document together which shows all the connections between different SQL servers, web pages and services that I've created over the last year.
My question is, what ports do all of these things use to communicate with SQL Server 2000? I believe the only connections right now are using ADO/ADO.NET, or straight SQL Linked Servers.
Hello. I'm a novice with SQL Server. I set up a SQL Server instance using Enterprise Manager and I want to find out what port that instance is listening to, because it's not listening to the default.
Is there a way I can specify a port for the server to listen to?
Hello. I'm a novice with SQL Server. I set up a SQL Server instance using Enterprise Manager and I want to find out what port that instance is listening to, because it's not listening to the default.
Everything is on my local machine, this is a development database.
Is there a way I can specify a port for the server to listen to?
So, I have 2 laptops, both with standalone SQL Server 2012 Management Studio.
laptop 1 can connect to my remote server on xxx.xxx.xxx.xxx,1433 laptop 2 cannot connect through management studio - but can connect directly from the development website on this machine.
I get error 18456, cannot connect to server and login failed for 'user'
I have access to the default instance of a SQL Server ..... I have access to the QA only .. by reading the registry through the QA I get to knw that there are additional 4 more instances on the Server ..... is is possible to get the port on which they are listening using the QA ....
I knw that we can go to the servers network utility & see it there in the TCP /IP ... but i dont have access to that , neither do i have access to the error logs that tell me , on which port is SQL Server listening to
Hey all.I'm running SQL server 2000, on W2K server. All the latest patches/etcfor both installed.I've a need to allow remote access to the DB. I have a strong passwordon the sa account, and have completed the various security checklistson the MS website, including running the baseline security program theyprovide.Due to the nature of the application, windows authentication is notpossible.Besides someone trying to hack in via a password guess, are there anyother things I need to worry about? Again, all the latest patches andwhat not are installed.ThanksMatt
