Re: Publish SQL 2000 to Inet

OK,

There's one other possible issue you might have. In the configuration of
your ODBC data source/alias for SQL on the client workstation, make sure you
go to the "Client Configuration" window and uncheck the "Dynamically
determine port" option, then force the port number to 1433 (if that's the
appropriate port now). The "dynamically determine port" option relies on a
packet sent from the client to the SQL server with a request for the port
number. This will fail because your client is not on the same subnet as your
SQL Server anymore. But if you specify the port number manually in the Alias
configuration as described above, it should work.

To further compound the problem I seem to recall some issue with dynamically
detecting port numbers of non-default SQL instances. I don't know or
remember if that is still the case with the latest SQL Service Pack or not.
I searched the MS KB for this one but couldn't find it - it's been a long
time ago since I had that issue and it might have been fixed in the
meantime. Anyways if you uncheck the "dynamic" option it should work,
provided your server publishing rule has been properly configured (it seems
OK to me).

Virgil




"beto @ southworks" <beto@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OYUdgJbyFHA.3696@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks for your reply Virgil! I'm using SQL Server authentication, for
> testing purposes I've registered the SQL Server instance from a
> workstation inside the LAN without looping through the ISA Server and I've
> registered it succesfully.
> So there is no doubt for me that it must be an ISA Server issue.
>
> I'm not sure if it is worth to comment but when I've installed SQL Server
> I've configured the TCP/IP Port to 2866. Then I've change it to the
> default port value (1433) to make sure that it wasn´t my problem.
>
> Thanks Again Virgil!
>
> "ZVR" <nospamever@xxxxxx> wrote in message
> news:O9KdnXjXUaIER9_eRVn-iA@xxxxxxxxxxxxx
>> What kind of authentication are you using with your SQL server?
>> Integrated authentication or SQL-server authentication. In other words
>> where is your SQL login defined - at the SQL Server level or as a
>> Domain/active Directory account. If you're trying with Integrated
>> Authentication it will probably not work because you don't have access to
>> the domain database from the Internet.
>>
>> Virgil
>>
>>
>>
>>
>> "beto @ southworks" <beto@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:eEor1VQyFHA.2132@xxxxxxxxxxxxxxxxxxxxxxx
>>> Hi! I need to publish a SQL2000 server to Inet through an ISA Server
>>> 2004. Have tried everything I've found and I cannot get it working. This
>>> is my configuration.
>>>
>>> * My SQL Server Machine is a SecureNAT client.
>>> * I've run the server publishing wizard on the ISA Server machine and
>>> published the SQL Server on it's default port (1433).
>>> * SQL Server instance name IS NOT the Default instance name (does it
>>> matters?)
>>> * On the client machine (inet) I create an Alias using the ISA Server
>>> Public IP Address as Server Name, so the client does not have to resolve
>>> the connection port.
>>>
>>> When I try to register the SQL instance on the client machine I get:
>>> "SQL Server registration failed because of the connection failure
>>> displayed below. Do you wish to Register anyway?
>>> SQL Server does not exist or access denied.
>>> ConnectionOpen (Connect())"
>>>
>>> If I run a trace on the ISA Server to watch incoming connections I can
>>> see that the incoming from the external IP address connection is not
>>> being denied, but nothing happens.
>>> I get the same if I try to Register the SQL Instance from a host in the
>>> LAN looping through the ISA Server for testing purposes.
>>>
>>>
>>> Is there a way to troubleshoot this Registration process? I can´t see
>>> where it's being stopped or what is missing.
>>> Thanks a Lot!
>>>
>>> Beto.
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Merge replication in SQL Server
    ... However, port 443 is for https, did you want your SQL ... Configuring an instance of SQL Server to use a static port ... you can script out replication jobs by right clicking on a publication ...
    (microsoft.public.sqlserver.replication)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Will anything change when I install SQL 2008 on the laptop? ... Queries to the Data Engine must go to the port that SQL Server is ... More info: How to: Configure a Windows Firewall for Database Engine Access ...
    (microsoft.public.sqlserver.connect)
  • Re: hack using xp_cmdshell
    ... > Fortunately 14 years of SQL experience, and a little common sense, would ... > should run it on a different port and just have my developers connect to ... Tibor Karaszi, SQL Server MVP ... >> install SQL Server in Windows Only mode and then Switch down to Mixed ...
    (microsoft.public.sqlserver.server)
  • Re: Getting an absolutely up to date version of MSDE
    ... The real reason for updating is that I have online SQL Server ... >> Enterprise Manager connection does not now work (has worked splendidly ... >dynamically assigned port (actually letting the remote MDAC client stack be ...
    (microsoft.public.sqlserver.msde)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... I agree with Arnie that you shall not encounter conflicts or port confusion ... Certainly you could install both SQL 2005 and 2000 as named instance. ... TCP Ports Needed for Communication to SQL Server Through a Firewall ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.setup)