samba - Apr 2003 - msdfs problems

I have setup samba with msdfs, and configured it.  The problem is that it
works with some windows 2000 workstations, but not with others, even if
they are at the same service pak levels.

I.e, I have workstation a and workstation b, both running 2000.  On
workstation a, I can map the dfs share to a drive, and be able to access
everything in that share (which is different shares on different servers).
On workstation b, I can map the dfs share to a drive, but I can't browse
or do anything with the dfs shares in the drive I just mapped. The error I
get from workstation b when I try to browse the shares, is something like
this:
"\\mydfsservername\dfs\folder1
The folder was moved or removed"
>From watching the samba logs, I've noticed that each time I try to click
on the folders under the dfs drive, many messages get logged, but
foremost, I see this:  NT_STATUS_OBJECT_PATH_NOT_FOUND

"[2003/04/23 17:39:06, 3] smbd/trans2.c:call_trans2qfilepathinfo(1707)
  call_trans2qfilepathinfo: check_name of prog failed (Error 0)
[2003/04/23 17:39:06, 3] smbd/error.c:error_packet(113)
  error packet at smbd/trans2.c(1709) cmd=50 (SMBtrans2)
NT_STATUS_OBJECT_PATH_NOT_FOUND
[2003/04/23 17:39:06, 5] lib/util.c:show_msg(275)"

That's what is logged when I try to  access the dfs shares from
workstation b.

Why would I have access and be able to see every thing from workstation a,
but no access to the same shares from workstation b, even if I don't
discriminate between the two workstations?  Such is the puzzle I'm working
with.

Any help will be appreciated.

thanks
robert

Robert,

Do you use different username/password pairs to log on to workstations a and
b?
>From what I remember, the username/password used to log on is used when
connecting to dfs links.

- Shirish

Robert Johannes wrote:

I have setup samba with msdfs, and configured it.  The problem is that it
works with some windows 2000 workstations, but not with others, even if
they are at the same service pak levels.

I.e, I have workstation a and workstation b, both running 2000.  On
workstation a, I can map the dfs share to a drive, and be able to access
everything in that share (which is different shares on different servers).
On workstation b, I can map the dfs share to a drive, but I can't browse
or do anything with the dfs shares in the drive I just mapped. The error I
get from workstation b when I try to browse the shares, is something like
this:
"\\mydfsservername\dfs\folder1
The folder was moved or removed"
>From watching the samba logs, I've noticed that each time I try to click
on the folders under the dfs drive, many messages get logged, but
foremost, I see this:  NT_STATUS_OBJECT_PATH_NOT_FOUND

"[2003/04/23 17:39:06, 3] smbd/trans2.c:call_trans2qfilepathinfo(1707)
  call_trans2qfilepathinfo: check_name of prog failed (Error 0)
[2003/04/23 17:39:06, 3] smbd/error.c:error_packet(113)
  error packet at smbd/trans2.c(1709) cmd=50 (SMBtrans2)
NT_STATUS_OBJECT_PATH_NOT_FOUND
[2003/04/23 17:39:06, 5] lib/util.c:show_msg(275)"

That's what is logged when I try to  access the dfs shares from
workstation b.

Why would I have access and be able to see every thing from workstation a,
but no access to the same shares from workstation b, even if I don't
discriminate between the two workstations?  Such is the puzzle I'm working
with.

Any help will be appreciated.

thanks
robert

Sorry, but afraid the logs aren't clean; I need logs that start from the
point a workstation makes a TCP connection to Samba. The log indicates
that the client is navigating the share using non-DFS requests. It could
either be something in the negotiation phase (missed by the log), or
some setting on the client itself.

Could you do this:
1. Power down the client.
2. Kill smbd on the server and remove all log files.
3. Start smbd on the server.
4. Power up the client.
5. Connect to the dfs share and then 'cd' into the folder1.
6. Send me the level 10 log generated.

If this is a production server and you can't do this, we'll have to do
this in a different way, let me know.

Thanks,
Shirish

On Tue, 29 Apr 2003, Robert Johannes wrote:
>Enclosed are the files you requested for.  It is one file, that's about
>19k gzipped.  It includes all the files you requested.
>
>robert
>
>On Tue, 29 Apr 2003, Shirish Kalele wrote:
>
>> Could you send me a level 10 log containing only the following
operations:
>> 1. map \\dfsservername\dfs from workstation B
>> 2. attempt to 'cd' to folder1 under the mapped drive.
>>
>> Steps 1 and 2 from workstation A.
>>
>> Could you also send me your smb.conf file.
>>
>> Thanks,
>> Shirish
>>
>> On Tue, 29 Apr 2003, Robert Johannes wrote:
>>
>> >In your scenario below, yes, I can map \\server\share to a drive
letter on
>> >workstation b, but I still can't map or access
\\dfsservername\dfs\folder1
>> >on the same workstation.
>> >
>> >Is there a way to turn up logging on the win2000 workstations so I
can
>> >capture what the workstation is saying while communicating with the
samba
>> >server?  Are workstations sensitive to naming issues with share
names,
>> >character length, e.t.c?
>> >
>> >robert
>> >
>> >On Mon, 28 Apr 2003, Shirish Kalele wrote:
>> >
>> >> Let me rephrase:
>> >>
>> >> If your link \\dfsservername\dfs\folder1 points to
\\server\share, can you
>> >> map it (\\server\share) directly from workstation B? And after
mapping it
>> >> as a separate drive letter, can you access
\\mydfsservername\dfs\folder1
>> >> from that workstation (B)?
>> >>
>> >> - Shirish
>> >>
>> >> On Mon, 28 Apr 2003, Robert Johannes wrote:
>> >>
>> >> >I can't directly map the dfs link.  I can map to the
dfs parent though
>> >> >(i.e, \\mydfsservername\dfs, but not
\\mydfsservername\dfs\folder1).
>> >> >
>> >> >I'm kind of at a dead-end with this, since snoop and
the logs have not
>> >> >revealed much that I would consider to aid in the
resolution of this
>> >> >problem.
>> >> >
>> >> >robert
>> >> >
>> >> >On Mon, 28 Apr 2003, Shirish Kalele wrote:
>> >> >
>> >> >> And can you map the dfs link directly from the
workstation?
>> >> >>
>> >> >> If you can, can you browse the link from the dfs tree
after mapping the
>> >> >> link separately (as a drive letter)?
>> >> >>
>> >> >> - SK
>> >> >>
>> >> >> >>
>> >> >> >> Do you use different username/password pairs
to log on to workstations a and
>> >> >> >> b?
>> >> >> >>
>> >> >> >> >From what I remember, the
username/password used to log on is used when
>> >> >> >> connecting to dfs links.
>> >> >> >>
>> >> >> >> - Shirish
>> >> >> >>
>> >
>>
>>
>
>