Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cipherus
Starting Member
5 Posts |
 Posted - 2005-06-09 : 23:08:30
|
| i installed SQL server 2000 (just updated it to sp3a) on a windows 2003 std box. the enterprise manager on that box can connect to the localhost server no problem, but when i try to connect to it from my enterprise manager on my home computer, it either doesn't find it or can't login for some reason. When i try to register new server, i put the IP address in the Server: field, and have tried both Windows login and SQL Server login methods. no go.there is no firewall on the colo, and im fairly new to SQL server. but looking through several books online, the free MS books library, and a bunch of other places, there seems to be no description at all about even setting SQL server up for remote connections... so maybe i installed it wrong or something?any help would be much appreciated. |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-06-09 : 23:23:50
|
| You sure there's no firewall? Do you have any network protocols enabled for SQL Server on the colo server?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
cipherus
Starting Member
5 Posts |
Posted - 2005-06-10 : 00:04:44
|
| 100% sure there is no firewall. was thinking of adding one soon though. what port(s) would i have to open?Enabled protocols by order:TCP/IPNamed Pipesand just installed SP4 now |
|
|
|
cipherus
Starting Member
5 Posts |
Posted - 2005-06-10 : 01:50:17
|
| another few things i was thinking:is there someplace with a list of allowed/denied IP addresses somewhere in MSSQL?do i have to have a qualified domain name? (e.g. mssql.mydomain.com) to connect, rather than an ip address? probably not.. but worth a guess. maybe there is a specific way i can add it to my DNS forward lookups to make it go to the right place.another thing, i'm use an education version of enterprise 2000. not that i think it would limit the service in anyway, but maybe that could be part of it.does the SQL server name have to be Default for it to accept incoming IP connections? because i didn't use the default setting, i named it something else.also, when people install SQL server 2000, basically you just install it and should be able to connect from across the internet no problem without any added settings, right? (not taking into account firewalls on the server).another thing, i have it set for Mixed authentication, should i set up for just windows authentication? has anyone seen that to make a difference?answers to any of these questions would be greatly appreciated. |
|
|
|
cipherus
Starting Member
5 Posts |
Posted - 2005-06-10 : 04:02:13
|
| you know what's funny. i was using the wrong connection string in the server field.i was just putting the ip address instead of (ip address)\(named instance of server)5 letters have been keeping me stumped all day >_< |
|
|
|
|
|
|
|
|
installing on a remote colocation server