Off the top of my head I recall something about the appropriate protocols being enabled? i.e. SQL Express may only be listening on local native client and not TCP/IP
On 23 November 2013 11:50, Greg Keogh <[email protected]> wrote: > I forgot to mention this is SQL Server 2008R2. I have "Allow remote > connections to this server" checked. I also noticed in the tcpview utility > that the SQL Server process is not listening on port 1433 and it never > seems to open (but perhaps it doesn't work the way I expect). I > also forward port udp 1434 just in case the sql browser needs this, but it > makes no difference -- Greg > > > On 23 November 2013 09:21, Greg Keogh <[email protected]> wrote: > >> Folks, I want to connect to SQL Server Express on my home server from the >> outside world. >> >> My router forwards tcp 1433 to the correct machine. I can see port 1433 >> visible but closed in Gibson's port scan. Attempts to connect time out. >> >> I'm guessing therefore that I've missed some setting inside SQL Server >> itself to allow outside connections, but I'm stumped. Any advice anyone?! >> I'm sure I did this years ago, but it's not so easy this time. >> >> Thanks >> Greg K >> > > -- regards, Preet, Overlooking the Ocean, Auckland
