failed. I'm now trying to connect 50 machines across different countries.
However one machine does not work. We are using WIndows 98 instead of
Windows ME and it has a correct MDAC. But after using it 3 times it does not
It's very strange because it has worked and I saw it my self. I have re
"Jeroen" wrote:
> 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.
> > >
