Connecting SQL Mgr to non-1433 port?

Ok, if I change the TCP Listen port for SQL Svr to a port other than 1433, I
have been unable to get SQL Mgr to connect to it (this is even if I'm using
SM on the same machine as the SQL service).
I can connect if instead of the IP address I use ".", but trying to connect
via the IP address, no go.
Anyone have a workaround for this?
Thanks,
CC
cc wrote:
> Ok, if I change the TCP Listen port for SQL Svr to a port other than 1433, I
> have been unable to get SQL Mgr to connect to it (this is even if I'm using
> SM on the same machine as the SQL service).
> I can connect if instead of the IP address I use ".", but trying to connect
> via the IP address, no go.
> Anyone have a workaround for this?
> Thanks,
> CC
Include the port number in the hostname that you connect to, i.e.
myserver,1433
or
100.100.100.100,1433
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Tracy:
Ah, thank you, I had been using a ':'
CC
"Tracy McKibben" wrote:

> cc wrote:
> Include the port number in the hostname that you connect to, i.e.
> myserver,1433
> or
> 100.100.100.100,1433
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Connecting SQL Mgr to non-1433 port?

Ok, if I change the TCP Listen port for SQL Svr to a port other than 1433, I
have been unable to get SQL Mgr to connect to it (this is even if I'm using
SM on the same machine as the SQL service).
I can connect if instead of the IP address I use ".", but trying to connect
via the IP address, no go.
Anyone have a workaround for this?
Thanks,
CCcc wrote:
> Ok, if I change the TCP Listen port for SQL Svr to a port other than 1433,
I
> have been unable to get SQL Mgr to connect to it (this is even if I'm usin
g
> SM on the same machine as the SQL service).
> I can connect if instead of the IP address I use ".", but trying to connec
t
> via the IP address, no go.
> Anyone have a workaround for this?
> Thanks,
> CC
Include the port number in the hostname that you connect to, i.e.
myserver,1433
or
100.100.100.100,1433
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy:
Ah, thank you, I had been using a ':'
CC
"Tracy McKibben" wrote:

> cc wrote:
> Include the port number in the hostname that you connect to, i.e.
> myserver,1433
> or
> 100.100.100.100,1433
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Connect to SQL Server over the internet

Hi,
Computer A is where is installed SQL server 2000 and the BE. Computer B, I
have the FE (ADP in access 2003). The both computers are connected the
internet.
So, how can I connect to SQL Server over the internet? I mean, I want
connect my FE Computer B) to BE (computer A).
I listen something, we can do this connection trough IP address, but I don't
have idea how can I do.
Any Ideas?
Thanks,
Jos Perdigoif you truly have got your server completely exposed over the internet,
I wouldn't bother connecting to them, everyone else will be doing that
for you.
you can put an ip address in a connection string just as you can a
server name, so if you're currently connecting saying
server=MyExposedServer;database=db1 you can instead connect with
server=1.1.1.1 etc. where 1.1.1.1 is your server ip.
I doubt you have exposed your SQL server like this as it's not a good
idea, so you'll have to consider configuring firewalls, creating VPN
connections, etc.
Cheers
Will|||And if I protected my database with login and password? Is it security?
Thanks
jos perdigao
"Will" <william_pegg@.yahoo.co.uk> wrote in message
news:1145373393.799617.84180@.z34g2000cwc.googlegroups.com...
> if you truly have got your server completely exposed over the internet,
> I wouldn't bother connecting to them, everyone else will be doing that
> for you.
> you can put an ip address in a connection string just as you can a
> server name, so if you're currently connecting saying
> server=MyExposedServer;database=db1 you can instead connect with
> server=1.1.1.1 etc. where 1.1.1.1 is your server ip.
> I doubt you have exposed your SQL server like this as it's not a good
> idea, so you'll have to consider configuring firewalls, creating VPN
> connections, etc.
> Cheers
> Will
>|||It's a bit like saying, if I put a lock on my door, is my house safe?
Yes to a casual intruder, but there are different levels of security.
Why do you need to connect to your SQL server over the internet? As I
see it you're writing a client based application, so you will have some
kind of an installation process, at which point you could set up a vpn
connection to your SQL server. This means that you could put you SQL
server behind a firewall and configure a much more secure setup.
I'm nothing more than familiar with server security, but the idea of
just exposing a sql server to the internet without anything more than a
password on the database strikes me as being a very bad idea.
I would suggest posting a question on this to the sqlserver.security
group. As for the programming side, all I can say is that you can
replace your server name with an I.P. address and your client
connection should work just as though you're on a LAN.
Cheers
Will