J
Jon Robertson
I read the following in eWeek (November 24, 2003, "Building on
'Trust'", pg 10, 2nd paragraph that begins with "WIndows XP will also
get").
The article states that ICF will be enabled by default in WinXP SP2.
Where can I get official information from Microsoft regarding this? I
could open an MSDN incident, but I'd rather not.
Turning on ICF by default on the LAN connection would be disasterous to
our customers. We have over 100 customers using our product, which
relies on DCOM & IP to communicate between the client workstations and
the server.
Our customers that have an Internet connection have either a firewall
or at least a basic router that protects their internal network. The
workstations only have a single network connection, and that's the LAN
connection. Enabling ICF by default on the LAN connection would
definitely prevent our software from functioning, and I suspect would
cause problems for other ISVs that use DCOM.
Firewalls are not intended to be run at the workstation level, blocking
data to that workstation. They are intended to protect the entire
local network from outside access. I've always thought ICF was a dumb
idea to begin with, but enabling ICF by default will cost our company a
lot of time and money to go back and disable it on every one of our
customer workstations (well over 2,000 workstations).
Jon
'Trust'", pg 10, 2nd paragraph that begins with "WIndows XP will also
get").
The article states that ICF will be enabled by default in WinXP SP2.
Where can I get official information from Microsoft regarding this? I
could open an MSDN incident, but I'd rather not.
Turning on ICF by default on the LAN connection would be disasterous to
our customers. We have over 100 customers using our product, which
relies on DCOM & IP to communicate between the client workstations and
the server.
Our customers that have an Internet connection have either a firewall
or at least a basic router that protects their internal network. The
workstations only have a single network connection, and that's the LAN
connection. Enabling ICF by default on the LAN connection would
definitely prevent our software from functioning, and I suspect would
cause problems for other ISVs that use DCOM.
Firewalls are not intended to be run at the workstation level, blocking
data to that workstation. They are intended to protect the entire
local network from outside access. I've always thought ICF was a dumb
idea to begin with, but enabling ICF by default will cost our company a
lot of time and money to go back and disable it on every one of our
customer workstations (well over 2,000 workstations).
Jon