I removed Named Pipes as that supposedly worked for someone in another post.

I also used the wizard to create the user and now it works as expected. I
am wondering if my ISP might have copied the users from another database when
setting it up. I will play with another server that has the same problem and
try to verify that it isn't anything to do with including Named Pipes with
TCP/IP.

I check on the exact error messages at that time.

"Sue Hoegemeier" wrote:

> No setup with SQL Server 2000 would do this - you don't
> have that level of granularity with security. At the network
> level, you can restrict IP addresses using IPSec filters but
> it wouldn't know what SQL login you are using.
> If you create new logins and can't login in with Query
> Analyzer or Enterprise Manager with these new logins,
> something else is going on.
> Please post the exact errors you get in Enterprise Manager
> and the steps you are using to create the logins.
>
> -Sue
>
> On Fri, 22 Sep 2006 16:42:01 -0700, Bill Rushmore
> <rushmwr.Nospam@yahoo.com> wrote:
>
> >I am working with an ISP to create 2005 web projects. They have set up a SQL
> >2000 database and given me the sa password. I can use sa to login and also
> >retreive the data for the web page using sa login.
> >
> >I tried creating an ASPNET user and also tried other user names so I don't
> >have to use sa. None of these will login. I tried connecting as a new user
> >using EM and that fails also for any user no matter what kind of permissions
> >I have tried to set up for the user.
> >
> >There was a problem ealier in that the firewall is set up to only recognize
> >my IP address to minimize the security issue of using the sa address.
> >
> >What kind of set up for SQL Server could allow sa but not any user I have
> >set up. Has anyone heard of firewall issues that only let sa login but not a
> >user with full permissions?
> >
>
>