RE: Windows Me/98 Client connecting to SQL W2k3

Thanks Donna,

These comments are very good recommendations.

Our problem is actually our website which is based on Data Access Pages.
Nothing particular, because to simplify the connection problem it can also be
tested by using the command OSQL.

On Wednesday I will be at the client site and I will check the MDAC and the
mapping of the share.

The network type is TCP/IP. I don't see the need to switch to Named Pipes,
since there is a VPN connection via port 80 and after establishing the
connection port 1433 is open. It has been proven that this works fine with XP
client.

SQL authentication we do not use. Only Windows Authentication.

The use of and UDL implies that all webpages must be changed and since we
have proven that it works fine on XP en 2000 we don't see the need.

If you have any comments on this before Wednesday, please let me know.

Many thanks so far and I'll come back on this issue.

Regards,
Jeroen


"Donna Lambert" wrote:

> Jeron,
>
> -What is the error you are seeing?
> -What version of MDAC are your client machines? If not 2.7 or later, you'll
> need to upgrade.
> -Are you using TCP or Named Pipes? Try both. Try using an alias, try
> creating a DSN, and try a UDL file. If you need help trying those, write
> back and I'll explain.
> -Does SQL authentication work but not Windows?
> -Does \\<win2003server\<anyshare> work from the ME\98 clients?
> If this fails, you have GENERAL authentication issues against the Win2003
> server, unrelated to SQL. And you'll need to address those, and we can talk
> more about that.
>
> If yes to that last question, can you connect to \\<win2003server>\ipc$?
> You would do this from a command prompt with this command:
> net use \\<servername\IPC$
>
> If that fails, it looks like a pipe issue.
>
> Donna
>
>
>
> "Jeroen" wrote:
>
> > We have a multiple clients that do have all cients of different clients. We
> > would like to connect to SQL Server running on a WIndows 2003 Server.
> >
> > We use Windows Authentication.
> >
> > According to Microsoft: "SQL Server clients running on Windows Millennium
> > Edition, Windows 98, or Windows 95 computers can connect to instances of SQL
> > Server 2000 on Windows NT or Windows 2000 computers using Windows
> > Authentication."
> >
> > I presume W2K3 is also possible using Windows Authentication, however it
> > does not work! We have created the same username password credentials at the
> > server. On XP machines we don't have problems.
> >
> > Could anybode advice on this?
.

Relevant Pages

  • Re: IIS 6.0 and 401.2 and 401.1 Errors
    ... > authentication -- client and server first negotiate authentication that ... > So, if you see repeated 401.2 for the same resource from the same client, ... > authenticated connection and instead RENEGOTIATING a new connection. ... > You can easily verify this by installing "Network Monitor" from Windows ...
    (microsoft.public.inetserver.iis)
  • Re: IIS 6.0 and 401.2 and 401.1 Errors
    ... authentication -- client and server first negotiate authentication that ... authenticated connection is considered "authenticated" and directly succeed. ... So, if you see repeated 401.2 for the same resource from the same client, it ... means that the client and server are NOT keeping their previously ...
    (microsoft.public.inetserver.iis)
  • Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched
    ... debug: ... connection lost. ... client on the same node as the server. ... [No surprise, as I allow, but don't use, host-based authentication.] ...
    (comp.os.vms)
  • Re: IIS 6.0 and 401.2 and 401.1 Errors
    ... > So, if you see repeated 401.2 for the same resource from the same client, it ... > authenticated connection and instead RENEGOTIATING a new connection. ... > this unnecessary renegotiation that is causing extra authentication trips ... > Server 2003 Add/Remove Programs, Windows Components and then watch the ...
    (microsoft.public.inetserver.iis)
  • dynamic client authentication
    ... The authentication mode was set to Integrated ... Windows authentication, so clients could be easily identified ... from the client - even if IWA is also checked. ... that all existing and future domain users can use ...
    (microsoft.public.inetserver.iis.security)
Quantcast