|
|
Posted by bass_player [SBS-MVP] on 10/01/07 04:09
Have you tried running SQL Profiler to check whether or not any application
can connect to SQL Server?
"John" <John@nospam.infovis.co.uk> wrote in message
news:%23z5FMf7AIHA.4568@TK2MSFTNGP02.phx.gbl...
>I am using the remote servers ip address, as provided by the host, instead
>of server name.
>
> Doing telnet <remote sql ip> 1433, the isa log registers access on port
> 1433 but accessing the remote sql server using sql server management
> studio express to connect, isa log does not log any attempt on port 1433.
> I can't figure out why the management studio is not connecting on port
> 1433 or how to make it do it.
>
> Thanks
>
> Regards
>
> "Erland Sommarskog" <esquel@sommarskog.se> wrote in message
> news:Xns99BC1E65262FYazorman@127.0.0.1...
>> John (livingusman@googlemail.com) writes:
>>> I don't know as it is remotely located. I received ip and username/
>>> password from host which worked fine on old sbs 2000 + isa 2000 server
>>> but not on new sbs 2003 r2 + isa 2004. Anyway I can check?
>>
>> A named instance has a name like SERVER\INSTANCE. To be able to access
>> a named instance you need to have its port number open. And if you also
>> access it one the form SERVER\INSTANCE, you need access to UDP port
>> 1434. (You can always access it as SERVER,portnum.)
>>
>> May be you should ask in a forum about ISA Server (which I'm completely
>> ignorant of)?
>>
>> You should check with you host on which port SQL Server is listening.
>>
>> --
>> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>>
>> Books Online for SQL Server 2005 at
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>> Books Online for SQL Server 2000 at
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>
Navigation:
[Reply to this message]
|