Re: Network file/print sharing

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Vince Taylor (VinceTaylor_at_discussions.microsoft.com)
Date: 02/10/05

Next message: Ron Lowe: "Re: L2TP Error 781"
Previous message: Spirit: "Re: Networking Drive Permission lost"
In reply to: Eric Cross [MVP]: "Re: Network file/print sharing"
Messages sorted by: [ date ] [ thread ]

Date: Thu, 10 Feb 2005 13:19:03 -0800

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
"Eric Cross [MVP]" wrote:

> 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
>
>

Next message: Ron Lowe: "Re: L2TP Error 781"
Previous message: Spirit: "Re: Networking Drive Permission lost"
In reply to: Eric Cross [MVP]: "Re: Network file/print sharing"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

sharing pcs & files-different locations
... & one in our small business. ... I also have a new Laptop. ... Can I make it so that I can access files between both desktop pc's? ... windows xp home/sp2/AVG virus/Zonealarm, windows firewall on LT, ...
(microsoft.public.windowsxp.basics)
Re: Network file/print sharing
... When I tried to access files on my computer from the ... laptop, the no access message still appeared. ... With Windows Firewall ...
(microsoft.public.windowsxp.network_web)
Re: networking from laptop to PC malfunction
... PC is ethernet to router. ... >Laptop, Laptop not able to access files on the PC, unless I ... upgrade your antivirus program to the latest version and retest. ...
(microsoft.public.windowsxp.network_web)
Re: Picture files eror message
... fine since I bought new laptop. ... I can still access files by right ... open with> Photo Gallery but would like to be able to open them ... Windows Vista Home Premium x64 + SP1 ...
(microsoft.public.windows.vista.music_pictures_video)
RE: no internet or email connection
... Running XP Pro SP2 on laptop. ... Wireless net is healthy (can access files, ... With either LAN or dialup cannot access internet or email. ...
(microsoft.public.windowsxp.network_web)