Network file/print sharing

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have 3 computer wireless network, all running XP Home SP2. With SP2, one
(only one) of the computers cannot access files or printer on my main
computer with the firewall on this computer enabled (although file and print
sharing are supposedly enabled). Turning off the firewall solves the problem,
but I want a firewall.

Are there any fixes to this problem? I have auto updating on all computers;
so I have the latest distributed fixes from MS.
 
Greetings Vince,

If any of the computers have the Windows Firewall enabled, make sure it is
properly configured for file and printer sharing. With Windows Firewall
enabled, go to the Exception tab, and make sure the File and Printer Sharing
checkbox is checked.

If it works when you temporary disable the Windows Firewall, enable the
firewall again, and then enable firewall logging for both successful and
drop packets. Then try it again and look at the pfirewall.log file in the
C:\Windows\ directory.

_____________
Eric Cross
Microsoft MVP (Windows Networking)
http://mvp.support.microsoft.com
 
I did as instructed. When I tried to access files on my computer from the
laptop, the no access message still appeared. There was no pfirewall.log on
the laptop. On my computer, the log file showed lots of entries like the
following:
2005-02-04 09:21:15 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-04 09:21:16 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE

Any more suggestions?

Vince
 
Hi Vince,

That log file is showing ports 137 being dropped by the Windows Firewall.
For file and printer sharing the following ports must be opened to allow
file and printer sharing traffic. The ports are UDP 137, 138, TCP 139, and
445. Under the Exceptions tab in the Windows Firewall, select File and
Printer Sharing and click the Edit button. Make sure those checkboxes are
selected.

Did you enable Logging on the laptop? To do so, follow these steps:

1. Click Start, Run, type firewall.cpl, and then click Ok.
2. Click the Advanced tab.
3. Under Security Logging, click the Settings button.
4. In the Log settings, select the Drop and Successful Connections
checkboxes and click Ok.
5. Click Ok to close the firewall.

_____________
Eric Cross
Microsoft MVP (Windows Networking)
http://mvp.support.microsoft.com
 
Dear Eric,

All of the listed ports are open on the computer whose log file I copied.
What's next?

I did set of logging on the laptop, but I think I had forgotten to okay my
way completely out of the dialog boxes. I have done so now.

Look forward to more of your useful help.

Thanks,

Vince
 
Hi Vince,

If those ports are opened in the Windows Firewall to allow file and printer
sharing, then you should able to share files and your printer unless your
running a third party firewall that is blocking your computer. If so, you'll
need to make sure it is properly configured and not blocking access between
the machines on the network. Otherwise, you'll need to repost the log file
so we can see what's happening with the Windows Firewall enabled.

_____________
Eric Cross
Microsoft MVP (Windows Networking)
http://mvp.support.microsoft.com
 
Dear Eric,

I have confirmed that the ports you listed are open on both my computer and
the laptop, and I have enabled logging on both computers.

My computer can see and access the laptop files. Here is the log file on my
computer when I sucessfully access a shared file on the laptop:

1429827614 1429827614 0 - - - RECEIVE
2005-02-07 11:02:59 OPEN TCP 192.168.1.101 65.254.254.34 1143 110 - - - - -
- - - -
2005-02-07 11:03:59 CLOSE UDP 192.168.1.101 67.21.13.2 1027 53 - - - - - - -
- -
2005-02-07 11:04:10 CLOSE TCP 192.168.1.101 207.46.250.113 1120 443 - - - -
- - - - -
2005-02-07 11:04:15 CLOSE TCP 192.168.1.101 207.46.156.156 1139 80 - - - - -
- - - -
2005-02-07 11:04:15 CLOSE TCP 192.168.1.101 207.46.156.156 1140 80 - - - - -
- - - -
2005-02-07 11:04:28 CLOSE TCP 192.168.1.101 207.46.250.113 1108 443 - - - -

The laptop can see that my computer exists on the network. Here is the
laptop log file (in its entirety) when I tried to access a directory of
shared files for my computer:
#Version: 1.5
#Software: Microsoft Windows Firewall
#Time Format: Local
#Fields: date time action protocol src-ip dst-ip src-port dst-port size
tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path

2005-02-07 10:57:25 OPEN TCP 192.168.1.100 192.168.1.101 139 61797 - - - - -
- - - -

Here is the corresponding log file on my computer:
- - - - - RECEIVE
2005-02-07 10:57:34 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-07 10:57:34 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-07 10:57:34 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-07 10:57:34 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-07 10:57:35 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-07 10:57:35 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-07 10:57:36 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-07 10:57:37 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - - - -
- - - RECEIVE
2005-02-07 10:57:37 DROP UDP 192.168.1.100 192.168.1.255 137 137 78 - -

I find it very puzzling that I can access the laptop files, but that the
laptop cannot access mine. Note that this inability to access my files
happens even if the firewall on the laptop is disabled. Note also that the
laptop can access files on a third computer with its firewall enabled. What
could possibly explain this.

I don't have any third-party firewalls installed on my computer. The
wireless network (Linksys) does have some kind of rudimentary firewall, I
believe, but this has been in place long before this problem arose.

Thanks for your help.

Vince
 
Hi Vince,

The entries in the log file on your computer is still showing ports 137
being dropped by the Windows Firewall. An alternative solution is try
opening the ports via the command prompt. Open the command prompt (Click
Start - Run - cmd), type the following line, and then press Enter.

netsh firewall set portopening UDP 137 ENABLE

_____________
Eric Cross
Microsoft MVP (Windows Networking)
http://mvp.support.microsoft.com
 
Dear Eric,

I have done as you suggested. I received the response: "OK". However, the
result was the same. When I try to access files or directories on my computer
from the laptop, I receive the message access denied.

Here is the log from the laptop for the session where I tried to access my
computer. Probably only the last few entries are relevant, because it took a
few tries to even show my computer as a network resource.

Laptop log:
2005-02-10 12:56:00 CLOSE TCP 192.168.1.100 216.49.88.118 1216 80 - - - - -
- - - -
2005-02-10 12:56:00 CLOSE TCP 192.168.1.100 216.49.88.118 1217 80 - - - - -
- - - -
2005-02-10 12:56:00 CLOSE TCP 192.168.1.100 216.49.88.118 1218 80 - - - - -
- - - -
2005-02-10 12:56:03 DROP UDP 0.0.0.0 255.255.255.255 68 67 330 - - - - - - -
RECEIVE
2005-02-10 12:56:06 DROP UDP 192.168.1.100 239.255.255.250 1265 1900 161 - -
- - - - - RECEIVE
2005-02-10 12:56:09 DROP UDP 192.168.1.100 239.255.255.250 1265 1900 161 - -
- - - - - RECEIVE
2005-02-10 12:56:12 DROP UDP 192.168.1.100 239.255.255.250 1265 1900 161 - -
- - - - - RECEIVE
2005-02-10 12:56:31 OPEN UDP 192.168.1.100 67.21.13.2 1027 53 - - - - - - -
- -
2005-02-10 12:56:32 OPEN TCP 192.168.1.100 216.150.240.41 1271 110 - - - - -
- - - -
2005-02-10 12:56:32 OPEN TCP 192.168.1.100 64.12.180.19 1274 80 - - - - - -
- - -
2005-02-10 12:56:36 OPEN TCP 192.168.1.100 207.200.89.193 1275 80 - - - - -
- - - -
2005-02-10 12:56:36 CLOSE TCP 192.168.1.100 64.12.180.19 1274 80 - - - - - -
- - -
2005-02-10 12:56:36 OPEN TCP 192.168.1.100 207.200.89.193 1276 80 - - - - -
- - - -
2005-02-10 12:56:37 OPEN TCP 192.168.1.100 207.200.86.79 1277 80 - - - - - -
- - -
2005-02-10 12:56:37 OPEN TCP 192.168.1.100 64.236.44.88 1278 80 - - - - - -
- - -
2005-02-10 12:56:37 OPEN TCP 192.168.1.100 64.236.44.88 1279 80 - - - - - -
- - -
2005-02-10 12:56:37 OPEN TCP 192.168.1.100 64.12.174.57 1280 80 - - - - - -
- - -
2005-02-10 12:57:17 CLOSE TCP 192.168.1.100 207.200.86.79 1277 80 - - - - -
- - - -
2005-02-10 12:57:18 CLOSE TCP 192.168.1.100 64.12.174.57 1280 80 - - - - - -
- - -
2005-02-10 12:57:32 CLOSE TCP 192.168.1.100 207.200.89.193 1276 80 - - - - -
- - - -
2005-02-10 12:57:32 CLOSE TCP 192.168.1.100 207.200.89.193 1275 80 - - - - -
- - - -
2005-02-10 12:57:50 INFO-EVENTS-LOST - - - - - - - - - - - - 19 -
2005-02-10 12:58:00 CLOSE UDP 192.168.1.100 67.21.13.2 1027 53 - - - - - - -
- -
2005-02-10 12:58:34 CLOSE TCP 192.168.1.100 216.150.240.41 1271 110 - - - -
- - - - -
2005-02-10 12:58:40 OPEN UDP 192.168.1.100 67.21.13.2 1027 53 - - - -

My corresponding computer log:

2005-02-10 12:56:00 CLOSE TCP 192.168.1.100 216.49.88.118 1216 80 - - - - -
- - - -
2005-02-10 12:56:00 CLOSE TCP 192.168.1.100 216.49.88.118 1217 80 - - - - -
- - - -
2005-02-10 12:56:00 CLOSE TCP 192.168.1.100 216.49.88.118 1218 80 - - - - -
- - - -
2005-02-10 12:56:03 DROP UDP 0.0.0.0 255.255.255.255 68 67 330 - - - - - - -
RECEIVE
2005-02-10 12:56:06 DROP UDP 192.168.1.100 239.255.255.250 1265 1900 161 - -
- - - - - RECEIVE
2005-02-10 12:56:09 DROP UDP 192.168.1.100 239.255.255.250 1265 1900 161 - -
- - - - - RECEIVE
2005-02-10 12:56:12 DROP UDP 192.168.1.100 239.255.255.250 1265 1900 161 - -
- - - - - RECEIVE
2005-02-10 12:56:31 OPEN UDP 192.168.1.100 67.21.13.2 1027 53 - - - - - - -
- -
2005-02-10 12:56:32 OPEN TCP 192.168.1.100 216.150.240.41 1271 110 - - - - -
- - - -
2005-02-10 12:56:32 OPEN TCP 192.168.1.100 64.12.180.19 1274 80 - - - - - -
- - -
2005-02-10 12:56:36 OPEN TCP 192.168.1.100 207.200.89.193 1275 80 - - - - -
- - - -
2005-02-10 12:56:36 CLOSE TCP 192.168.1.100 64.12.180.19 1274 80 - - - - - -
- - -
2005-02-10 12:56:36 OPEN TCP 192.168.1.100 207.200.89.193 1276 80 - - - - -
- - - -
2005-02-10 12:56:37 OPEN TCP 192.168.1.100 207.200.86.79 1277 80 - - - - - -
- - -
2005-02-10 12:56:37 OPEN TCP 192.168.1.100 64.236.44.88 1278 80 - - - - - -
- - -
2005-02-10 12:56:37 OPEN TCP 192.168.1.100 64.236.44.88 1279 80 - - - - - -
- - -
2005-02-10 12:56:37 OPEN TCP 192.168.1.100 64.12.174.57 1280 80 - - - - - -
- - -
2005-02-10 12:57:17 CLOSE TCP 192.168.1.100 207.200.86.79 1277 80 - - - - -
- - - -
2005-02-10 12:57:18 CLOSE TCP 192.168.1.100 64.12.174.57 1280 80 - - - - - -
- - -
2005-02-10 12:57:32 CLOSE TCP 192.168.1.100 207.200.89.193 1276 80 - - - - -
- - - -
2005-02-10 12:57:32 CLOSE TCP 192.168.1.100 207.200.89.193 1275 80 - - - - -
- - - -
2005-02-10 12:57:50 INFO-EVENTS-LOST - - - - - - - - - - - - 19 -
2005-02-10 12:58:00 CLOSE UDP 192.168.1.100 67.21.13.2 1027 53 - - - - - - -
- -
2005-02-10 12:58:34 CLOSE TCP 192.168.1.100 216.150.240.41 1271 110 - - - -
- - - - -
2005-02-10 12:58:40 OPEN UDP 192.168.1.100 67.21.13.2 1027 53 - -

Any further insights?

Vince
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Sharing files in XP 2
help with home networking 1
File sharing working one way 14
File Sharing Issues - Can't Get My Home Network Running 5
File & Print Sharing via Wireless Access Point 13
File and printer sharing problem 2
Loss of File and Printer Sharing 2
Enable file/printer sharing in home wlan only, disabled in otherwlans 2

Back
Top