home lan puzzler

[Harry Putnam]

Setup: 3 winxp boxes
1 linux
1 winxp on laptop

All above are hooked up on home network the 3 desktop winxp boxes all
run windowsxp pro.

I'm seeing a sort of baffling problem that I'm not sure when nor how
it started.

The shares that are setup can be connected to from 2 and 3 just fine.
The baffling part is 2 and 3 when connected to 1 cannot see inside
certain folders. The folders can be access and files moved or removed
but the files cannot be seen.

I get no error messages to include here. Even setting up a mapped
drive on mach3 in explorer I see the main directory but nothing
inside.

If I type a share address into explorer like

\\mach1\mach1-share\folder\subfolder

Explorer opens them fine. But the files are invisible.

I've seen this phenomena mentioned on the windows xp newsgroups before
but don't recall seeing a resolution.

I'm coming from a unix backgroud and have grown accustomed to network
connections that are reliable and straight forward.

Somehow it seems on a windows home lan things get changed and
sometimes don't work properly for no apparent reason.

I imagine that is just that I don't know where to look.


I recently brought mach1 up to date on sp2. Haven't noticed any
particular problems but I believe the problem discussed here was
already going on before the update.

 

[Malke]

Setup: 3 winxp boxes
1 linux
1 winxp on laptop

All above are hooked up on home network the 3 desktop winxp boxes all
run windowsxp pro.

I'm seeing a sort of baffling problem that I'm not sure when nor how
it started.

The shares that are setup can be connected to from 2 and 3 just fine.
The baffling part is 2 and 3 when connected to 1 cannot see inside
certain folders. The folders can be access and files moved or removed
but the files cannot be seen.

I get no error messages to include here. Even setting up a mapped
drive on mach3 in explorer I see the main directory but nothing
inside.

If I type a share address into explorer like

\\mach1\mach1-share\folder\subfolder

Explorer opens them fine. But the files are invisible.

I've seen this phenomena mentioned on the windows xp newsgroups before
but don't recall seeing a resolution.

I'm coming from a unix backgroud and have grown accustomed to network
connections that are reliable and straight forward.

Somehow it seems on a windows home lan things get changed and
sometimes don't work properly for no apparent reason.

I imagine that is just that I don't know where to look.


I recently brought mach1 up to date on sp2. Haven't noticed any
particular problems but I believe the problem discussed here was
already going on before the update.

On the XP boxen, are you running XP Home or Pro? Home doesn't allow you
to share out the user's home folder (My Documents) or the Program Files
folder, although you can share out subfolders in Program Files. If this
is your case, then try using the Shared Documents folder instead.

Here are my notes on the issue of problems after a particular MS update
which may be what you are thinking of:

KB885250, an update from 2/8/2005 can cause file and printer sharing
problems under Windows networking and SAMBA. It has been reported that
both SP1 and SP2 boxen are affected. If your attempt to use SMB shares
seems compromised after last week's hotfixes, remove KB885250.

See this MS Knowledge Base article:
http://www.microsoft.com/technet/security/bulletin/ms05-011.mspx

Check in the section "Vulnerability Details, Workarounds" for several
approaches to providing the protection of the hotfix without using the
hotfix.

Those notes are a bit old by now, so the update may have been fixed. I
have a mix of XP Pro, one XP Home, and Linux boxen on my networks and
am able to share files with no problems - taking the limitations of XP
Home into account. FWIW, my XP boxen are all SP2 and completely
updated, including KB885250.

If this information didn't help, post back with more details regarding
what version of XP each box is running, if your network setup ever
worked properly, etc.

If the problem is only on the XP boxen (i.e., sharing works fine from
Linux so you know the Samba server is OK), you might try running XP's
Network Setup Wizard again on all the XP boxen. When you do this, have
all the computers on. Then run the Wizard on each box, watching for the
change in Workgroup name (it will default to MSHOME) so you can change
it. You will then need to shut down all the XP boxen and restart them.
Disable the Windows Firewall if you are using third-party software
because the Wizard will automatically enable it. If you are using the
Windows Firewall, make sure it is properly configured for file sharing
during this process.

Malke

 

[Harry Putnam]

On the XP boxen, are you running XP Home or Pro? Home doesn't allow you
to share out the user's home folder (My Documents) or the Program Files
folder, although you can share out subfolders in Program Files. If this
is your case, then try using the Shared Documents folder instead.

Harry quotes original post:

Here are my notes on the issue of problems after a particular MS update
which may be what you are thinking of:

Harry quotes OP:

If this information didn't help, post back with more details regarding
what version of XP each box is running, if your network setup ever
worked properly, etc.

See above regarding version info.
concerning your point about if it ever worked... yes it did. And not
long ago either. As mentioned in OP. I don't think the sp2 upgrade
is the problem since my issue was happing before the upgrade.

If the problem is only on the XP boxen (i.e., sharing works fine from
Linux so you know the Samba server is OK), you might try running XP's
Network Setup Wizard again on all the XP boxen. When you do this, have
all the computers on. Then run the Wizard on each box, watching for the
change in Workgroup name (it will default to MSHOME) so you can change
it. You will then need to shut down all the XP boxen and restart them.
Disable the Windows Firewall if you are using third-party software
because the Wizard will automatically enable it. If you are using the
Windows Firewall, make sure it is properly configured for file sharing
during this process.

Good idea, thanks. I'll try that out and report back.

 

[Harry Putnam]

Good idea, thanks. I'll try that out and report back.

I've established that the samba smbclient can access all windows xp
boxes. Further I can use samba (sambafs) to mount the drives in
question and access them from the linux box as well.

No files are invisible as in the case I described.

I have yet to run the wizard on all winxp pro boxes ... still working

 

[Malke]

I've established that the samba smbclient can access all windows xp
boxes. Further I can use samba (sambafs) to mount the drives in
question and access them from the linux box as well.

No files are invisible as in the case I described.

I have yet to run the wizard on all winxp pro boxes ... still working

Harry, where are the invisible files? In which folders? Would there be
any reason for those particular folders to be hidden? Can you give more
description about this?

The only other recent thing I've seen reported about files/folders being
hidden in a network after a Windows Update had to do with Windows 98
files (after an XP update, I believe). Since you don't have any Win98
machines, this doesn't seem applicable.

Maybe if we approach the problem from what folders are "invisible", that
will help.

Malke

 

[Harry Putnam]

I've established that the samba smbclient can access all windows xp
boxes. Further I can use samba (sambafs) to mount the drives in
question and access them from the linux box as well.

No files are invisible as in the case I described.

I have yet to run the wizard on all winxp pro boxes ... still working

I've now run the network wizard on all three winxp pro boxes.

One result was that the problematic box now sees all players in
network places display (entire network/etc/etc/)

However, from that particular machine files inside some directories
are in visible. All drives in question have the same sharing
settings.

==
User1 user2 and SYSTEM have full control
==

User1 and 2 are accounts with same name and permissions on all
machines.

I'm thinking the fact that some files are invisible is telling us
something but I can't quite grasp what.

 

[Malke]

I've now run the network wizard on all three winxp pro boxes.

One result was that the problematic box now sees all players in
network places display (entire network/etc/etc/)

However, from that particular machine files inside some directories
are in visible. All drives in question have the same sharing
settings.

==
User1 user2 and SYSTEM have full control
==

User1 and 2 are accounts with same name and permissions on all
machines.

I'm thinking the fact that some files are invisible is telling us
something but I can't quite grasp what.

OK, let's clarify: the problem is that (pick one):

a. From an XP box you can't see files in a Linux directory;
b. From a Linux box you can't see files in an XP directory;
c. From an XP box you can't see files in an XP directory.

And what - and where - are the files? Are all the files the same?

Malke

 

[Harry Putnam]

I must have a totally confusing style I guess. Sorry if it seems to
be overly obfuscated... it isn't really.

OK, let's clarify: the problem is that (pick one):

a. From an XP box you can't see files in a Linux directory;

Throw all thoughts about linux out right here. It isn't involved
here. Only maybe to test something or the like. Introducing the linux
box into the equation seems to be adding mucho confusion.

b. From a Linux box you can't see files in an XP directory;

See above.
But .. yes I can see them from a linux box.

c. From an XP box you can't see files in an XP directory.
Bingo.

And what - and where - are the files? Are all the files the same?

These are totally normal files ranging from simple text to ghosted
images. There is nothing special about them.

In this scheme all boxes are running winxp pro sp/2.
mach1 is where the files in question are located at:

E:\bk1\ghost-bk1 has an assortment of files
*.txt *.html *. and two directories under it.

None of this is visible from mach2 or mach3. Both can navigate
explorer to E:\bk1\ghost-bk1 as:

\\mach1\mach1-e\bk1\ghost-bk1

But no files are visible in that directory, viewed from the remote
hosts mach2 and mach3

In fact if I navigate from Network Places on mach2 or mach3 like:

entire network/Microsoft windows network/home/

I see mach2 and mach3 but not mach1.

However the network shares I've created over the months to mach1 from
mach2 and mach3 still work with addresses like:
\\mach1\mach1-c\Program Files\
or \\mach1\mach1-d\dir\subdir\

And do display all files there.

But not so for \\mach1\mach1-e\bk1\ghost-bk1\
or \\mach1\mach1-h\bk2\ghost-bk2\

I have been able to see this stuff in the past infact most of the
images located there were placed there thru the network running ghost
on mach2 and mach3. Backed up their drives and placed the images on mach1
thru the ethernet wire as it is being compressed compiled.

I can't figure out what is changed.

Hopefully above will clarify my problem ...
I'm going to reboot everything for the umpteenth time and see if it
helps.

 

[Malke]

I must have a totally confusing style I guess. Sorry if it seems to
be overly obfuscated... it isn't really.

It is just that because you've been working with this for a while and
you have the network/machines in front of you so that things are very
clear in your mind. I just wasn't "seeing" it. Sorry.

Throw all thoughts about linux out right here. It isn't involved
here. Only maybe to test something or the like. Introducing the linux
box into the equation seems to be adding mucho confusion.

Yes, because I thought you were asking about interoperability problems.

These are totally normal files ranging from simple text to ghosted
images. There is nothing special about them.

In this scheme all boxes are running winxp pro sp/2.
mach1 is where the files in question are located at:

E:\bk1\ghost-bk1 has an assortment of files
*.txt *.html *. and two directories under it.

None of this is visible from mach2 or mach3. Both can navigate
explorer to E:\bk1\ghost-bk1 as:

\\mach1\mach1-e\bk1\ghost-bk1

But no files are visible in that directory, viewed from the remote
hosts mach2 and mach3

In fact if I navigate from Network Places on mach2 or mach3 like:

entire network/Microsoft windows network/home/

I see mach2 and mach3 but not mach1.

However the network shares I've created over the months to mach1 from
mach2 and mach3 still work with addresses like:
\\mach1\mach1-c\Program Files\
or \\mach1\mach1-d\dir\subdir\

And do display all files there.

But not so for \\mach1\mach1-e\bk1\ghost-bk1\
or \\mach1\mach1-h\bk2\ghost-bk2\

I have been able to see this stuff in the past infact most of the
images located there were placed there thru the network running ghost
on mach2 and mach3. Backed up their drives and placed the images on
mach1 thru the ethernet wire as it is being compressed compiled.

I can't figure out what is changed.

Hopefully above will clarify my problem ...
I'm going to reboot everything for the umpteenth time and see if it
helps.

I doubt that rebooting will work in this case. I honestly don't know the
answer, but have a couple of suggestions. I Googled for "browse with
UNC names works" and got this link which looks promising:

http://www.chicagotech.net/nettroublshooting.htm

A workaround which I got from MVP Steve Winograd (networking guru
extraordinaire) when I was having problems with my own network was to
forget about using Network Places. Instead, I used Search to search for
computers on the network and made shortcuts to the shares. I put mine
in a folder in my desktop and they worked perfectly, even when Network
Places would crash and lock up the whole machine. However, I wasn't
having the same problem as you with "invisible" files. I was having the
problem of not all computers showing on the network and running the
Network Setup Wizard the way I detailed earlier solved it for me. Like
you, I had no idea why something that was working perfectly stopped
doing that. I still don't know. ;-)

So I'm sorry I don't have a definitive answer for you.

Best of luck,

Malke

 

[AJR]

Are NTFS permissions involved - or just share (FAT - simple file sharing)
permissions? Can you access "invisible" files by UNC? May not be the
problem but as you are probably aware NTFS permission propagation to folder
files can be denied.

 

[Malke]

Are NTFS permissions involved - or just share (FAT - simple file
sharing)
permissions? Can you access "invisible" files by UNC? May not be the
problem but as you are probably aware NTFS permission propagation to
folder files can be denied.

That's a really good point - like maybe the right permissions aren't on
the child folders. But wouldn't he get an "access denied" error instead
of just not being able to see the files? I'm asking - I don't know the
answer.

Malke

 

[Harry Putnam]

Are NTFS permissions involved - or just share (FAT - simple file sharing)
permissions? Can you access "invisible" files by UNC? May not be the
problem but as you are probably aware NTFS permission propagation to folder
files can be denied.

That's a really good point - like maybe the right permissions aren't on
the child folders. But wouldn't he get an "access denied" error instead
of just not being able to see the files? I'm asking - I don't know the
answer.

Malke's point was my take as well. Yes the folders are accessable by
Unc. But again, files at:

\\Remote\share\subdir\HERE are invisible.

A reboot all around has made some changes as detailed below but still
not just working like it should.

Just now, thoroughly checking all three machines I see differences
amongst them.

mach1 (host with the subject )files

A) Mach1
1) Mach1 does not appear in its own Network places at
`Entire Netowrk\Microsoft...\Home <= clicking home gets a `unavailable [...]'
message.

Going by UNC \\chub\chub-e\bk1\ghost-bk1\etc etc

I can get to all of them nothing is hidden or invisible.
2) Now trying Entire Network\microsoft...\home works as it should

A further note is that working thru Network Places on mach1 is very
slow .. more so than the other two.

B) Mach2
1) Using mach2 `network places'
Entire Network\Microsoft...\Home\HERE
Mach1 is not visible but Mach2 anb 3 are.

2) Using UNC I can get to all files under \\chub\chub-e\bk1

Close explorer and open a new explorer and again at Netowrk Places
Mach1 is not visible at Entire Network\Microsoft...\Home

3) Mach3

Mach3 Network Places shows
Entire Network\Microsoft...\Home\HERE
Mach1 is not visible but Mach2 and mach3 are.

Using UNC addressing I can get to everything


Further NOTE:
Using the `Search for computer' on the search menu. from Mach3
mach1 is readily found and all under it appear.



This all seems pretty flaky. There must still be something wrong at
mach1.

Someone mentioned properties or permission propagation.

What I see is that all subdir under any share .. not just the ones
I'm having trouble with, when viewed at right click \Sharing:

Universally on all machines the `do not share' button is selected.

This is true whether or not I'm able to navigate to them from anywhere
on the network.

 

[Chuck]

Are NTFS permissions involved - or just share (FAT - simple file sharing)
permissions? Can you access "invisible" files by UNC? May not be the
problem but as you are probably aware NTFS permission propagation to folder
files can be denied.

That's a really good point - like maybe the right permissions aren't on
the child folders. But wouldn't he get an "access denied" error instead
of just not being able to see the files? I'm asking - I don't know the
answer.

Malke's point was my take as well. Yes the folders are accessable by
Unc. But again, files at:

\\Remote\share\subdir\HERE are invisible.

A reboot all around has made some changes as detailed below but still
not just working like it should.

Just now, thoroughly checking all three machines I see differences
amongst them.

mach1 (host with the subject )files

A) Mach1
1) Mach1 does not appear in its own Network places at
`Entire Netowrk\Microsoft...\Home <= clicking home gets a `unavailable [...]'
message.

Going by UNC \\chub\chub-e\bk1\ghost-bk1\etc etc

I can get to all of them nothing is hidden or invisible.
2) Now trying Entire Network\microsoft...\home works as it should

A further note is that working thru Network Places on mach1 is very
slow .. more so than the other two.

B) Mach2
1) Using mach2 `network places'
Entire Network\Microsoft...\Home\HERE
Mach1 is not visible but Mach2 anb 3 are.

2) Using UNC I can get to all files under \\chub\chub-e\bk1

Close explorer and open a new explorer and again at Netowrk Places
Mach1 is not visible at Entire Network\Microsoft...\Home

3) Mach3

Mach3 Network Places shows
Entire Network\Microsoft...\Home\HERE
Mach1 is not visible but Mach2 and mach3 are.

Using UNC addressing I can get to everything


Further NOTE:
Using the `Search for computer' on the search menu. from Mach3
mach1 is readily found and all under it appear.



This all seems pretty flaky. There must still be something wrong at
mach1.

Someone mentioned properties or permission propagation.

What I see is that all subdir under any share .. not just the ones
I'm having trouble with, when viewed at right click \Sharing:

Universally on all machines the `do not share' button is selected.

This is true whether or not I'm able to navigate to them from anywhere
on the network.

Harry,

Do us a favour please and provide some diagnostics to go on - "ipconfig /all"
and "browstat status" from each computer would be good.
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

Maybe you will find some help here too:
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

 

[Malke]

Are NTFS permissions involved - or just share (FAT - simple file
sharing)
permissions? Can you access "invisible" files by UNC? May not be the
problem but as you are probably aware NTFS permission propagation to
folder files can be denied.

That's a really good point - like maybe the right permissions aren't
on the child folders. But wouldn't he get an "access denied" error
instead of just not being able to see the files? I'm asking - I don't
know the answer.

Malke's point was my take as well. Yes the folders are accessable by
Unc. But again, files at:

\\Remote\share\subdir\HERE are invisible.

A reboot all around has made some changes as detailed below but still
not just working like it should.

Just now, thoroughly checking all three machines I see differences
amongst them.

mach1 (host with the subject )files

A) Mach1
1) Mach1 does not appear in its own Network places at
`Entire Netowrk\Microsoft...\Home <= clicking home gets a
`unavailable [...]' message.

Going by UNC \\chub\chub-e\bk1\ghost-bk1\etc etc

I can get to all of them nothing is hidden or invisible.
2) Now trying Entire Network\microsoft...\home works as it should

A further note is that working thru Network Places on mach1 is very
slow .. more so than the other two.

B) Mach2
1) Using mach2 `network places'
Entire Network\Microsoft...\Home\HERE
Mach1 is not visible but Mach2 anb 3 are.

2) Using UNC I can get to all files under \\chub\chub-e\bk1

Close explorer and open a new explorer and again at Netowrk Places
Mach1 is not visible at Entire Network\Microsoft...\Home

3) Mach3

Mach3 Network Places shows
Entire Network\Microsoft...\Home\HERE
Mach1 is not visible but Mach2 and mach3 are.

Using UNC addressing I can get to everything


Further NOTE:
Using the `Search for computer' on the search menu. from Mach3
mach1 is readily found and all under it appear.



This all seems pretty flaky. There must still be something wrong at
mach1.

Someone mentioned properties or permission propagation.

What I see is that all subdir under any share .. not just the ones
I'm having trouble with, when viewed at right click \Sharing:

Universally on all machines the `do not share' button is selected.

This is true whether or not I'm able to navigate to them from anywhere
on the network.

The above bit about the "do not share" being selected is very strange.
I'd try (and we're just talking about the Windows machines; leave the
Linux boxen alone):

1. *Un*share everything. Reboot.

2. On all the XP Pro boxen, go to the View tab in Folder Options and
uncheck "use Simple Sharing". This thread has gotten long, so I'm
assuming that you've already and long ago made identical user accounts
and passwords on all machines.

3. With all machines on, run the Network Setup Wizard on all machines
again. Watch for the "MSHOME gotcha" and be sure to select Share Files
& Folders. Reboot. Check the Windows Firewall settings and if you are
using it, make sure it is set to allow your lan. If you are not using
WF, make sure it is OFF and your third-party firewall is set to allow
your lan.

Now see whether All Is Well.

If it isn't, take a deep cleansing breath and whatever Adult
Beverage/Drug you prefer and make shortcuts to the shares with the
Search thing I suggested earlier.

Let me know what happens.

Malke

 

[Harry Putnam]

Do us a favour please and provide some diagnostics to go on - "ipconfig /all"

None of my machines know anything about the `browstatus status'

command or any variation I could come up with:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>browstatus status
'browstatus' is not recognized as an internal or external command,
operable program or batch file.

C:\>==========================

I can't think of a good reason to publish my hardware and IP addresses
here so only included the top half Which is the same for all machines
except the name:

=============================
C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : ansil

Three differnet names of course

Primary Dns Suffix . . . . . . . : local.net0
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local.net0

All three appear the same on second half as well with exception nof
hardware and IP addresses.

The above bit about the "do not share" being selected is very strange.
I'd try (and we're just talking about the Windows machines; leave the
Linux boxen alone):

Wait.. are you saying that if you pick a subfolder under a share and
click on Sharing/security It shows something besides:

[x]Do not share this folder

Being checked?

All my machines show the `Do not etc' on all subfolders under shares.

1. *Un*share everything. Reboot.

OK, will do, but it will be a few hours after doing some driving around
chores I need to get done.

 

[Chuck]

Do us a favour please and provide some diagnostics to go on - "ipconfig /all"

None of my machines know anything about the `browstatus status'

command or any variation I could come up with:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>browstatus status
'browstatus' is not recognized as an internal or external command,
operable program or batch file.

Harry,

Try "browstat status" please. But download browstat first - follow instructions
here.
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

 

[Harry Putnam]

Try "browstat status" please. But download browstat first - follow instructions
here.
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

(Note: READER is a linux box on this network running samba)
(Note: All winxp pro machines show the same error)

Mach1 (chub) Where subject files are located:

browstat status:
Status for domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}

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

Mach2 (harvey)

Browstat status:

Status for domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}

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

Mach3 (Ansil)

Status for domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}

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

 

[Harry Putnam]

Harry,

Try "browstat status" please. But download browstat first - follow
instructions here.
<http://nitecruzr.blogspot.com/2005/05/getting-access-denied-in-network.html#WhatToDoNow>

I've done this and posted the results. Please note that I am not
getting the error your link discusses.

 

[Chuck]

(Note: READER is a linux box on this network running samba)
(Note: All winxp pro machines show the same error)

Mach1 (chub) Where subject files are located:

browstat status:
Status for domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{4AF29430-11AA-4F44-9E77-EE00279AC7EE}

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

Mach2 (harvey)

Browstat status:

Status for domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{994106B3-3846-46FE-943B-ADE0520D3F69}

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

Mach3 (Ansil)

Status for domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
Browsing is active on domain.
Master browser name is: READER
Could not open key in registry, error = -1073741809 Unable to determine build of browser master: -1073741809
\\\\READER . Version:04.09 Flags: 9a03 NT SERVER
1 backup servers retrieved from master READER
\\READER
There are 3 servers in domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}
There are 1 domains in domain HOME on transport \Device\NetBT_Tcpip_{4EABAEF3-C4ED-45C8-BAF7-81D2DA968269}

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

OK, so we're back to Samba involved.

So far, I see 3 symmetrical browstats, only NBT transports. No obvious
problems.

I still have no idea of the scope of the problem, and without the ipconfigs I
doubt that I will. What we were going to do with the ipconfigs is run CDiag,
which might show us a pattern / scope of symptoms anyway. You're welcome to run
CDiag yourself, and describe any discrepancies found, without revealing details.
I'll coach you as much as I can.
<http://nitecruzr.blogspot.com/2005/05/what-is-cdiag-comprehensive-diagnosis.html>

--
Cheers,
Chuck
http://nitecruzr.blogspot.com/
Paranoia is not necessarily a bad thing - it's a normal response from experience.
My email is AT DOT
actual address pchuck sonic net.

 

[Harry Putnam]

Chuck,
I'm not sure if this is noteworthy but I'm noticing that running

`net view' on all winxp pro machines fails to display the subject
machine. (chub)

The interesting part is that running:

net view chub
(on any of the winxp pro)

Displays all of chubs shares.

net view:
Server Name Remark

-------------------------------------------------------------------------------
\\ANSIL
\\HARVEY
\\READER Samba 3.0.10
The command completed successfully.
======================================

net view chub:
Shared resources at chub



Share name Type Used as Comment

-------------------------------------------------------------------------------
chub-a Disk
chub-bk1 Disk
chub-bk2 Disk
chub-c Disk
chub-d Disk
chub-dvdb Disk sony dui 330
chub-e Disk sata1_0
chub-g Disk sata2_0
chub-h Disk
chub-printer Print HP Mult-ifunction 7130
chub_02 Disk
E Disk
F Disk
harvey_22 Disk
IDE1_bad Disk
Printer Print hp officejet 7100 series fax
Printer2 Print SnagIt 7
SharedDocs Disk
The command completed successfully.