Re: Windows File Sharing with IPCop

From: Laura A. Robinson (larobins@bellatlantic.net)
Date: 08/21/02 

From: "Laura A. Robinson" <larobins@bellatlantic.net>
To: "Benjamin D. Goldman" <bgoldman@kipany.com>, "Bryan Ponnwitz" <bponnwit@btboces.org>, <focus-ms@lists.securityfocus.com>
Date: Wed, 21 Aug 2002 15:29:24 -0400

No, you do not need to open the NetBIOS ports to use file and printer
sharing in Windows 2000/XP.

Laura
----- Original Message -----
From: "Benjamin D. Goldman" <bgoldman@kipany.com>
To: "Bryan Ponnwitz" <bponnwit@btboces.org>;
<focus-ms@lists.securityfocus.COM>
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.

-----Original Message-----
From: Bryan Ponnwitz [mailto:bponnwit@btboces.org]
Sent: Tuesday, August 20, 2002 8:36 PM
To: focus-ms@lists.securityfocus.COM
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!!

Bryan Ponnwitz
Webmaster - Broome-Tioga Boces
bponnwit@btboces.org
(607) 763-3609

Relevant Pages

  • RE: Windows File Sharing with IPCop
    ... netbios use explicitly) without having these open. ... Windows File Sharing with IPCop ... I'm running IPCop at work to segment me from the rest of the network. ... port 3389) and it works like a charm. ...
    (Focus-Microsoft)
  • Re: Functions of Port 445?
    ... get rid of all NetBios over Tcp/Ip) ... performed by port 445? ... which uinstalls the Server service. ... other functions being performed by 445 other than file sharing. ...
    (microsoft.public.windows.server.security)
  • RE: Windows File Sharing with IPCop
    ... Ahhh, he's trying to use Direct Host, which is pretty much NetBIOS version 2 ... RPC SHOULDN'T be necessary because RPC is for client/server communications ... However, if I'm am wrong, and its happened before, open TCP port 135 (RPC ... Windows File Sharing with IPCop ...
    (Focus-Microsoft)
  • RE: Windows File Sharing with IPCop
    ... I suggest you change the port of the IPCop UI to something else its in /etc/httpd/conf/httpd.conf. ... There may also be some hard coded ipchains for the port 445 in the start-up scripts so check them also. ... Windows File Sharing with IPCop ... I'm running IPCop at work to segment me from the rest of the network. ...
    (Focus-Microsoft)
  • Effect of NetBIOS Over TCP on File Sharing
    ... If NetBIOS over TCP is turned off on a workstation, will port 137 the ... NetBIOS Name Service be used at all? ... If NetBIOS over TCP is turned off, will file sharing from servers located ... Aside from making it impossible to do file sharing with older servers, ...
    (microsoft.public.windows.server.security)