"Simon Lidberg [MSFT]" wrote:

> Are the clients connecting to the the server using integrated security? Are
> they connecting using the same network protocols?
>
> Simon
> This posting is provided "as is" with no warranties and confers no rights.
>
> "Craig Pickles" <reply2cr***@hotmail.com> wrote in message
> news:gt5e219f870d80c536sq2fcr5q54sou887@4ax.com...
> > On Wed, 2 Mar 2005 16:21:03 +0100, "Simon Lidberg [MSFT]"
> > <simon***@online.microsoft.com> wrote:
> >
> >>In order for Windows Authentication to work you need to be in the same
> >>domain or at least a trusted domain, is this true in your case?
> >>If they are not in the same domain then you have to revert to SQL
> >>authentication.
> >
> > I am gueessing that we are in a trusted domain by the fact that
> > windows XP clients can connect with no problems from the same office?
> > Or is it that this may not be the case?
> >
> > Cheers,
> > Craig
>
>
>

"Mike Allen" wrote:

> I'm having same issue.  My XP client can connect to SQL using TCP/IP while
> 2000 can only connect with Named Pipes.  Both client computers are in same
> domain as the SQL server.  Any ideas?
>
> "Simon Lidberg [MSFT]" wrote:
>
> > Are the clients connecting to the the server using integrated security? Are
> > they connecting using the same network protocols?
> >
> > Simon
> > This posting is provided "as is" with no warranties and confers no rights.
> >
> > "Craig Pickles" <reply2cr***@hotmail.com> wrote in message
> > news:gt5e219f870d80c536sq2fcr5q54sou887@4ax.com...
> > > On Wed, 2 Mar 2005 16:21:03 +0100, "Simon Lidberg [MSFT]"
> > > <simon***@online.microsoft.com> wrote:
> > >
> > >>In order for Windows Authentication to work you need to be in the same
> > >>domain or at least a trusted domain, is this true in your case?
> > >>If they are not in the same domain then you have to revert to SQL
> > >>authentication.
> > >
> > > I am gueessing that we are in a trusted domain by the fact that
> > > windows XP clients can connect with no problems from the same office?
> > > Or is it that this may not be the case?
> > >
> > > Cheers,
> > > Craig
> >
> >
> >

"Ron Martin" wrote:

> We are having tha same issue here, only with XP clients. I can get in on my
> XP desktop, another user can as well. Two other users using Windows XP,
> through a 2way trusted domain, cannot get to the SQL server. No one enters
> any names, just Windows service account.
>
>
> "Mike Allen" wrote:
>
> > I'm having same issue.  My XP client can connect to SQL using TCP/IP while
> > 2000 can only connect with Named Pipes.  Both client computers are in same
> > domain as the SQL server.  Any ideas?
> >
> > "Simon Lidberg [MSFT]" wrote:
> >
> > > Are the clients connecting to the the server using integrated security? Are
> > > they connecting using the same network protocols?
> > >
> > > Simon
> > > This posting is provided "as is" with no warranties and confers no rights.
> > >
> > > "Craig Pickles" <reply2cr***@hotmail.com> wrote in message
> > > news:gt5e219f870d80c536sq2fcr5q54sou887@4ax.com...
> > > > On Wed, 2 Mar 2005 16:21:03 +0100, "Simon Lidberg [MSFT]"
> > > > <simon***@online.microsoft.com> wrote:
> > > >
> > > >>In order for Windows Authentication to work you need to be in the same
> > > >>domain or at least a trusted domain, is this true in your case?
> > > >>If they are not in the same domain then you have to revert to SQL
> > > >>authentication.
> > > >
> > > > I am gueessing that we are in a trusted domain by the fact that
> > > > windows XP clients can connect with no problems from the same office?
> > > > Or is it that this may not be the case?
> > > >
> > > > Cheers,
> > > > Craig
> > >
> > >
> > >