problem with network share and Windows FireWall

[Jeff]

Hey

I have 2 computers in my home network, one pc is a winXPpro+sp2, the other
is a win2k3 machine

on the win2k3 machine I've created a NFS share, using fs.msc.... The problem
is that I'm unable to connect to this share from the winXP machine.... well,
if I turn off firewall on both machines I'm able to connect, so I guess it
is a firewall issue

win2k3 machine is domain controller in this network, Active Directory
installed

These are the ports I've opened on Windows FireWall in both machines:
111 - both TCP and UDP
1039 - both TCP and UDP
1047 - both TCP and UDP
1048 - both TCP and UDP
2049 - both TCP and UDP

Haven't enabled the "File and printer share" on both machines

any suggestions?

Jeff

 

[Mike Lowery]

Sniff the traffic to find out what ports need to be opened.

 

[Jeff]

what tools in windows do you recommend for sniffing ports ?

Jeff

 

[Jeff]

I ran LanSpy 2.0 and discovered these available ports on the win2k3 machine
(I run the test from the winXP machine) :
21, 80, 139, 445, 3389

Another strange thing is that I've created exceptions for 111, 1039, 1047,
1048, 2049 but LanSpy didn't find them. So that may mean that LanSpy is a
bad tool... or there is a issue in the Windows Firewall on the win2k3
machine

The problem is that on the win2k3 machine I've created a share and I'm
unable to connect to that share if firewalls are turned on... But I hope
there can be possible to enable some kind of exceptions that allow having
firewall turned on, and allowing me to connect to the shares from my winXP
machine.. On these exceptions I've specified using my subnet as restriction
(scope), so the ports don't come available for the entire world

Any suggestions?

 

[Mike Lowery]

Sniff the traffic, not ports. You can already find out what ports are open
by running "netstat -an".

Load up Wireshark and look at the packets coming in to your server. You'll
be able to determine what ports they're trying to reach.