[fran101]

I have 1 pc using vista ultimate and 2 laptops using vista home premium. I use a BT homehub 2 to which my pc is connected via ethernet and the laptop are connected via wireless connection. Network discovery has been activated on all 3 machines and all machines are visible on the network.

The problem I am having is: each of the laptops can share files and folders via the network, laptop 1 can share with the pc in both directions but laptop 2 can not access the pc even tho the pc can access laptop 2. When accessing the pc via the laptop i get an error message stating "\\FRANCIS-PC is not accessible. You may not have permission to use the network resource"

This problem has only come about since the laptop (os) was re - built. As a tempoary stop gap I have been using net-op remote control host and guest to allow laptop 2 to access the pc which was working fine, but now it states that the pc cannot be found even though it can be seen in the network window. I have tried pinging the pc and that was successful with no loss.

Below is ipconfig /all

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Francis>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Francis-Laptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-16-EA-47-1A-B8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::689c:b62d:b99b:ed46%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.66(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 04 July 2009 02:08:03
Lease Expires . . . . . . . . . . : 05 July 2009 12:06:41
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 268441322
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-CA-1B-27-00-03-0D-9D-E2-4A

DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8102/8103 Family PCI-E FE NIC
Physical Address. . . . . . . . . : 00-03-0D-9D-E2-4A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{A5790F50-359C-4CDA-860C-8C52371F6
BC3}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : isatap.home
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2d6:1c6d:f01:a966:db83(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::1c6d:f01:a966:db83%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Francis>

Any help would be great

[pedroguy]

Hi:If the ipconfig is from l2,you do have an apparently good network connection.
Have you tried pinging l2 from the pc
A failure to ping is generally a firewall issue.So if no pinging,I would disable the firewall running on l2 first,try pings,if no joy,disable the firewall on the pc.
Make sure that any or all firewalls running(Windows and/or third party firewalls that may be running in any security suite that you have installed)
So,from pc you would be pinging 192.168.1.66.

If no joy there,the next step I might take is to disable encryption in the router just to see if this is a security issue.

[JohnWill]

Turn off any firewalls for debugging. If the firewall is the problem, you'll have to configure it to allow access to "trusted zone" addresses. Note that some firewalls must be completely uninstalled to stop them from affecting your networking.

Hold the Windows key and press R, then type CMD to open a command prompt.

In the command prompt window that opens, type type the following commands:

PING each remote computer by IP address, and if successful, PING by name. Open a command prompt as described above and type.

PING <ip address>
or
PING <computer name>

Where:
<ip address> - is the x.x.x.x IP address
<computer name> - is the computer name

A failure to PING is almost always a firewall configuration issue. Any failure to PING needs to be corrected before you go any farther.

Note: You can obtain the IP address and computer name of a computer by opening a command prompt (DOS window) and typing IPCONFIG /ALL. This should work for any Windows version. The IPCONFIG /ALL display will provide a wealth of useful information for debugging your network connection.

Check your Services are Started on all PCs:

• COM+ Event System (for WZC issues)
• Computer Browser
• DHCP Client
• DNS Client
• Network Connections
• Network Location Awareness
• Remote Procedure Call (RPC)
• Server
• TCP/IP Netbios helper
• Wireless Zero Configuration (XP wireless configurations)
• WLAN AutoConfig (Vista wireless configurations)
• Workstation

Note: You can check the services in Control Panel, Administrative Tools, Services.

All of these services should be started, and their startup type should be automatic.

If a service is not running, open it's properties and check the dependencies. Check each of the dependencies and see which one is preventing the service from running. Checking the event log is also a good idea here, there may be clues to what is failing.


All computers should be in the same workgroup for computer browsing to function properly. File & Print Sharing has to be enabled on any computer you wish to share files or printers from. You also need to actually share the resource in question from My Computer, right click on the drive/printer/folder, and select sharing.

If you encounter difficulties accessing computers that are visible in Network Places (Network and Sharing Center in Vista), make sure the computer being accessed has an account with the same name/password as the system connecting to it uses to login. NOTE: Vista's default is to require a password on the account to enable file/print sharing.

While the default NetBIOS setting is correct for normal network configurations, it's possible for it to be altered, and it costs nothing to make sure it's correct. NETBIOS over TCP/IP must be enabled for normal network browsing. You can open a command prompt as described above and type the following command: nbtstat -n. This will display the status of NetBIOS or indicate it's not configured.