Norton Internet Security & SQL Server

Hi,

Just installed Norton Internet Security on an XP workstation that also has
SQL Server on it.

I now find that I cannot access SQL Server and multiple messages are being
issued by NIS.

When I switch off the Firewall & Intrusion Detection I can access SQL
Server.

Does anyone know how to configure NIS so that I can use it alongside SQL
Server?

Thanks,

Mike.Uytkownik "Mike Stogden" <news@.uniquest.demon.co.uk> napisa w wiadomoci
news:bhaolh$i5i$1$8300dec7@.news.demon.co.uk...
> Hi,
> Just installed Norton Internet Security on an XP workstation that also has
> SQL Server on it.
> I now find that I cannot access SQL Server and multiple messages are being
> issued by NIS.
> When I switch off the Firewall & Intrusion Detection I can access SQL
> Server.
> Does anyone know how to configure NIS so that I can use it alongside SQL
> Server?
Hi, try this:

permit UDP OUT and IN protocol for

SQL Server Service Manager (sqlmangr.exe)
SQL Server Windows NT (sqlserver.exe)

And TCP OUT and IN protocol for

SQL Tracing Tool (profiler.exe)
ISQL (isqlw.exe)

from any adress:any port and this should work, and then try fit your rules
to be more security

best regards
Marcin D

NON DOMAIN AND DOMAIN CONNECTION

Hi all,

it happen to me a strange problem:

i have a mdb file (in Access 2K) with SQL Server 2K linked tables who
runs on a workstation which is on a different domain that the SQL
Server. It works.

If i create a mdb file from a workstation which is a the domain of the
SQL Server and then i run it a my non-domain workstation i have error
message:

Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection

But if i reattached my tables it works.

If someone have an idea...

PS: same ODBC on both machinesRavieR (principle@.caramail.com) writes:
> it happen to me a strange problem:
> i have a mdb file (in Access 2K) with SQL Server 2K linked tables who
> runs on a workstation which is on a different domain that the SQL
> Server. It works.
> If i create a mdb file from a workstation which is a the domain of the
> SQL Server and then i run it a my non-domain workstation i have error
> message:
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection

I'm nor sure that I followed the confiuguration exactly, but trusted
connections in workgroups is usually an iffy thing. For instance, at
home I have a non-domain workstation, on which I run a non-domain
virtual machine where I have the beta version of SQL 2005. From the
host machine I cannot conenct with trusted connection to SQL2005 on
the virtual machine, but not the other way round.

I think you need to be logged with the same username on both, and the
two users need to have the same password.

You may be better off with SQL authentication in this case.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

no trust connection

hi every one
i having i workstation with running in windows 98, now i want link it to the SQL server which are in windows 2000. when i try to link it the following error message " no associate trust SQL Server Connection". Can i know how to settle this problem
thanks in advanceare you trying to connect to the server using windows integrated
authentication? If so, make sure you're logged on to the domain in your
workstation before trying to connect to sql server. You might want to try to
connect using standard authentication (i.e using sa or another login) just
to verify you can connect to the server successfully. If this doesn't work,
make sure you can get to the server through tcp port 1433 (sql server port);
this can be tested using the following command:
telnet servername 1433
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...
> hi every one
> i having i workstation with running in windows 98, now i want link it to
the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem
> thanks in advance
>|||Hi,
Windows 98 will only support SQL server Authentication.
So while linking from SQL 2000, use SQL server Login credentials.
Thanks
Hari
MCDBA
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...
> hi every one
> i having i workstation with running in windows 98, now i want link it to
the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem
> thanks in advance
>|||when i using window intergrate authentication that can sucess link to the SQL server, but when i using the SQL authentication it fail at the end so what should i do now.
how to open the port 1433 '
thanks in advance|||is there a firewall between the client and the server? If they are in the
same network you don't have to open ports or anything.
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:D6026E6E-7EE4-4739-A280-9EA3BAD30032@.microsoft.com...
> when i using window intergrate authentication that can sucess link to the
SQL server, but when i using the SQL authentication it fail at the end so
what should i do now.
> how to open the port 1433 '?
> thanks in advance|||what error are you getting?
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:1256EDE4-FAA1-4A10-BF29-AAD182FBC94A@.microsoft.com...
> that r not any firewall install in that server, i just format and
reinstall the window for that server. so waht action i can take
> thanks in advance|||are you saying you get this error when trying to connect to sql server using
STANDARD authentication? It's weird, that error shows up when you can't
connect to sql but using integrated authentication.
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:85BAB5CE-BD59-4559-A7E1-1ED4A36596BE@.microsoft.com...
> it also show "no associate trust SQL Server Connection"

no trust connection

hi every one
i having i workstation with running in windows 98, now i want link it to the
SQL server which are in windows 2000. when i try to link it the following e
rror message " no associate trust SQL Server Connection". Can i know how to
settle this problem
thanks in advanceare you trying to connect to the server using windows integrated
authentication? If so, make sure you're logged on to the domain in your
workstation before trying to connect to sql server. You might want to try to
connect using standard authentication (i.e using sa or another login) just
to verify you can connect to the server successfully. If this doesn't work,
make sure you can get to the server through tcp port 1433 (sql server port);
this can be tested using the following command:
telnet servername 1433
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...

quote:

---

> hi every one
> i having i workstation with running in windows 98, now i want link it to

---

the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem

quote:

---

> thanks in advance
>

---

|||Hi,
Windows 98 will only support SQL server Authentication.
So while linking from SQL 2000, use SQL server Login credentials.
Thanks
Hari
MCDBA
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...

quote:

---

> hi every one
> i having i workstation with running in windows 98, now i want link it to

---

the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem

quote:

---

> thanks in advance
>

---

|||when i using window intergrate authentication that can sucess link to the SQ
L server, but when i using the SQL authentication it fail at the end so what
should i do now.
how to open the port 1433 '?
thanks in advance|||is there a firewall between the client and the server? If they are in the
same network you don't have to open ports or anything.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:D6026E6E-7EE4-4739-A280-9EA3BAD30032@.microsoft.com...

quote:

---

> when i using window intergrate authentication that can sucess link to the

---

SQL server, but when i using the SQL authentication it fail at the end so
what should i do now.

quote:

---

> how to open the port 1433 '?
> thanks in advance

---

|||that r not any firewall install in that server, i just format and reinstall
the window for that server. so waht action i can take
thanks in advance|||what error are you getting?
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:1256EDE4-FAA1-4A10-BF29-AAD182FBC94A@.microsoft.com...

quote:

---

> that r not any firewall install in that server, i just format and

---

reinstall the window for that server. so waht action i can take

quote:

---

> thanks in advance

---

|||it also show "no associate trust SQL Server Connection"|||are you saying you get this error when trying to connect to sql server using
STANDARD authentication? It's weird, that error shows up when you can't
connect to sql but using integrated authentication.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:85BAB5CE-BD59-4559-A7E1-1ED4A36596BE@.microsoft.com...

quote:

---

> it also show "no associate trust SQL Server Connection"

---

no such interface supported virus

I'm running an access 2000 front end with a slq server 2000 back end on a lo
cal network. All of the sudden one workstation couldn't connect to the serv
er. So after trying several things I think I've came to the correct conclus
ion. I believe that the ma
chine was infected by a virus that was missed by two different scanners. I
think its a hijack virus that takes control of sql when its trying to connec
t to the server using the server name. Its very odd and isn't detected by s
canners. A temp. fix is to
just use the ip of the server to connect and then it works. Also if I try a
nd ping the server by name it doesn't get a return however if I use the elon
gated full name of the server with domain its fine. Any ideas suggestions c
lues?Is the server running a Personal Firewall?
Are you connecting via TCP or Named Pipes?
What are you using for Name Resolution of the server?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.