When I run: osql -S 192.168.1.xxx -E -Q "sp_who2" it takes 47 seconds.
When I run: osql -S 192.168.1.xxx -U test -P password -Q "sp_who2" it takes
1 second.
The client is a web server that is in the DMZ connecting to a SQL 2000
server that is behind a firewall (NetScreen I believe) that only has TCP
port 1433 open and is doing NAT.
Any idea why Windows Authentication is so much slower than SQL
Authentication?
Re: Slow Windows Authentication vs Fast SQL Authentication ... added a host entry and everything is better now. ... The client is a web server that is in the DMZ connecting to a SQL 2000 ... Any idea why Windows Authentication is so much slower than SQL... (microsoft.public.sqlserver.connect)
Suggestions on hardening a web server ... I was looking for some advice on hardening a web server that will host ASP... pages and connect to a SQL Server 7 machine. ...firewall and the SQL box will be inside the firewall. ... (microsoft.public.inetserver.iis.security)
Re: New web server design with SQL back-end ... >>Is this setup more secure, in the sense that the SQL is on a separate box ... I would have placed the webserver outside of the firewall.... be enough at the front end of the web server?... Then using a Cisco Pix firewall to hide the SQL server behind. ... (microsoft.public.inetserver.iis)
Re: encrypt server data ... I guess you need to set 'vpn' for the sql and web server.... > to a SQL server that is on the internal LAN behind a firewall.... > that NAT and Ipsec have problems coexisting. ... (microsoft.public.inetserver.iis.security)
Re: where to put SQL Server ? ... > Unless you need to access the SQL Server from inside the firewall,... > put both the web server, and the SQL Server on the outside. ... put the web server in there. ... (microsoft.public.inetserver.iis.security)
