Problem in Importing data from excel to sql server

I have excel file that has field named Purpose. Its max length is 400 character. I import this file to sql server database table. And also i change the purpose field in sql server database table with nvarchar 400. But when i run this job, it gave me error message:

Error at source for row number 1215. Errors encountereed so far in this task: 1.
Data for source column 18 ('Purpose') is too large for the specified buffer size.

What should i do so that i still can import the data from excel to sql server database?

Thanks for your help.I have far fewer problems when I take spreadsheets and put them in Access and then import them into sql server from access than I do just importing from excel.

Problem deploying reports

Hi,

I have an application that involves 3 components one of which is
Reports.
My system's configuration:
SQL 2000 - Default instance
SQL 2005 - Named instance (Instance1).

I provide the user with an option of selecting the SQL Server instance.
If the user chooses Instance1, then I need to deply the reports in SQL
2005.
The exceptions encountered during installation are logged in the Event
log.
When I do the installation for the in a machine, I always
get the following error in the event log:
Could not connect to the Report Server Database
http://<MachineName>/ReportingServices.asmx.
I tried giving the rs.exe options from commandline. I got an error like:

Error in DetermineReportUrlSecurity().

I don't have the exact error with me now.

Note that I do not get this error when I do the installation in a
machine where both default and named instances are SQL 2005.

Can anyone tell me why this happens?

Thanks,

Sandhya

Are you installing RS2005 on the same machine as RS 2000? If so you should be prompted to do a files only install, is that the case? If it is then I am not sure when you are seeing this error. During configuration? If you could provide the error message and a better description of exactly what you are doing, perhaps I can offer some help.|||

Hi,

I am deploying my reports during the time of installation of my application i.e., throwugh an msi. I deploy the reports using rs.exe command and any error encountered would be logged in event log.

While installing SQL 2005. I selected the option 'Install and configure' for Reporting Services component. I also verified that I am able to browse to the Reports page. So there is no problem with the configuration. Someone had a similar problem which I saw in another forum. There a solution was given as to disable the firewall/create exceptions for report server. But in my system the firewall is already disabled.

I am deploying my reports from the installer by giving the rs.exe command wherein I get the following error:
Could not connect to the Report Server Database
http://<MachineName>/ReportingServices.asmx.

I tried giving the rs.exe from the command line with -t parameter to trace the error.
Folowing is the exact error that I am getting:
Microsoft.ReportingServices.ScriptHost.ScriptHost.DetermineServerUrlSecuri
ty()
at Microsoft.ReportingServices.ScriptHost.ScriptHost.InstanceMain()
at Microsoft.ReportingServices.BaseCmdLine.CommandLineMain(String[] args,
BaseCmdLine instance)

Why do I get this error?

Thanks,
Sandhya

|||

You need to connect to http://machinename/ReportServer/ReportingServices.asmx.

I hope this help.s

|||Hi,
I am connecting to http://machinename/ReportServer/ReportingServices.asmx.
Still I get the error. Any clues as to why I face this problem?
Thanks,
Sandhya|||According to the error the report server does not exist. Does the report server come up if you browse to http://machinename/reportserver? Does http://machinename/reports work?|||

Hi,

For Yukon, the default configuration for the Report page would be:

Default instance - http://<machinename>/reports

Named Instance - http://<machinename>/reports$<InstanceName>

In my case, I have Yukon in the named instance(Instance1). Hence I need to connect to http://<machinename>/reports$Instance1 and I verified that I am able to browse to this page. I get the Reports homepage.

When I browse to http://machinename/reportserver$Instance1, I get the following displayed in the page:

chnshl13423/ReportServer$Instance1 - /

---

---

Microsoft SQL Server Reporting Services Version 9.00.1399.00

So what might be the problem?

Thanks,

Sandhya

|||you should pass in -s http://machinename/reportserver$Instance1 to rs.exe.|||

Hi,

I am already giving the following:

rs.exe -i "C:\Pr\DCMReports For Yukon\DeploymentScript\PublishDCMReports.rss" -s "http://chnshl13423/reportserver$Instance1" -v parentFolder="DCM Reports For Yukon" -v reportLocation="C:\Pr\DCMReports For Yukon\DeploymentScript\PublishDCMReports.rss" -v serverName="chnshl13423\Instance1" -v databaseName="DCMSolution"

Thanks,

Sandhya

|||Any suggestions?|||

Hmm, It looks like you are doing everything that you should be. All the script host does at this point is call the soap method ListSecureMethods, using the ReportService2005.asmx endpoint. Your command looks correct and the server is up and running. I really don't know what would be causing this error.

The only thing I can think of is if the user you are running rs.exe as can not be authenticated with RS or RS is setup to use forms or basic auth. You could try using a different user, or if you are using basic auth, pass in the username and password options.

Problem deploying reports

Hi,

I have an application that involves 3 components one of which is
Reports.
My system's configuration:
SQL 2000 - Default instance
SQL 2005 - Named instance (Instance1).

I provide the user with an option of selecting the SQL Server instance.
If the user chooses Instance1, then I need to deply the reports in SQL
2005.
The exceptions encountered during installation are logged in the Event
log.
When I do the installation for the in a machine, I always
get the following error in the event log:
Could not connect to the Report Server Database
http://<MachineName>/ReportingServices.asmx.
I tried giving the rs.exe options from commandline. I got an error like:

Error in DetermineReportUrlSecurity().

I don't have the exact error with me now.

Note that I do not get this error when I do the installation in a
machine where both default and named instances are SQL 2005.

Can anyone tell me why this happens?

Thanks,

Sandhya

Are you installing RS2005 on the same machine as RS 2000? If so you should be prompted to do a files only install, is that the case? If it is then I am not sure when you are seeing this error. During configuration? If you could provide the error message and a better description of exactly what you are doing, perhaps I can offer some help.|||

Hi,

I am deploying my reports during the time of installation of my application i.e., throwugh an msi. I deploy the reports using rs.exe command and any error encountered would be logged in event log.

While installing SQL 2005. I selected the option 'Install and configure' for Reporting Services component. I also verified that I am able to browse to the Reports page. So there is no problem with the configuration. Someone had a similar problem which I saw in another forum. There a solution was given as to disable the firewall/create exceptions for report server. But in my system the firewall is already disabled.

I am deploying my reports from the installer by giving the rs.exe command wherein I get the following error:
Could not connect to the Report Server Database
http://<MachineName>/ReportingServices.asmx.

I tried giving the rs.exe from the command line with -t parameter to trace the error.
Folowing is the exact error that I am getting:
Microsoft.ReportingServices.ScriptHost.ScriptHost.DetermineServerUrlSecuri
ty()
at Microsoft.ReportingServices.ScriptHost.ScriptHost.InstanceMain()
at Microsoft.ReportingServices.BaseCmdLine.CommandLineMain(String[] args,
BaseCmdLine instance)

Why do I get this error?

Thanks,
Sandhya

|||

You need to connect to http://machinename/ReportServer/ReportingServices.asmx.

I hope this help.s

|||Hi,
I am connecting to http://machinename/ReportServer/ReportingServices.asmx.
Still I get the error. Any clues as to why I face this problem?
Thanks,
Sandhya|||According to the error the report server does not exist. Does the report server come up if you browse to http://machinename/reportserver? Does http://machinename/reports work?|||

Hi,

For Yukon, the default configuration for the Report page would be:

Default instance - http://<machinename>/reports

Named Instance - http://<machinename>/reports$<InstanceName>

In my case, I have Yukon in the named instance(Instance1). Hence I need to connect to http://<machinename>/reports$Instance1 and I verified that I am able to browse to this page. I get the Reports homepage.

When I browse to http://machinename/reportserver$Instance1, I get the following displayed in the page:

chnshl13423/ReportServer$Instance1 - /

---

---

Microsoft SQL Server Reporting Services Version 9.00.1399.00

So what might be the problem?

Thanks,

Sandhya

|||you should pass in -s http://machinename/reportserver$Instance1 to rs.exe.|||

Hi,

I am already giving the following:

rs.exe -i "C:\Pr\DCMReports For Yukon\DeploymentScript\PublishDCMReports.rss" -s "http://chnshl13423/reportserver$Instance1" -v parentFolder="DCM Reports For Yukon" -v reportLocation="C:\Pr\DCMReports For Yukon\DeploymentScript\PublishDCMReports.rss" -v serverName="chnshl13423\Instance1" -v databaseName="DCMSolution"

Thanks,

Sandhya

|||Any suggestions?|||

Hmm, It looks like you are doing everything that you should be. All the script host does at this point is call the soap method ListSecureMethods, using the ReportService2005.asmx endpoint. Your command looks correct and the server is up and running. I really don't know what would be causing this error.

The only thing I can think of is if the user you are running rs.exe as can not be authenticated with RS or RS is setup to use forms or basic auth. You could try using a different user, or if you are using basic auth, pass in the username and password options.

problem creating view on table from linked server DB using IP addr

Hello,
I can create a view on a table from a named linked server database.
select * from server1.RemoteDB.dbo.Table1
But I am having a problem creating a view on a table from a non-named linked
server that is just using the IP address of the server. Example:
Select * from [56.19.175.167].RemoteDB.dbo.Table1
When I run the view (in design mode) the square brackets get moved around
like this:
Select * from [56].[19.175.167.RemoteDB].dbo.Table1
The error message says it cannot find the server [56] and to re-run
sp_addlinkedserver. Could someone share the correct syntax for using the I
P
address as the server name?
Thanks,
Rich> When I run the view (in design mode)
STOP DOING THAT!
Create your view in Query Analyzer, and run the view in Query Analyzer.
Enterprise Mangler's tool for this is quite crippled and this is not the
only problem you'll encounter. Try using a CASE expression in your query,
for one.
A|||Just a few more details:
I am already aliasing the remote table
Select * from [56.19.175.167].RemoteDB.dbo.Table1 tblx
and
for the linked server that I can create a view on - that server resides on
the same server computer as the server I am working from.
The server I am having a problem with is a remote server which resides 3000
miles away from my local server. Does this make a difference?
"Rich" wrote:

> Hello,
> I can create a view on a table from a named linked server database.
> select * from server1.RemoteDB.dbo.Table1
> But I am having a problem creating a view on a table from a non-named link
ed
> server that is just using the IP address of the server. Example:
> Select * from [56.19.175.167].RemoteDB.dbo.Table1
> When I run the view (in design mode) the square brackets get moved around
> like this:
> Select * from [56].[19.175.167.RemoteDB].dbo.Table1
> The error message says it cannot find the server [56] and to re-run
> sp_addlinkedserver. Could someone share the correct syntax for using the
IP
> address as the server name?
> Thanks,
> Rich
>|||> Select * from [56.19.175.167].RemoteDB.dbo.Table1 tblx
Another thing to reduce the complexity here, of having IP addresses
hard-coded into your query, is to create a simply-named alias using Client
Network Utility, and then refer to the alias instead of the IP address. Not
that this makes it okay to use the view designer, but I think it is a better
approach overall. In addition to alleviating problems with 4-dot naming, it
also makes it much easier to update the system should that IP address
change - you just change the alias definition instead of all the places you
manually referred to it in code.

Problem creating a stored procedure with the Execute as clause.

I have a server with a login named NewCreator. This login is assigned only to the dbcreator server role.

I want this login to be able to execute the stored procedure, sp_helplogins.

The sp_helplogins documentation says the caller of this proecedure needs securityadmin permissions.

I know that I should be able to create a login, say 'SecAdmin' and assign that login to the security admin server role, and then grant NewCreator Impersonate permission on SecAdmin.

What I don't like about this technique is that NewCreator can get on the server and gain complete authority over security when I really only want him to be able to execute sp_helplogins.

Therefore, what I am attempting is the following:

I create the login, SecAdmin, and assign it to the securityadmin server role.

Then I right click sp_helplogins and select 'Modify'.

I change the Alter to Create, change the name of the procedure to sp_myspecialone, and then add the sql statement "With Execute as 'SecAdmin'.

I execute the above and the new stored procedure is created. I then grant Execute on sp_myspecialone to NewCreator.

Everything works fine so far. But when I login as NewCreator and execute sp_myspecialone, I get an error in line 73 - no permission.

Line 73 is blank, but the next few lines read:

if(not(is_srvrolemember('securityadmin')= 1))

begin

raiserror(15247,-1,-1)

select @.RetCode = 1

goto label_86return

end

What am I doing wrong? Is their a better alternative to accomplish what I want to do?

Your assistance would be greatly appreciated.

It looks like when executing "AS SecAdmin" you are only executing the proc in the context of the user not the login. Therefore, it won't resolve the server permissions of the login SecAdmin but just the database permissions of the user SecAdmin.

In your scenario check:

execute as login = 'SecAdmin'

SELECT is_srvrolemember('securityadmin')

execute as user = 'SecAdmin'

SELECT is_srvrolemember('securityadmin')

I'm afraid i don't have any alternatives at this time but i'll have a think.

Hope this helps for now.

|||

Actually, is it possible to change the proc to be something along the lines of:

CREATE PROC blah
AS

EXECUTE AS LOGIN = 'SecAdmin'

EXEC sp_helplogins

Problem creating a stored procedure with the Execute as clause.

I have a server with a login named NewCreator. This login is assigned only to the dbcreator server role.

I want this login to be able to execute the stored procedure, sp_helplogins.

The sp_helplogins documentation says the caller of this proecedure needs securityadmin permissions.

I know that I should be able to create a login, say 'SecAdmin' and assign that login to the security admin server role, and then grant NewCreator Impersonate permission on SecAdmin.

What I don't like about this technique is that NewCreator can get on the server and gain complete authority over security when I really only want him to be able to execute sp_helplogins.

Therefore, what I am attempting is the following:

I create the login, SecAdmin, and assign it to the securityadmin server role.

Then I right click sp_helplogins and select 'Modify'.

I change the Alter to Create, change the name of the procedure to sp_myspecialone, and then add the sql statement "With Execute as 'SecAdmin'.

I execute the above and the new stored procedure is created. I then grant Execute on sp_myspecialone to NewCreator.

Everything works fine so far. But when I login as NewCreator and execute sp_myspecialone, I get an error in line 73 - no permission.

Line 73 is blank, but the next few lines read:

if (not (is_srvrolemember('securityadmin') = 1))

begin

raiserror(15247,-1,-1)

select @.RetCode = 1

goto label_86return

end

What am I doing wrong? Is their a better alternative to accomplish what I want to do?

Your assistance would be greatly appreciated.

It looks like when executing "AS SecAdmin" you are only executing the proc in the context of the user not the login. Therefore, it won't resolve the server permissions of the login SecAdmin but just the database permissions of the user SecAdmin.

In your scenario check:

execute as login = 'SecAdmin'

SELECT is_srvrolemember('securityadmin')

execute as user = 'SecAdmin'

SELECT is_srvrolemember('securityadmin')

I'm afraid i don't have any alternatives at this time but i'll have a think.

Hope this helps for now.

|||

Actually, is it possible to change the proc to be something along the lines of:

CREATE PROC blah
AS

EXECUTE AS LOGIN = 'SecAdmin'

EXEC sp_helplogins

problem connexion to db

i m using an sqlserver base in creating dynamic site with asp.
i m using automatic asp generator code named aspmaker.

in aspmaker i can connect to the db whitout problems and so generate html pages . the problem is that when i ry navigating in my new site i get this message :

error type :
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]connexion fail of user
'AWATEF\IUSR_AWATEF'.
/inbmi/fournisseurlist.asp, line 114

navigator type:
Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Page :
GET /inbmi/fournisseurlist.aspCheck the permissions for the user 'AWATEF\IUSR_AWATEF', check your ODBC configuration, also check the ASP forums.

Problem connecting to SS2K5 named instance using client tools

Hi,

The problem I have is this:

I have installed SQL Server 2005 Enterprise Edition on a W2K3 server that already has a SQL Server 2000 default instance installed. The installation appears to be a success. The problem is that having installed the client tools, and trying to connect, I get the following error message in a dialog:

"Cannot connect server SERVERNAME\INSTANCENAME
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)(Microsoft SQL Server)"

The funny thing is that I can connect to the SQL Server 2000 default instance that is on that server.
So it's obviously not a connection problem per se at my end i.e. bad dns etc which might stop me resolving the server name.

Googling for this error text gives the following advice on various web sites:

1. Check that the remote server allows connections.

It does, as other colleagues in my team have successfully installed the tools and can connect with no problems.

2. Check that the SQL Browser service is running.

It is, as without this running, my colleagues would not be able to connect either.

3. Open SQL Server Configuration Manager. Select "SQL Server 2005 Network Configuration | Protocols for MSSQLSERVER" then enable the protocols you need.

The required protocol (TCP/IP) is enabled. Named pipes is also enabled, although I don't think that we're using that. And shared memory is also enabled by default.

4. Open the firewall and add exceptions for sqlbrowser.exe or UDP port
1434

There is no firewall running at either end of the connection and as mentioned I can connect to the SS2K default instance.

5. Make sure that the server machine is reachable.

I can connect to the SS2K default instance so it must be reachable. I can't see that I would need to change any configuration settings as my colleagues are using exactly the same default settings for their connections and they work fine.

The only thing that I have done differently is that I originally installed the client tools using someone else's privileged account as I didn't have admin rights on my box. The client tools didn't work, so I got admin rights to my box, uninstalled the client tools and then reinstalled them using my account. Still no luck. Not sure if something is still hanging around after the uninstallation that would cause me a problem.

To help, I've also filled out the following questionnaire:

[1] Client side:

> What is the connection string in you app or DSN?

There isn't one. I'm trying to connect from the SQL Server Management Studio | 'Connect to Server' dialog.

> If client fails to connect, what is the client error messages?

"Cannot connect server Y\Z
An error has occurred while establishing a connection to the server. When connecting to SQL Server
2005, this failure may be caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)(Microsoft SQL Server)"

Is the client remote or local to the SQL server machine? Remote

Can you ping your server? YES

Can you telnet to your SQL Server? YES

What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other (please specify] N/A
What is your client application? SQL Management Studio
Is your client computer in the same domain as the Server computer? Different domains
What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes]. All 3 protocols are enabled
Do you have aliases configured that match the server name portion of your connection string? No
Do you select force encryption on server and/or client? No

[2] Server side:

What is the MS SQL version? SQL Server 2005
What is the SKU of MS SQL? Enterprise
What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. All 3
Does the server start successfully? YES. Other people can connect to the same instance.
If SQL Server is a named instance, is the SQL browser enabled? YES
What is the account that the SQL Server is running under? Domain Account
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? N/A. Firewall not running.
Do you make firewall exception for SQL Browser UDP port 1434? N/A. Firewall not running.
What tool or Application are you using to connect to SQL Server SQL Server Management Studio

[3] Platform:

What is the OS version? Windows 2003 (Server side), Windows XP Pro Version 2002 SP 2
Do you have third party antivirus, anti-spareware software installed? Symantec AntiVirus

[4] Misc:

If you have certificate configuration issue: N/A

Has anybody else come across this problem, as I've run out of ideas.

Many thanks,

Hi,

I've fixed the problem.
One of my colleagues who can log onto the SS2005 named instance from his workplace came to my workplace today and found that he also couldn't connect from there. That ruled out my installation. So we played with SQLCMD trying to connect and found that we could if we specified the TCP port (1776). So then it was just a question of working out
what the syntax was to specify the port in the Connection dialog. Turns out that server-name\,1776 works and allows us to connect.

Thanks.

Problem Connecting to SQL Server Non-default Named Instance

I am having a problem connecting to a SQL Server named [non-default] instanc
e
using the Server "alias" name. Connecting, through Enterprise Manager with
the IP\instance name or server name\instance name works fine. Connecting to
the default instance using the alias also works fine.
I have confirmed that when connecting to the non-default instance, using
either the IP or server name, the connecting is made through the correct [no
t
1433] port.
We have a developer network, with some workstations being able to use the
"alias"\instance name, and other workstations not, when conencting to the
non-default instance. So, there is something particular to some workstations
that is preventing access to non-default SQL instances using the alias.
The developer workstations are all built identically, so could it be an XP
service pack that may only have been applied to some workstations, that coul
d
be causing the problem? Or is there another reason.
Thanks!
dcnDeveloper.Canada.Net wrote:
> I am having a problem connecting to a SQL Server named [non-default]
> instance using the Server "alias" name. Connecting, through
> Enterprise Manager with the IP\instance name or server name\instance
> name works fine. Connecting to the default instance using the alias
> also works fine.
> I have confirmed that when connecting to the non-default instance,
> using either the IP or server name, the connecting is made through
> the correct [not 1433] port.
> We have a developer network, with some workstations being able to use
> the "alias"\instance name, and other workstations not, when
> conencting to the non-default instance. So, there is something
> particular to some workstations that is preventing access to
> non-default SQL instances using the alias.
> The developer workstations are all built identically, so could it be
> an XP service pack that may only have been applied to some
> workstations, that could be causing the problem? Or is there another
> reason.
> Thanks!
> dcn
SP2 does have some issues connecting to MSDE. IUf you define an alias,
you use just the alias name to connect, not alias\instance.
Are you defining the alias in the SQL Server Client Network Utility?
David Gugick
Imceda Software
www.imceda.com|||I must use the instance name, as we have about 10 instances on the same
server, all using different ports.
I have not defined the alias in the client utility, although I know this
works. It is just puzzling why I cannot use the alias\instance name when
connecting to the database, whereas other computers can. There is somthing
different between half the PCs in our development group, and the
rest...although not sure what.
We will likely not spin our wheels any further on this, and just live with
an alias setting in the client utility as a workaround for the affected PCs.
Thanks!
dcn
"David Gugick" wrote:

> Developer.Canada.Net wrote:
> SP2 does have some issues connecting to MSDE. IUf you define an alias,
> you use just the alias name to connect, not alias\instance.
> Are you defining the alias in the SQL Server Client Network Utility?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||I'm sure they were all built the same. That doesn't really mean they are
necessarily the same now if they are developer machines though (unless your
developers are MUCH different than any I ever met). Have you tried having
them upgrade the MDAC on the machines that don'e work just for kicks and
grins? You can find the latest at www.microsoft.com/data
"Developer.Canada.Net" <Developer.Canada.Net@.discussions.microsoft.com>
wrote in message news:7974ACEC-FE12-4250-B122-8865CFE44C10@.microsoft.com...
> I must use the instance name, as we have about 10 instances on the same
> server, all using different ports.
> I have not defined the alias in the client utility, although I know this
> works. It is just puzzling why I cannot use the alias\instance name when
> connecting to the database, whereas other computers can. There is somthing
> different between half the PCs in our development group, and the
> rest...although not sure what.
> We will likely not spin our wheels any further on this, and just live with
> an alias setting in the client utility as a workaround for the affected
PCs.
> Thanks!
> dcn
>
> "David Gugick" wrote:
>|||Developer.Canada.Net wrote:
> I must use the instance name, as we have about 10 instances on the
> same server, all using different ports.
> I have not defined the alias in the client utility, although I know
> this works. It is just puzzling why I cannot use the alias\instance
> name when connecting to the database, whereas other computers can.
> There is somthing different between half the PCs in our development
> group, and the rest...although not sure what.
> We will likely not spin our wheels any further on this, and just live
> with an alias setting in the client utility as a workaround for the
> affected PCs. Thanks!
> dcn
>
> "David Gugick" wrote:
>
Try turning off the Windows Firewall and see what happens.
David Gugick
Imceda Software
www.imceda.com|||On Thu, 10 Mar 2005 15:56:17 -0500, "David Gugick"
<davidg-nospam@.imceda.com> wrote:
in <#6n6bObJFHA.3428@.tk2msftngp13.phx.gbl>

>SP2 does have some issues connecting to MSDE. IUf you define an alias,
>you use just the alias name to connect, not alias\instance.
As far as I can tell the only issues have to do with implementing
the ridiculous excuse for a firewall that SP2 provides. SP2 has
no issues connecting to MSDE if a real firewall like KERIO is
used. My apologies, but this is deliberately meant to sound
inflammatory.
Stefan Berglund|||Stefan Berglund wrote:
> On Thu, 10 Mar 2005 15:56:17 -0500, "David Gugick"
> As far as I can tell the only issues have to do with implementing
> the ridiculous excuse for a firewall that SP2 provides. SP2 has
> no issues connecting to MSDE if a real firewall like KERIO is
> used. My apologies, but this is deliberately meant to sound
> inflammatory.
I assume you mean inflammatory to Microsoft, no?
David G.|||On Sat, 12 Mar 2005 12:51:21 -0500, "David Gugick"
<davidg-nospam@.imceda.com> wrote:
in <#qyVYwyJFHA.336@.TK2MSFTNGP09.phx.gbl>

>Stefan Berglund wrote:
>I assume you mean inflammatory to Microsoft, no?
Yes, of course.
Stefan Berglund|||I agree it's not a full-featured firewall, but is much improved in SP2
and as I understand it will examine incoming and outgoing packets to
some degree. For end users who until recently probably didn't keep their
virus definitions up to date, the firewall can help. Most end-users who
are on some sort of broadband have their PCs hooked directly to the
cable/DSL modem, further exposing them to attack. For businesses, this
is generally not a problem, but it does cause headaches for many
end-users, headaches aside.
David G.|||On Sun, 13 Mar 2005 21:29:57 -0500, "David Gugick"
<davidg-nospam@.imceda.com> wrote:
in <OueRz2DKFHA.732@.TK2MSFTNGP12.phx.gbl>

>I agree it's not a full-featured firewall, but is much improved in SP2
>and as I understand it will examine incoming and outgoing packets to
>some degree. For end users who until recently probably didn't keep their
>virus definitions up to date, the firewall can help. Most end-users who
>are on some sort of broadband have their PCs hooked directly to the
>cable/DSL modem, further exposing them to attack. For businesses, this
>is generally not a problem, but it does cause headaches for many
>end-users, headaches aside.
I can only suppose that by improved you mean turned on by
default. I was not aware that it did any stateful inspection of
packets or that it even looked at outgoing traffic. Obviously
the ~Windows firewall~ is better than nothing, but I prefer and
insist that all my clients operate from behind a hardware
firewall in addition to having Kerio, AVG, Ad-Aware, and Spybot
S&D on every box. I run all that even on my server which also
runs SQL and it goes without saying that they all get along
together fabulously.
Kerio can be a bit overwhelming for the novice, but once it's set
up it's a breeze. I've even used it to reclaim a client's laptop
that had been taken over by the Dark Angel trojan. This thing
was so insidious that on every reboot it took out ZoneAlarm and
Norton. Norton was able to detect its attempts at phoning home
but wasn't able to cope otherwise. It was at this point that I
removed Norton and ZoneAlarm from my boxes and went with tools
that are comparatively more lightweight and that do the job
expected of them.
Stefan Berglund