Re: Why do I have to enable File and Printer sharing to connect through the XP firewall?


"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx> wrote in
message news:EBDE3F42-3AF0-4A34-8EB3-C67C8D771FE9@xxxxxxxxxxxxxxxx
I assume Windows account since I'm not passing any user/pw information in
the connection string.

Then I assume you say something like "Integrated security = true", or
"trusted connection".

Yes, trusted connection.


The user(s) are already members of the domain. In this particular
instance, the user is me and I'm a domain/olap admin.

If you have logged on to the domain, then ti sould work fine over the
TCP/IP netlib.


BTW I looked for "cliconfig.exe" so I could check the client-side
configuration and didn't find it anywhere on my machines. What
package/app installs it?

It is cliconfg.exe, not cliconfig.exe. It is part of Windows.

My apologies, now I see it. I verified that TCP is before Named Pipes, and
even disabled Named Pipes but
I still can't connect using either my client app or Management Studio.
(error 26 : Error location server/instance specified) after easily locating
it with the browser.

In my client I even tried to force a protocol in the collection string using
tcp:<server/instance> and also Network Library=DBMSSOCN but with no luck.

I'm in the process of trying all these permutations on a clean(er) machine,
but in the mean time do yo have anymore suggestions?

Keith

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Keith" <keith@xxxxxxx> wrote in message
news:e7Bo6gM9HHA.4784@xxxxxxxxxxxxxxxxxxxxxxx

"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx> wrote
in message news:E402B142-E357-4124-A897-43E4D1747848@xxxxxxxxxxxxxxxx
I was not aware of that. I am using mixed mode authentication.

That is a server-side setting. What matters is how the client tries to
connect. IS the client connecting using a Windows account or using a SQL
Server account?

I assume Windows account since I'm not passing any user/pw information in
the connection string.

For Windows authentication, SQL Server need to enumerate the SIDs for
the account you pass with Windows (DC). The client should be able to
connect using TCP/IP Sockets, assuming the client user has logged into
the AD in the first place. If not, I assume that some AD validation is
attempted when the login to SQL Server is performed. (But I admit that
AD is far from my expertise...)

The user(s) are already members of the domain. In this particular
instance, the user is me and I'm a domain/olap admin.

BTW I looked for "cliconfig.exe" so I could check the client-side
configuration and didn't find it anywhere on my machines. What
package/app installs it?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"Keith" <keith@xxxxxxx> wrote in message
news:O782RHJ9HHA.2004@xxxxxxxxxxxxxxxxxxxxxxx

"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx>
wrote in message
news:4F9AE0A4-4F1B-462E-AD9B-3C840072AC33@xxxxxxxxxxxxxxxx
Perhaps the connection is made using Named Pipes? I'd use cliconfg.exe
on the client to verify that TCP/IP (sockets) is selected higher than
Named Pipes. Sockets shouldn't require anything else but the TCP port.
Unless you are trying a Windows logins, of course. Also, since you
specify the port in your connection string, you shouldn't need the SQL
Server browser service on the server (unless it is needed for other
purposes, of course).


Tibor,

Thanks for the reply. Could you clarify what you mean when you said
"Unless you are trying a Windows logins, of course." Are you saying
that Windows Authentication/Mixed Mode uses Named Pipes to communicate
with the domain controller? I was not aware of that. I am using mixed
mode authentication.

Thanks!

Keith




.

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: after installing KB011829 OWA is not working anymore
    ... Based on my research, after you install hotfix KB911829, I suggest we ... Profile WMI Provider to each client computer that is running Windows Vista ... If you are running the Premium Edition of Windows Small Business Server ...
    (microsoft.public.exchange.connectivity)
  • Re: DHCP Issues. Very strange
    ... I understand the issue to be: some client computers ... can not obtain IP from SBS server. ... it is most possible a client side issue of Windows ... since you have join it to SBS domain and the Windows XP SP2 ...
    (microsoft.public.windows.server.sbs)
  • Site-tosite VPN Issue
    ... Windows Server 2003 domain controller ... Mixture of PCs running Windows 2000 Profressional with SP3 and Windows XP ... the VPN to the Windows Server 2003 domain controller. ... 12.7MB file from the server to the client PC. ...
    (microsoft.public.windows.server.networking)