hostname's and ICF

[mt]

Were using Internet Connection Firewall on all of our xp client machines. We
use an application called "filemaker pro" which uses local hostnames to
allow users to access databases in their own subnet.

However users cannot access each other via hostname with ICF enabled, but
they can access via IP address.
With ICF disable all works well.

I've tried freeing up tcp port 53 for dns as well as tcp/udp ports 137,138,
and 139 for Netbios but no luck.

Any thoughts?

please email
(e-mail address removed)

 

[Lanwench [MVP - Exchange]]

ICF is not designed for LAN-facing connections. I suggest you get a decent
broadband router/firewall and use it to protect your entire network - you
can get a NetGear FR114P for about $80 last time I checked at www.cdw.com.
Make sure it's a firewall, not just a NAT box.

 

[Guest]

If you consult the windows help on your computer it
clearly states that ICF
is for use only on computers directly connected to the
Internet and may
interfere with LAN communications if turned on for LAN
connections.

If you want a firewall on your LAN try one of the good
free firewalls such
as zonealarm or sygate.

 

[mt]

I understand where your both coming from with this but were running a public
lan, with registered IP's on all machines, and they are directly connected
to the internet.

 

[Lanwench [MVP - Exchange]]

You absolutely need to get a good hardware firewall and put it between your
Internet router and your LAN. Even if you also want to run software
firewalls of some sort.

You don't need public IPs on your LAN - although if you put a firewall in
place, they will essentially become 'private', it's still not recommended
practice.

 

[mt]

I couldn't agree more, however the university policy doesn't permit private
lan.


"Lanwench [MVP - Exchange]"

 

[Lanwench [MVP - Exchange]]

Is the network you're on protected from the Internet by a decent firewall?
I'd sure hope so....if not, I'd talk to the highest-level people I could
find. If they're running public IPs on LAN computers, they probably have
their heads buried somewhere dark.

I couldn't agree more, however the university policy doesn't permit
private lan.


"Lanwench [MVP - Exchange]"

You absolutely need to get a good hardware firewall and put it
between your Internet router and your LAN. Even if you also want to
run software firewalls of some sort.

You don't need public IPs on your LAN - although if you put a
firewall in place, they will essentially become 'private', it's
still not recommended practice.