Allen, Michael B (RSCH)
Michael_B_Allen at ml.com
Thu Dec 28 04:58:43 GMT 2000
> -----Original Message-----
> From: Christopher R. Hertel [SMTP:crh at nts.umn.edu]
> > smb://[[domain/]user[:password]@][workgroup#][server[:port][/share[/path]]]
> The part I am trying to work out is this: except in the case of a trust
> relationship or browsing a specific workgroup/ntdomain, is the domain
> name ever required?
Yes. I think you are confusing my definitions of "domain" and "workgroup" in the URL spec above. I believe Simo interpreted it in the same way as myself as he corrected my original proposal to give the above.
In the above, "domain" is the authentication domain for a user and is vitally important. I cannot connect to a share here at work without specifying it. It is required in the PrimaryDomain field during session setup and used by the server to authenticate me(the client) with the domain controller. A "?" can be used in it's place to specify the default domain but it is often specified regardless. In this context this information is strictly bound to the username(and for that reason IMO should reside next to it in a URL). MS uses domain\username so to simply avoid the backslash we do domain/username. Think of the [[domain/]user[:password]@] as *prepending* authentication information into the URL.
The "workgroup#" is a special exception to the whole concept of URLs and is meant to deal specifically which Richards original issue. Steve has suggested several times that it has no business in the URL(and I tend to agree). It is _only for browsing_ under rare cases where the name of the workgroup of intrest is not the same as the authentication domain. It is a bastard stepchild. An orphan. The problem is where do you put the damn thing. My previous post targeted that issue and I think, at least Simo and I, felt that it could safely be prepended to the server name. In this way you can start a browsing session for you extra-special bastard stepchild of a workgroup with:
and then drill down by clicking on a server and then a share and then ...
More information about the samba-technical