InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 03:27:28 GMT20http://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxHi Steve, What do you mean that SQL express only uses a local connection. So if I have an sqlexpress edition on a network I cannot link different microsoft access databases to it? Secondly, how do I log on to the server with SSMS using the ip and port number?I am new to sql server so I hope these questions aren't to foolish!!DallrTue, 01 Jul 2008 15:55:21 GMTdallrhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxCan't you change your port number?Wed, 26 Mar 2008 20:00:22 GMTRBarryYounghttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxHi Everyone,Well I found the issue that I have been having...My Isp is screwing me. At first they said they were only blocking port 25, then i called today and found out that they blocked port 1433 to 1434! Talk about irritating. They claimed they had many attacks and that they will not unblock these ports for me. Now since my hosting company cannot change the ports because then it would affect all the other clients sites, I have to move up to a vps or vpn. Which is more expensive. So i spoke with them about a change of plan...So thanks for everyones help it was greatly appreciated. My isp sucks.lolSo if i get what i want through my hosting company how do i go about changing the ports for sql server express?Wed, 26 Mar 2008 06:45:59 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxMatt brings up a good point, though for something personal, perhaps it's not that big a deal. It would be better to have VPN, and I mentioned to Chris that I can't point him to another server to test because they're all protected and hidden.Lots of hosting companies allow this, and good or bad, I'm not sure what is wrong with Chris' setup.Chris, one thing to keep in mind is that Express and the install on your PC has nothing to do with the remote server. You should be able to use Excel or any ODBC/OLEDB compliant client to connect with the credentials. I still think there's some strange networking thing going on with your PC.Mon, 24 Mar 2008 14:01:01 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxThe bigger question is - why is it set up this way? The fact that the hosting company has your database server set up "in the open" would be a HUGE red flag. That's like leaving the keys in your car AND putting up the neon sign pointing that out to everyone coming by.All due respect - there's no way you should be able to connect remotely to the database via SSMS over the internet. That's a HUGE security flaw, and (IMO) whichever hosting company set this up ought go back and review their security setup. Of course - that involves pulling their head out of wherever it's stuck right now.....Mon, 24 Mar 2008 13:35:30 GMTMatt Miller (#4)http://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxHi Steve,No i am not using a laptop..its my own pc, with a wireless card on it.I am using express edition 2005Mon, 24 Mar 2008 09:39:10 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxThe connection worked fine for me with credentials Chris supplied, so I'm guessing there's some firewall or limiting factor either on his network or elsewhere. I sent some screen shots to Chris of what I have for SSMS and asked if he has the Express edition or Developer SSMS.Chris, one more thought, have you used this laptop elsewhere to connect to SQL Servers? Can you try from another network as a test, even a Starbucks/hotspot?Mon, 24 Mar 2008 09:34:54 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxThe funny thing is, is that I can ping the server that my db is residing on. I had afriend of mine try connecting from his workplace and he can't get connected either, and he works at a development company. So if he can't even connect and I am not sure if steve will be able to but if he can't connect either then it definetly has to an issue at the hostibg company.They had asked me a couple days ago to ask my isp if they were blocking port 1433, and they said no the only port in which they block is 25.I will give the hosting company another day or so before i end up pulling the plug. because like i have said its not supposed to be this difficult. I even have my router wide open, no security settings at all. Its there for people to piggy back which sucks for me.They were making me believe that it was from my end...I even unistalled sqlexpress 2 times and set it up again with all defualts i changed the settings after words in the config and surface config to enable tcpip and pipes local and remote connections everything is enabled for it to be a go but it doesn't work.When i was developing at a compnay i was previously at i had no issues connecting to my db's or internal dbs on the intranet. This is getting to the point of beyond ridiculous. maybe their servers don't like canadian connections..lmaoMon, 24 Mar 2008 09:25:57 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxTracert timing out doesn't surprise me at all. When I didn't have my firewall exceptions set properly, although I had enabled exceptions as identified in MS KB Article 914277 (sqlserver.exe & sqlbrowser.exe), I also could not ping my "hosting" server. It would continually show request timed out, which is what led me down the path of the firewall to being with. Then when I could ping and connect using SSMSE from the XP machine when I disabled the firewall, it took no time to determine what was not identified in the article, File and Printer Sharing needed to be enabled.Mon, 24 Mar 2008 08:54:31 GMTEd Salyerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxlol..Thanks Steve, I sent you an email about 10 minutes with all the info you will need.Again thanks for all the help. It seems as though the hosting company is stumped altogether on this..lol I sent them 3 tracert's already and it times out outside their server.Mon, 24 Mar 2008 08:44:46 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspx:), It certainly shouldn't be.Willing to do a test if you like. If I mess it up, feel free to post a complaint here where everyone can see it :)Mon, 24 Mar 2008 08:41:36 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxThats what they told me that i am allowed to connect through 1433. Its getting to the point where i think i may need to get a new hosting company, because in all respect its not supposed to be this difficult. This has been going on since friday.Mon, 24 Mar 2008 08:39:48 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxEd has a good point. I'd also ask the hosting company if they allow direct, 1433 connections from your local PC to the remote SQL Server. They might not.Mon, 24 Mar 2008 08:35:17 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxI was not speaking of a firewall on the PC you are using when trying to connect to the remote db. My firewall exceptions needed to be set on the Windows Server 2003 PC that I connect to that houses my SQL 2000 and SQL Server 2005 database servers. You would need to have the hosting server folks verify they have the firewall exceptions added that are needed, unless they have their firewall disabled, which I wouldn't think would be a great idea.Mon, 24 Mar 2008 08:29:41 GMTEd Salyerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxSorry for the delay, Chris.Let me try and explain how this works and then maybe you'll see a hole in what's happening.When you install SQL Server 2005, it runs on TCP/IP by default, port 1433, and allows you to connect with any Windows PC, using the standard ODBC dialogs. You connect using either the IP, the Windows name (+ /instancename if you use instances), or if you are on the console, then using "(local)".SQL Server Express only allows local connections, meaning from the console of that server, by default, but the other editions should allow remote connections. However you need to check this using another machine. If the hosting company says they can connect from their workstations, not being the console, then that's not the issue.When you connect with SSMS, SSMS is on your workstation and makes a socket connection to SQL Server, even if SQL Server is on your local machine. So you can't necessarily use SSMS to check settings on the server.From what you're describing, it sounds like either they're a networking issue, or you are using Named Pipes by default to connect to a remote machine. Try opening the SSMS, typing in the address of the server, then hitting options. Manually choose TCP/IP to connect. See what happens.alternatively, I'll try from here if you want to email me directly (sjones @ sqlservercentral.com). Set up a new user, or get the hosting company to change the password for a one time connect that you can change or remove after a test.SteveMon, 24 Mar 2008 08:21:35 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxHi Ed,I don't have any firewall on my pc and file printer sharing is enabled. I also had a friend of mine try connecting the the host server and he gets the same error I do. I have sent a tracert to the hosting company and it times out just before their server.They have this asp.net enterprise manager web app that i can use to do my database stuff but its very limited, and annoying to use.Mon, 24 Mar 2008 08:21:18 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxI had the same problem last week. I created a SQL 2005 database server on the same server I was running SQL 2000 on. When I tried to connect from an XP machine, I got the same error you describe. What I found to be my problem was not having File and Printer Sharing as an allowed Firewall exception along with the exceptions for sqlbrowser.exe and sqlserver.exe which I had created.Mon, 24 Mar 2008 08:12:20 GMTEd Salyerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxHi Old, yes the sql server browser is running.Hemant, I have spoke with hosting company they are allowing remote connections. They changed me over to a new server but that still doesn't work.Mon, 24 Mar 2008 07:53:56 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxHi Old, yes the sql server browser is running.Hemant, I have spoke with hosting company they are allowing remote connections. They changed me over to a new server but that still doesn't work.Mon, 24 Mar 2008 07:53:14 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxHi,you need to enable remote connection at your Host server, follow and check the steps listed here http://support.microsoft.com/kb/914277Mon, 24 Mar 2008 02:12:10 GMTHemantgiri S. Goswamihttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxPlease check if the SQL Browser service is running or not?Mon, 24 Mar 2008 01:07:36 GMTMaverick100877http://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxSorry about posting in the wrong area..I spoke with my isp as well as the hosting company, neither is filtering out 1433. i'm trying to connect from my pc. I have a website that allows me to use sql server db's and they can connect to it, but i keep getting the same error. From my pc in the ssm express i have enabled remote connections..as for the sp_configure i really have no idea on how to use it.I have connected to sql db's on intranets at a company that i used to work for but this kind of remote connection is new to me.I have 2 pcs, one in the basement which has a router connected to the main modem and my pc ( that is upstairs ) that has a wireless card in it. my pc upstairs is the one i am trying to connect to.Sat, 22 Mar 2008 21:29:42 GMTchrismillerhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxFirst, did you add named pipes to the server? I'm not sure named pipes works through routers. I think it's a networking issue. You can use sp_configure or EM to set the "allow remote connections" to on.Be sure that the hosting company isn't filtering out 1433, which is the default method to connect.Are you connecting from the web server or from your machine?Lastly, please post in the appropriate forum. I moved this to the 2005 forum.Sat, 22 Mar 2008 20:36:23 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic473222-146-1.aspxHi All,I am not sure if this is a newbie question or not...I have this website which allows me to use sql server. I cannot get it to connect to the remote server at all. First I used sms 2005 express, didn't work then i uninstalled it and installed sms 2005 developer edition and let it set all the defaults. I cannot for the life of me get it to connect to the remote server. Now the hosting company can connect to it. I keep getting this error...An error has occurred while establishing a connection to the server. Whenconnecting to SQL Server 2005, this failure may be caused by the fact thatunder the default settings SQL Server does not allow remote connections.(provider: Named Pipes Provider, error: 40 - Could not open a connection toSQL Server) (Microsoft SQL Server, Error: 53)I am running win2k. I also enabled named pipes and tcpip and cannot get connected...Anyone have any idea on this? the hosting company seems stumped. I have no firewall running, no antivirus and my router is set to defaults no security.Sat, 22 Mar 2008 08:44:51 GMTchrismiller