Cant view shared files

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

Guest

Iv set up a home network using the wizard on two PCs, and set up a shared
file on one.

But when I try too access this file it doesnt appear in "My Network Places".

I then click workgroup and the PCs in the network are there, but if I select
the other PC, with the shared folder, I am denied.

Anyone help me?
 
Iv set up a home network using the wizard on two PCs, and set up a shared
file on one.

But when I try too access this file it doesnt appear in "My Network Places".

I then click workgroup and the PCs in the network are there, but if I select
the other PC, with the shared folder, I am denied.

Anyone help me?
Click to expand...

Lack of access / visibility is a very common symptom here, with many causes.
One of the most common would be a misconfigured or overlooked personal firewall,
or other security component. There are several other possibilities too, and any
might be the cause of your problem. Read this article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

Or provide "browstat status" and "ipconfig /all" from each computer, so we can
diagnose the problem. Read this article, and linked articles, and follow
instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Please let us know if any of these suggestions are of any help. What you learn
may help others in the future, and that's the purpose of these forums.
 
ipconfig /all

My PC:

Windows IP Configuration

Host Name . . . . . . . . . . . . : fancydancer
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-13-8F-78-5D-49
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 62.31.144.39
195.188.53.175
62.31.112.39
Lease Obtained. . . . . . . . . . : 30 March 2006 18:33:31
Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07


Other PC:

Windows IP Configuration

Host Name . . . . . . . . . . . . : THEBEAST
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-30-18-62-AB-9E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::230:18ff:fe62:ab9e%4
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 62.31.144.39
195.188.53.175
62.31.112.39
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : 30 March 2006 17:51:04
Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 80-00-58-3B-AD-D8-A3-3D
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . :
3ffe:831f:4004:1952:8000:583b:add8:a
33d
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-00-03
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.3%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled



the browstat status didnt work
 
ipconfig /all
Click to expand...

the browstat status didnt work
Click to expand...

OK, you have 2 problems there.

First, FancyDancer has an nVidia nForce network card. This card has a built in
hardware firewall. There are a few less than satisfied nVidia customers.
<http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html>
http://nitecruzr.blogspot.com/2006/02/hidden-personal-firewall-nvidia-nforce.html

Secondly, THEBEAST has IPV6 aka Teredo Tunneling aka Microsoft IPV6. Please
remove that (don't just uncheck it's entry in the list!).
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Then retry "ipconfig /all" and "browstat status".
 
IPconfig /all:

Windows IP Configuration

Host Name . . . . . . . . . . . . : THEBEAST
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-30-18-62-AB-9E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 62.31.144.39
195.188.53.175
62.31.112.39
Lease Obtained. . . . . . . . . . : 30 March 2006 20:41:56
Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07

I dont no how too fix the firewall on the Nvidia, I dont have it installed
on my pc so I cant access the settings, or administrate it. I read through
that forum and googled it but couldnt find anything on removing the firewall.

Any tips?
 
If I just remove the driver for my network card will that remove the firewall
aswell?

And will the card still work without any drivers?
 
If I just remove the driver for my network card will that remove the firewall
aswell?

And will the card still work without any drivers?
Click to expand...

Those are the questions of the week. We don't know a lot about the nForce
firewall. It's supposed to be a hardware firewall, and it's promoted as one.
Take a look at your LSP stack, and see if there are nVidia drivers bound in
there.

For XP SP2:
<http://nitecruzr.blogspot.com/2006/03/lsp-winsock-analysis-using-netsh.html>
http://nitecruzr.blogspot.com/2006/03/lsp-winsock-analysis-using-netsh.html

For all other OS / SP levels:
<http://nitecruzr.blogspot.com/2005/12/lsp-winsock-analysis-using-log-from.html>
http://nitecruzr.blogspot.com/2005/12/lsp-winsock-analysis-using-log-from.html

And read my articles, and follow the links to the nVidia forums. Do some
research. What you find out could help the next guy, and you, if you help us.
 
Back
Top