Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Laura A. Robinson (larobins_at_bellatlantic.net)
Date: Wed Aug 21 2002 - 14:29:24 CDT
No, you do not need to open the NetBIOS ports to use file and printer
sharing in Windows 2000/XP.
----- Original Message -----
From: "Benjamin D. Goldman" <bgoldmankipany.com>
To: "Bryan Ponnwitz" <bponnwitbtboces.org>;
Sent: Wednesday, August 21, 2002 12:21 PM
Subject: RE: Windows File Sharing with IPCop
even without NetBios, you probably have to open up the RPC, etc etc
ports... the ones that you should always block..
135-139... someone correct me if I am wrong - but I dont think you can
even use the browsing capability (which is still required even without
netbios use explicitly) without having these open.
From: Bryan Ponnwitz [mailto:bponnwitbtboces.org]
Sent: Tuesday, August 20, 2002 8:36 PM
Subject: Windows File Sharing with IPCop
I've run into a road block with my IPCop firewall and I'm hoping for
some help. Here's the scenario:
I'm running IPCop at work to segment me from the rest of the network. I
have a WinXP box behind my IPCop firewall. The XP machine is acting as
a File and Printer Sharing and Terminal Services server. File sharing
is configured for TCP/IP (no NetBIOS). I would like to be able to
access the WinXP box from the outside network. I looked on the
Microsoft support site, and found that you need to forward 445/TCP and
445/UDP to get it to work. I set this up and still cannot access the
shares. I did the exact same setup for Terminal Services (except on
port 3389) and it works like a charm. When I try to telnet to port 445
on the IPCop machine from the external network, it doesn't connect which
makes me think that it's a problem with IPCop. Could it be that IPCop
runs it's secure web UI on port 445 and is therefore blocking that port?
Any help would be much appreciated!!
Webmaster - Broome-Tioga Boces