I'm having much difficulty connecting to a shared directory on my xp home
machine from my vista home premium machine. The basic issue is that when I do
start->run->\\xpMachineName, I get the error message "A device attached to
the system is not functioning." There is no issue connecting to Vista shares
from xp, and I know name to address resolution is working as I can see the
correct IP address for my xp machine in the NetBT name table cache (nbtstat
-c).
I've done some Google research on the issue and have made a few attempts to
resolve it. Using the browstat utility, I noticed that the xp home machine
was the browser master, so I stopped the browser service on the xp machine
and ensured it was working on Vista. That seemed to work, but now I see the
following output from browstat status:
Status for domain WATERLOO on transport \Device\foobar
Browsing is active on domain.
Master browser name is: SERENITY
Master browser is running build 6000
1 backup servers retrieved from master SERENITY
\\SERENITY
Unable to retrieve server list from SERENITY: 1130
Looking up this error, it appears to be most commonly caused by Norton
Anti-virus which I do in fact have installed and would like to keep. The
suggested fix is to increase the IRPStackSize parameter in the registry. It
did not previously exist, but I created it and tried several values all the
way up to 50 (restarting each time) and saw no change.
Any ideas on other things to try? I'm not even sure the the browstat
reported issue is the root problem as I don't care whether browsing working
or not. I'm happy to connect using only start->run->computer name.
"Alex" <Alex@discussions.microsoft.com> wrote in message
newsB4F0930-0084-49C5-BA41-2A0110D9AAB5@microsoft.com...
> I'm having much difficulty connecting to a shared directory on my xp home
> machine from my vista home premium machine. The basic issue is that when I
> do
> start->run->\\xpMachineName, I get the error message "A device attached to
> the system is not functioning." There is no issue connecting to Vista
> shares
> from xp, and I know name to address resolution is working as I can see the
> correct IP address for my xp machine in the NetBT name table cache
> (nbtstat
> -c).
>
> I've done some Google research on the issue and have made a few attempts
> to
> resolve it. Using the browstat utility, I noticed that the xp home machine
> was the browser master, so I stopped the browser service on the xp machine
> and ensured it was working on Vista. That seemed to work, but now I see
> the
> following output from browstat status:
>
> Status for domain WATERLOO on transport \Device\foobar
> Browsing is active on domain.
> Master browser name is: SERENITY
> Master browser is running build 6000
> 1 backup servers retrieved from master SERENITY
> \\SERENITY
> Unable to retrieve server list from SERENITY: 1130
>
> Looking up this error, it appears to be most commonly caused by Norton
> Anti-virus which I do in fact have installed and would like to keep. The
> suggested fix is to increase the IRPStackSize parameter in the registry.
> It
> did not previously exist, but I created it and tried several values all
> the
> way up to 50 (restarting each time) and saw no change.
>
> Any ideas on other things to try? I'm not even sure the the browstat
> reported issue is the root problem as I don't care whether browsing
> working
> or not. I'm happy to connect using only start->run->computer name.
>
> Thanks,
>
> Alex
Meaning can I connect with \\IpAddress? That doesn't work either. I can,
however,
ping the xp machine just fine.
Some further information: I went ahead and tried uninstalling Norton
Internet Security and running the Norton Removal Tool, but this doesn't seem
to have made any difference.
Well, this is horribly embarrassing, but I've fixed the problem. It turned
out that file sharing was disabled for the wireless interface on the xp
computer. I guess this proves that too much knowledge isn't necessarily a
good thing. You get in a rut in thinking and miss the obvious.
The 1130 error reported by browstat status remains, but I guess it doesn't
matter since I can still connect to the other machine.
"Alex" <Alex@discussions.microsoft.com> wrote in message
news:799EF1C9-204C-4192-B4B0-D36F272B086C@microsoft.com...
> Well, this is horribly embarrassing, but I've fixed the problem. It turned
> out that file sharing was disabled for the wireless interface on the xp
> computer. I guess this proves that too much knowledge isn't necessarily a
> good thing. You get in a rut in thinking and miss the obvious.
>
> The 1130 error reported by browstat status remains, but I guess it doesn't
> matter since I can still connect to the other machine.
>
> Regards,
>
> Alex