Accessing other XP machine and NAS from Vista

  • Thread starter Thread starter ben
  • Start date Start date
B

ben

I have a problem with new vista machines unable to access existing machines.
I used to have two desktops and a laptop all running XP and a network storage
device. Each machine could share with every other machine and everything was
fine.

One of the desktops and the laptop died, to be replaced by two new laptops
running vista. So I now have:
1 desktop running XP Home SP2
1 laptop running vista home basic
1 laptop running vista home premium
1 QNAP TS-101 NAS
Everything is networked via a Speedtouch router with built in firewall

The desktop can access all machines. The two vista machines can share both
ways between them. However, the vista laptop machines cannot access the
desktop or NAS. They can see the available shares, but when you try and
access anything, you get the following message:

" \\computername is not accessible. You might not have permission
to use the network resource. Contact the administrator of this server
to find out if you have access permissions".

I've trawled through dozens of pages on the internet looking for info. As a
result, here are some of the settings and things I have tried:

firewalls turned off on all machines
all machines have the same workgroup name
file and printer sharing is on everywhere
run the Home Network File sharing Wizard on the XP machine
created a user account on each machine with the same username and password
on the vista machines
network is set to private
network discovery is on
file sharing is on
public folder sharing is on
installed the LLTD Responder software on XP machine
in TCP/IP properties, set always use netbios over tcp/ip and turned off use
lmhosts
RestrictAnonymous Registry entry is 0 on all machines
tried setting LmCompatibilityLevel to 1 on all machines

A subsidiary problem is that when I show the full network on the vista
machines, they see all the machines, but can't place the NAS in the network.

Any suggestions? Thanks for any help.
 
1. Create the username on all 3 computers. hopefully that will fix the
accessing XP issue.

Vista common issue - can see but ...and one xp from the vista however one is
prompting for a user name and ... so that you may want to create same
username and password on the both computers. ...
www.chicagotech.net/netforums/viewtopic.php?t=450


2. NAS could be the LM Authentication issue. Check this link for more
details.

Vista Permission IssuesVista: Can’t access NAS,MAC, Linux, Samba and Win98 >
http://www.chicagotech.net/netforums/viewforum.php?f=1 > > Bob Lin, MS-MVP,
MCSE & CNE . ...
www.chicagotech.net/vista/vistapermission.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
 
I have a problem with new vista machines unable to access existing machines.
I used to have two desktops and a laptop all running XP and a network storage
device. Each machine could share with every other machine and everything was
fine.

One of the desktops and the laptop died, to be replaced by two new laptops
running vista. So I now have:
1 desktop running XP Home SP2
1 laptop running vista home basic
1 laptop running vista home premium
1 QNAP TS-101 NAS
Everything is networked via a Speedtouch router with built in firewall

The desktop can access all machines. The two vista machines can share both
ways between them. However, the vista laptop machines cannot access the
desktop or NAS. They can see the available shares, but when you try and
access anything, you get the following message:

" \\computername is not accessible. You might not have permission
to use the network resource. Contact the administrator of this server
to find out if you have access permissions".

I've trawled through dozens of pages on the internet looking for info. As a
result, here are some of the settings and things I have tried:

firewalls turned off on all machines
all machines have the same workgroup name
file and printer sharing is on everywhere
run the Home Network File sharing Wizard on the XP machine
created a user account on each machine with the same username and password
on the vista machines
network is set to private
network discovery is on
file sharing is on
public folder sharing is on
installed the LLTD Responder software on XP machine
in TCP/IP properties, set always use netbios over tcp/ip and turned off use
lmhosts
RestrictAnonymous Registry entry is 0 on all machines
tried setting LmCompatibilityLevel to 1 on all machines

A subsidiary problem is that when I show the full network on the vista
machines, they see all the machines, but can't place the NAS in the network.

Any suggestions? Thanks for any help.
Click to expand...

Ben,

The desktop computer, running XP Home, will have Guest access only. Make sure
that Guest is properly activated.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest

If you trust all users of each computer equally (or if you're the only user)
then disabling Password Protected Sharing (Vista) or enabling Simple File
Sharing (XP), then enabling Guest on all computers, is the reliable and simple
way to setup your LAN.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Simple>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Simple

If you're having problems accessing a NAS from Vista, that may be an
authentication protocol problem. Vista only uses NTLM V2; XP would use NTLM V1
or V2, as required.
<http://nitecruzr.blogspot.com/2007/05/microsoft-windows-and-authentication.html>
http://nitecruzr.blogspot.com/2007/05/microsoft-windows-and-authentication.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Thanks for the response, Robert.

1. I have already, created the same username and password on both the Vista
and Xp machines, but this doesn't work I'm afraid.

2. I've already tried setting the LmCompatibilityLevel to 1, but again,
this hasn't worked.
 
Thanks for the response, Chuck.

I've tried activating the Guest account as you suggest. Unfortunately, this
hasn't helped. Incidentally, in your instructions, you show the use of a -g
option with the ntrights utility which gave an error. I assume that -u
should be used, which then refers to either a user or group, whichever the
specified name happens to be.

I could try the simple password disabling route if you think it might work,
but it's not ideal.

As I've already said, I've already tried setting the LmCompatibilityLevel to
1 and it hasn't worked.
 
What do you mean by "simple file sharing" on XP? File sharing is turned on
as part of the network set up.

Please don't forget that I can see shared files on the Vista machines from
XP. I have also accessed shared files on the XP machine from other XP
machines in the past.

Ben.
 
Thanks for the response, Chuck.

I've tried activating the Guest account as you suggest. Unfortunately, this
hasn't helped. Incidentally, in your instructions, you show the use of a -g
option with the ntrights utility which gave an error. I assume that -u
should be used, which then refers to either a user or group, whichever the
specified name happens to be.

I could try the simple password disabling route if you think it might work,
but it's not ideal.

As I've already said, I've already tried setting the LmCompatibilityLevel to
1 and it hasn't worked.
Click to expand...

Ben,

If you have a computer running XP Home (with Simple File Sharing forceably
enabled), you should disable Password Protected Sharing in Vista. Then, you'll
need to ensure that Guest is active on all computers for network access.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Guest

Than let's try some diagnostics. Look at logs from "browstat status", "ipconfig
/all", "net config server", and "net config workstation", from each computer.
Read this article, and linked articles, and follow instructions precisely
(Download browstat, and note the command window in Vista!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Thanks for continuing to help, Chuck. I've been away over the weekend, hence
delay in replying. Whilst away, I took the opportunity to try one of the
laptops in a different network with another Windows XP machine. I installed
the LLTD Responder and ran the network wizard on the XP machine. I was then
able to see shared files on the XP machine. I wasn't able to see files on
the Vista machine, but I didn't try any further.

I've run the diagnostics you have suggested. I found that when I run the
"net config server" command on the Vista machine, I get the following error:

System error 5 has occurred

Access is denied

Is this a symptom of the problem I am experiencing?

Also, I was unable to uninstall TCP/IPV6, as suggested. Whenever I selected
it, the uninstall option was greyed out. I have disabled it.

I can't see anything else untoward. Below is the output. Any further ideas?

Ben

=================================================

Desktop computer

Windows XP Home SP2

IPCONFIG



Windows IP Configuration



Host Name . . . . . . . . . . . . : BlackEvesham

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : lan



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : lan

Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet
Adapter

Physical Address. . . . . . . . . : 00-01-6C-EC-49-91

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.67

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.254

DHCP Server . . . . . . . . . . . : 192.168.1.254

DNS Servers . . . . . . . . . . . : 192.168.1.254

Lease Obtained. . . . . . . . . . : 04 February 2008 18:50:30

Lease Expires . . . . . . . . . . : 05 February 2008 18:50:30



NET CONFIG

Server Name \\BLACKEVESHAM
Server Comment Black Evesham in Study

Software version Windows 2002
Server is active on
NetBT_Tcpip_{15A9A7B3-A5A2-4B57-B24A-1B647FBC1353} (00016cec4991)
NetbiosSmb (000000000000)


Server hidden No
Maximum Logged On Users 5
Maximum open files per session 16384

Idle session time (min) 15
The command completed successfully.

Computer name \\BLACKEVESHAM
Full Computer name BlackEvesham
User name Ben

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{15A9A7B3-A5A2-4B57-B24A-1B647FBC1353} (00016CEC4991)

Software version Windows 2002

Workstation domain MSHOME
Workstation Domain DNS Name (null)
Logon domain BLACKEVESHAM

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.



BROWSTAT


Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{15A9A7B3-A5A2-4B57-B24A-1B647FBC1353}
Browsing is active on domain.
Master browser name is: BLACKEVESHAM
Master browser is running build 2600
1 backup servers retrieved from master BLACKEVESHAM
\\BLACKEVESHAM
There are 2 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{15A9A7B3-A5A2-4B57-B24A-1B647FBC1353}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{15A9A7B3-A5A2-4B57-B24A-1B647FBC1353}

=================================================

Laptop computer

Windows Vista Basic

IPCONFIG


Windows IP Configuration

Host Name . . . . . . . . . . . . : ToshSat
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Atheros AR5005G Wireless Network
Adapter
Physical Address. . . . . . . . . : 00-16-E3-C5-24-C4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.72(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 04 February 2008 16:39:15
Lease Expires . . . . . . . . . . : 05 February 2008 16:41:05
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
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 RTL8139/810x Family Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-16-36-F9-88-B4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{64269981-636F-4FAD-B04A-F32E57C2C26A}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.1.72%12(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Disabled


NET CONFIG

{net config Server failed - see above}


Computer name \\TOSHSAT
Full Computer name ToshSat
User name Ben

Workstation active on
NetbiosSmb (000000000000)
NetBT_Tcpip_{85B9BBD9-7474-4605-8E3F-FE01B97288A7} (0016E3C524C4)

Software version Windows Vista (TM) Home Basic

Workstation domain MSHOME
Logon domain ToshSat

COM Open Timeout (sec) 0
COM Send Count (byte) 16
COM Send Timeout (msec) 250
The command completed successfully.



BROWSTAT



Status for domain MSHOME on transport
\Device\NetBT_Tcpip_{85B9BBD9-7474-4605-8E3F-FE01B97288A7}
Browsing is active on domain.
Master browser name is: BLACKEVESHAM
Could not connect to registry, error = 53 Unable to determine build
of browser master: 53
\\\\BLACKEVESHAM . Version:05.01 Flags: 51203 NT POTENTIAL MASTER
1 backup servers retrieved from master BLACKEVESHAM
\\BLACKEVESHAM
There are 2 servers in domain MSHOME on transport
\Device\NetBT_Tcpip_{85B9BBD9-7474-4605-8E3F-FE01B97288A7}
There are 1 domains in domain MSHOME on transport
\Device\NetBT_Tcpip_{85B9BBD9-7474-4605-8E3F-FE01B97288A7}
 
I've just tried something I've tried before but not recently. Since I've
made a few changes, I ought to have tried it again before now. Anyway, it
was to try accessing shared files on the XP machine using a wired link
instead of wireless. Lo and behold, it works. I can also access the NAS.

So, the issue is what is different between the wired and wireless
connections. Do you have recommendations for investigation of this?
 
I've just tried something I've tried before but not recently. Since I've
made a few changes, I ought to have tried it again before now. Anyway, it
was to try accessing shared files on the XP machine using a wired link
instead of wireless. Lo and behold, it works. I can also access the NAS.

So, the issue is what is different between the wired and wireless
connections. Do you have recommendations for investigation of this?
Click to expand...

Ben,

Any computer can connect using WiFi, just as well as Ethernet, to a router and
it can access the Internet, and / or another computer, equally well.

The problem is IPV6. Remove IPV6 from both computers.
<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

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Chuck,

It's not possible to uninstall/remove TCP/IPV6 from Vista machines - see
http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx

I have disabled it as much as possible, by adding the suggested registry
value to disable tunnelling. However, it makes no difference.

I realise that, in principle, connecting via Wireless should be the same as
connecting using a wire, but clearly it isn't here. I have tried with both
laptops. Using wireless, I am unable to access files on the XP machine.
Using wired, I can see shared files.

Ben.
 
Hi Chuck,

I think that the problems I'm experiencing must be down to the router. I
have a Speedtouch 780. I notice from another thread (to which I have
responded) that these routers seem to have a problem. I'm having problems
updating the firmware, but I'm hoping that this will sort it out.

Thanks for your help, nevertheless.

Ben
 
Hi Chuck,

I think that the problems I'm experiencing must be down to the router. I
have a Speedtouch 780. I notice from another thread (to which I have
responded) that these routers seem to have a problem. I'm having problems
updating the firmware, but I'm hoping that this will sort it out.

Thanks for your help, nevertheless.

Ben
Click to expand...

Thanks for the update, Ben. I wonder if this is yet another symptom of the
Windows Scaling problem.
<http://nitecruzr.blogspot.com/2007/06/autotuning-in-vista-maybe-not-ready-for.html>
http://nitecruzr.blogspot.com/2007/06/autotuning-in-vista-maybe-not-ready-for.html

What's the exact title of the other thread? Is it in this forum?

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Yes, the thread I'm referring to is in this forum, and in this same
discussion group. The exact title is "Very strange problem networking Vista"
and was discussed at the beginning of january.

Although I'm on the brink of solving my problems, I have been thwarted by
the router refusing to upgrade to the latest realease I need. Oh well . . .
 
I've managed to upgrade the router to 6.2.29.2 and it has fixed the problem.
Excellent!
Click to expand...

Yeah!

Firmware upgrade is the ticket!

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Back
Top