Connecting to Remote SQL

I attempting to connect an XP Proffessional Client to a Remote SQL. The XP
machine is on a SBS 2000 network.

I have read previous messages and have successfully
Defined a Protocol
Created a Rule that deploys the protocol
Created an Outward bound Packet Filter.

The forth step as I understand is too
========
Use the SQL Client Network Utility to define an Alias
for the remote server, making sure you specify TCP/IP as the connection
type, and specify port 1433, don't leave it on dynamic.
========

The SBS server does not have SQL installed, so there is no utility?
The question(s) are
Is there another way of doing the above?
Do I have to do it at all, if there is no SQL installed
or
Do I have to install SQL to get past this point?

TIA

__Allan

seaverr
Tue Aug 12 01:33:14 CDT 2003

Dear Allan,

Thank you for your posting.

According to your post, you wonder whether it's possible to find
replacement for SQL Client Network Utility.

If I have misunderstood your concern please don't hesitate to let me know.

1. Client Network utility tool can be ignored when it's only to connect to
remote Microsoft SQL Server 2000, users can specify only the network name
of the server on which SQL Server is running, and optionally the name of
the instance of SQL Server.

2. However, to finish all the mentioned steps such as alias specification
and to create an outward bound packet filter, Client Network utility is
necessary. This tool is used to manage the client Net-Libraries, to define
server alias names, and to set the default options used by DB-Library
applications.

In some cases, an instance of SQL Server may be configured to listen on
alternate network addresses. If this is done, client applications
connecting to that instance must explicitly specify the alternate address.
While applications could specify the alternate addresses on each connection
request, it is easier to use the Client Network utility to set up an alias
specifying the alternate addresses. Applications can then specify the alias
name in place of the server network name in their connection requests.

Therefore you need to install SQL Server 2000, included in SBS 2000
Package, on your SBS 2000 Server.

If you have any further concern regarding SBS 2000 Server's SQL 2000
installation, please feel free to let me know.

Sincerely,

Seaver Ren

Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights
Get Secure! - www.microsoft.com/security

Steve
Tue Aug 12 04:32:11 CDT 2003

Allan Wissing wrote:

> I attempting to connect an XP Proffessional Client to a Remote SQL.
> The XP machine is on a SBS 2000 network.
>
> I have read previous messages and have successfully
> Defined a Protocol
> Created a Rule that deploys the protocol
> Created an Outward bound Packet Filter.
>
> The forth step as I understand is too
> ========
> Use the SQL Client Network Utility to define an Alias
> for the remote server, making sure you specify TCP/IP as the
> connection type, and specify port 1433, don't leave it on dynamic.
> ========
>
> The SBS server does not have SQL installed, so there is no utility?
> The question(s) are
> Is there another way of doing the above?
> Do I have to do it at all, if there is no SQL installed
> or
> Do I have to install SQL to get past this point?
>
> TIA
>
> __Allan

Firstly, Packet Filters are only required if the server itself needs to
be able to get out - not the case here.

Now to answer your questions:

The server doesn't need the SQL Client Network Utility - the Alias
needs to be defined on the client machine being used to access SQL - in
your case, your XP Pro machine. If you're going to be working with a
SQL Server, you should have the SQL Client Tools installed on that
anyway, and the Client Network Utility is one of those tools. You can
install them (if you haven't already) from the SBS CD2 SQL folder (I
think it's CD2!).

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Steve
Wed Aug 13 03:37:30 CDT 2003

Allan Wissing wrote:

> On Steve advise I installed the Client Utilities onto the XP Computer.
>
> I then set up an Alias - but alas my problem was not resolved.
>
> Question(s)
> When setting up the Alias (Client Utility), does the name have to be
> the name of the database or can it be any name I make up?
>
> Seaver said I had to install SQL on the SBS 2000 Server. Steve said
> - no need. Seaver where you thinking I need to do this soley for
> the purpose of getting hold of the Client Utilities, or is there
> another reason?
>
>
> __Allan

The Alias can be any name you wish (that's why it's called an *alias*),
but you must define it to point to the SQL Server you want to talk to,
either by DNS name or IP.

The in the SQL Client applications like QA, you specify the Alias name
(as chosen by you) as the server you want to connect to.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Allan
Fri Aug 15 18:28:16 CDT 2003

OK - I believe I have done all the above, but have not succeeded in
connecting.

Just a bit of history, which I did not advise to start with.
This is VB6 application connecting to a SQL server on the internet.
Unfortunately I know very little about this app. It's installed on the SBS
2000 server and works fine. I'm trying to get the same app working on an XP
Client.

As I say I have done all that is suggested, but the XP still fails to
connect. I put a packet sniffer onto the same machine, and the second
packet returned this message.

===========
HTTP/1.1 407 Proxy Authentication Required ( The ISA Server requires
authorization to fulfill the request. Access to the Web Proxy service is
denied. )
Via:1.1 SBS-SERVER
Proxy-Authenticate: NTLM
Proxy-Authenticate: Kerberos
Proxy-Authenticate: Negotiate
Pragma: no-cache
Cache-Control: no-cache
Content-Type: text/html
Content-Length: 3815
===========

Advise to get past this point would be appreciated.

__Allan

Allan
Fri Aug 15 21:14:58 CDT 2003

David,

I can confirm that that is (and was) the setting. The work directly was not
included. The check box says "Send to Requested Web Server".

The XP Client makes the requests on port 8080. When the same application
executes on the SBS Server then the request go out the external NIC on port
80.

__Allan

David
Fri Aug 15 23:31:59 CDT 2003

Allan,

If it's sending to port 8080 then it sounds like it may be inheriting the
Proxy server settings from IE.. If you open IE on the client machine then go
to the Tools/Internet Options/Connections tab and then click on the LAN
Settings button.. Is the Automatically detect settings, Use automatic
configuration script, or Use a Proxy server for you LAN selected.. If so,
try unselecting all of them and closing IE. Does the application work then?
Also, is the firewall client installed/enabled on this machine?


Hope that helps,
David Copeland
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.


"Allan Wissing" <Allan.Wissing@ComputerCraft.co.nz> wrote in message
news:bhk439$q37$1@lust.ihug.co.nz...
> David,
>
> I can confirm that that is (and was) the setting. The work directly was
not
> included. The check box says "Send to Requested Web Server".
>
> The XP Client makes the requests on port 8080. When the same
application
> executes on the SBS Server then the request go out the external NIC on
port
> 80.
>
> __Allan
>
>
>

Allan
Tue Aug 19 18:43:36 CDT 2003

David,

I tried unselecting the "Use a Proxy Server..." and tried again. This time
the message did'nt get to first base. The application could not communicate
with the SBS server.

I have tried this application with the Client firewall enabled and disabled.

I really want some feed back on the error message I sent?

__Allan

Allan
Tue Aug 19 18:45:19 CDT 2003

OK - I believe I have done all the above, but have not succeeded in
connecting.

Just a bit of history, which I did not advise to start with.
This is VB6 application connecting to a SQL server on the internet.
Unfortunately I know very little about this app. It's installed on the SBS
2000 server and works fine. I'm trying to get the same app working on an XP
Client.

As I say I have done all that is suggested, but the XP still fails to
connect. I put a packet sniffer onto the same machine, and the second
packet returned this message.

===========
HTTP/1.1 407 Proxy Authentication Required ( The ISA Server requires
authorization to fulfill the request. Access to the Web Proxy service is
denied. )
Via:1.1 SBS-SERVER
Proxy-Authenticate: NTLM
Proxy-Authenticate: Kerberos
Proxy-Authenticate: Negotiate
Pragma: no-cache
Cache-Control: no-cache
Content-Type: text/html
Content-Length: 3815
===========

Advise to get past this point would be appreciated.

__Allan

Steve
Tue Aug 19 20:36:32 CDT 2003

Allan Wissing wrote:

> OK - I believe I have done all the above, but have not succeeded in
> connecting.
>
> Just a bit of history, which I did not advise to start with.
> This is VB6 application connecting to a SQL server on the internet.
> Unfortunately I know very little about this app. It's installed on
> the SBS 2000 server and works fine. I'm trying to get the same app
> working on an XP Client.
>
> As I say I have done all that is suggested, but the XP still fails to
> connect. I put a packet sniffer onto the same machine, and the second
> packet returned this message.
>
> ===========
> HTTP/1.1 407 Proxy Authentication Required ( The ISA Server requires
> authorization to fulfill the request. Access to the Web Proxy service
> is denied. )
> Via:1.1 SBS-SERVER
> Proxy-Authenticate: NTLM
> Proxy-Authenticate: Kerberos
> Proxy-Authenticate: Negotiate
> Pragma: no-cache
> Cache-Control: no-cache
> Content-Type: text/html
> Content-Length: 3815
> ===========
>
> Advise to get past this point would be appreciated.
>
> __Allan

Um. This application is connecting to SQL, yet it's sending web
requests?

You don't connect to SQL via web proxy...

There's more going on here.

Did you get the SQL Client tools working? Were you able to connect from
the workstation using Query Analyzer?

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.