October 4, 2007 at 12:27 pm
I am an intern with no previous experience with SQL Server. I have 2005 standard edition that i installed onto our web and ftp server. installation went great. i now need the other machines on our subnet to connect remotely to sql server. is there a client software i install or do i use the whole program? any other information you can give me would be a great help. our network is behind a pix router, so we dont use windows firewall, so i should't have to open a port on that. i have accessed surface area and enabled tcp/ip. i have also gone to configuration tools and enabled tcp/ip. thanks for the help.
October 4, 2007 at 2:08 pm
You can install the SQL Server client tools (from the SQL Server CD), but anything capable of making an ODBC or OLEDB connection (including Microsoft Access) will do. How do your users need to work with the data? That's the big question. The pieces at the operating system level that allow a client application like Access connect to the SQL Server should already be in place.
K. Brian Kelley
@kbriankelley
October 5, 2007 at 11:28 am
we wont be doing much data manipulation. we are a software development company and will need to occasionaly access the server for development. i have installed client tools on a machine in our network. i have enabled tcp/ip. i opened management studio. do i just type in the name of the server to connect to? the message i got was
"TITLE: Connect to Server
------------------------------
Cannot connect to winserv1.
------------------------------
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
I also browsed for network servers and nothing came up... thanks a lot for the help
andrew
October 7, 2007 at 9:06 pm
Hi,
Check for the following
1.) Try connect using correct protocol
2.) Check whether allow remote connections has been enabled
3.) Firewall may block the particular port used for connection
Regards..Vidhya Sagar
SQL-Articles
October 8, 2007 at 10:53 am
tcp/ip in enabled under client protocols, port 1433 is allowed. no are no components installed so i didnt configure surface area. our network is behind a PIX router, but that shouldn't matter, right?
October 8, 2007 at 10:20 pm
The PIX won't pass 1433 by default.
October 9, 2007 at 4:06 pm
andrewbrinker (10/8/2007)
tcp/ip in enabled under client protocols, port 1433 is allowed. no are no components installed so i didnt configure surface area. our network is behind a PIX router, but that shouldn't matter, right?
If you don't enable remote connections from within Surface configuration, your PIX firewall is the least of your trouble (your server won't "talk" to anyone else). Since you're going over multiple subnets - make sure to enable TCP/IP connections.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 10, 2007 at 10:31 am
remote connections are enabled from surface on the server side. do you have to have an instance on the server side to connect or can i connect straight to the server? if so how do i make one?
October 10, 2007 at 10:48 am
You always connect to an instance - it's a matter of whether you've made a NAMED instance or not. You should be able connect to either
If you have a firewall between you and the server, or if the server is on a different subnet - you should try NOT allowing named pipes. The error below specifically mentions named pipes, which means it's being used as the default protocol. You really need to try to get it to use TCP instead.
Do it from a client machine: use the SS config mgr on the client and remove/disable named pipes. Also - in the SERVER config - make sure TCP/IP is not set up to use a dynamic port (my default install certainly was). If there is a 0 under dynamic port - it's going to use a dynamic port. Disable that by removing the value.
Make sure the port you pick (may be 1433, may not be) is a. open on the firewall, and b. matches what both the client maching and the server say it should be. Create an alias if necessry.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 10, 2007 at 11:29 am
i have no firewall between client and server. native client on server and client both match. when i looked at mssqlserver properties on server, the server name is WINSERV1. the instance box is blank. should i just type in WINSERV1 for the server name? when i open the drop down menu for server name, i should be able to "browse for more" and see the server from the network servers tab, right? thats not the case. i know im missing something small here, i just cant figure it out. thanks for everyones help so far.
andrew
October 10, 2007 at 11:33 am
Try using just the server IP instead of name from the client. If that doesn't work - try a regular ping from the client to the server.
I still didn't see you mention anything as to disabling Named pipes - did you get a chance to try that?
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 10, 2007 at 11:44 am
the client and server are on the same subnet. i tried to type the ip address into the server name from the client. here is the error message:
TITLE: Connect to Server
------------------------------
Cannot connect to 192.168.1.10.
------------------------------
ADDITIONAL INFORMATION:
Login failed for user ''. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)
I have disabled named pipes on both sides. all that is enabled is shared memory and tcp/ip. as far as the dymanic port, the only option i saw under the properties was "port". it is set to 1433 on both sides
October 10, 2007 at 11:45 am
sorry, the ping was good between client and server also.
October 10, 2007 at 6:10 pm
Is the SQL Bowser service running? If it isn't - turn it on, and try the login again.
Also - are you trying to use mixed mode or windows auth only?
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 11, 2007 at 10:55 am
sql server browser is running. i am using windows auth mode. during the install, i didnt specify a name and password and domain. would this matter? also, do i need to set up an alias on just the client or client and server?
Viewing 15 posts - 1 through 15 (of 27 total)
You must be logged in to reply to this topic. Login to reply