problem mounting NT share

2000-03-02 Thread Brian J. Stults
My university just switched from Novell servers to NT.  There are two
servers containing discs to which I have access.  One of them gave me no
trouble at all.  I used this command to mount the shared drive:

smbmount //server1/shared /mountpoint.  

However, I could not get the drive on the other server mounted.  My
username and password are identical for both, and I can mount both
easily from Windows98.  The sysadmin knows nothing of linux, but did
suggest one possible difference between the two servers that might be
causing the problem.  He said the first server, which I don't have
trouble with, is a domain hosted server, or something like that. 
While the one that I am having trouble with is a stand alone server,
or something like that.  Sorry, but I know absolutely nothing about
Windows NT.  He also suggested that I explicitly pass my username and
that I use GROUPNAME/USERNAME as my username rather then simply
USERNAME.  That didn't work, but I thought it might give you a better
idea of what he thinks the problem is.

Any ideas?  Thanks.
-- 

Brian J. Stults
Doctoral Candidate
Department of Sociology
University at Albany - SUNY
Phone: (518) 442-4652  Fax: (518) 442-4936
Web: http://www.albany.edu/~bs7452


Re: problem mounting NT share

2000-03-02 Thread Sebastian Canagaratna
Here is how I do it:

smbmount-2.1.x //machine/drive -U username -W networkname -c 'mount
/mntpoint -u 1000 -g 1000' 

My university is onu.edu so for network name I use onu.

This works. There may be other ways of getting it to work too.
The W is for the workgroup. You will have to know what the workgroup
is.

Hope this helps
Sebastian Canagaratna
Department of Chemistry
Ohio Northern University
Ada, OH 45810
 My university just switched from Novell servers to NT.  There are two
 servers containing discs to which I have access.  One of them gave me no
 trouble at all.  I used this command to mount the shared drive:
 
 smbmount //server1/shared /mountpoint.  
 
 However, I could not get the drive on the other server mounted.  My
 username and password are identical for both, and I can mount both
 easily from Windows98.  The sysadmin knows nothing of linux, but did
 suggest one possible difference between the two servers that might be
 causing the problem.  He said the first server, which I don't have
 trouble with, is a domain hosted server, or something like that. 
 While the one that I am having trouble with is a stand alone server,
 or something like that.  Sorry, but I know absolutely nothing about
 Windows NT.  He also suggested that I explicitly pass my username and
 that I use GROUPNAME/USERNAME as my username rather then simply
 USERNAME.  That didn't work, but I thought it might give you a better
 idea of what he thinks the problem is.
 
 Any ideas?  Thanks.
 -- 
 
 Brian J. Stults
 Doctoral Candidate
 Department of Sociology
 University at Albany - SUNY
 Phone: (518) 442-4652  Fax: (518) 442-4936
 Web: http://www.albany.edu/~bs7452
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null
 
 
 


Re: problem mounting NT share

2000-03-02 Thread aphro
turn up debugging in samba and include it in your post it makes it VERY
difficult to debug with just it wont work in the email.

nate

On Thu, 2 Mar 2000, Brian J. Stults wrote:

bs7452 My university just switched from Novell servers to NT.  There are two
bs7452 servers containing discs to which I have access.  One of them gave me no
bs7452 trouble at all.  I used this command to mount the shared drive:
bs7452 
bs7452 smbmount //server1/shared /mountpoint.  
bs7452 
bs7452 However, I could not get the drive on the other server mounted.  My
bs7452 username and password are identical for both, and I can mount both
bs7452 easily from Windows98.  The sysadmin knows nothing of linux, but did
bs7452 suggest one possible difference between the two servers that might be
bs7452 causing the problem.  He said the first server, which I don't have
bs7452 trouble with, is a domain hosted server, or something like that. 
bs7452 While the one that I am having trouble with is a stand alone server,
bs7452 or something like that.  Sorry, but I know absolutely nothing about
bs7452 Windows NT.  He also suggested that I explicitly pass my username and
bs7452 that I use GROUPNAME/USERNAME as my username rather then simply
bs7452 USERNAME.  That didn't work, but I thought it might give you a better
bs7452 idea of what he thinks the problem is.
bs7452 
bs7452 Any ideas?  Thanks.
bs7452 -- 
bs7452 
bs7452 Brian J. Stults
bs7452 Doctoral Candidate
bs7452 Department of Sociology
bs7452 University at Albany - SUNY
bs7452 Phone: (518) 442-4652  Fax: (518) 442-4936
bs7452 Web: http://www.albany.edu/~bs7452
bs7452 
bs7452 
bs7452 -- 
bs7452 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null
bs7452 

[mailto:[EMAIL PROTECTED] ]--
   Vice President Network Operations   http://www.firetrail.com/
  Firetrail Internet Services Limited  http://www.aphroland.org/
   Everett, WA 425-348-7336http://www.linuxpowered.net/
Powered By:http://comedy.aphroland.org/
Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/
-[mailto:[EMAIL PROTECTED] ]--
8:33am up 195 days, 20:57, 1 user, load average: 1.10, 1.08, 1.06


Re: problem mounting NT share

2000-03-02 Thread Brian J. Stults
I've attached the debugging information...  Not sure what to include, so
I'm including everything.  

s2.txt is debugging for the share that I can mount, and s3.txt is
the debugging info for the share I cannot mount.  The response I get is:

session setup failed: ERRDOS - ERRnoaccess (Access denied.)
SMB connection failed

What seems strange to me is that from Windows98 both shares are mount
without problems using the same username and password.

Thanks again.
-- 

Brian J. Stults
Doctoral Candidate
Department of Sociology
University at Albany - SUNY
Phone: (518) 442-4652  Fax: (518) 442-4936
Web: http://www.albany.edu/~bs7452



aphro wrote:
 
 turn up debugging in samba and include it in your post it makes it VERY
 difficult to debug with just it wont work in the email.
 
 nate
 
 On Thu, 2 Mar 2000, Brian J. Stults wrote:
 
 bs7452 My university just switched from Novell servers to NT.  There are two
 bs7452 servers containing discs to which I have access.  One of them gave me 
 no
 bs7452 trouble at all.  I used this command to mount the shared drive:
 bs7452 
 bs7452 smbmount //server1/shared /mountpoint.
 bs7452 
 bs7452 However, I could not get the drive on the other server mounted.  My
 bs7452 username and password are identical for both, and I can mount both
 bs7452 easily from Windows98.  The sysadmin knows nothing of linux, but did
 bs7452 suggest one possible difference between the two servers that might be
 bs7452 causing the problem.  He said the first server, which I don't have
 bs7452 trouble with, is a domain hosted server, or something like that.
 bs7452 While the one that I am having trouble with is a stand alone server,
 bs7452 or something like that.  Sorry, but I know absolutely nothing about
 bs7452 Windows NT.  He also suggested that I explicitly pass my username and
 bs7452 that I use GROUPNAME/USERNAME as my username rather then simply
 bs7452 USERNAME.  That didn't work, but I thought it might give you a better
 bs7452 idea of what he thinks the problem is.
 bs7452 
 bs7452 Any ideas?  Thanks.mount.smbfs started (version 2.0.6)
Initialising global parameters
params.c:pm_process() - Processing configuration file /etc/samba/smb.conf
Processing section [global]
doing parameter message command = /bin/sh -c '/usr/bin/linpopup %f %m %s; 
rm %s' 
doing parameter netbios name = ss3f129
doing parameter passwd program = /usr/bin/passwd
doing parameter workgroup = loganlab
doing parameter config file = /etc/samba/smb.conf
doing parameter printer = lp
doing parameter printing = bsd
doing parameter printcap name = /etc/printcap
doing parameter security = SERVER
doing parameter load printers = True
doing parameter hosts allow = 169.226.108.130 169.226.108.129 169.226.108.142 
169.226.108.98 169.226.108.92 169.226.108.147
doing parameter wins server = 169.226.25.32
doing parameter guest account = nobody
doing parameter log file = /var/log/samba-log.%m
doing parameter lock directory = /var/lock/samba
doing parameter encrypt passwords = yes
pm_process() returned Yes
load_client_codepage: loading codepage 850.
added interface ip=169.226.108.129 bcast=169.226.108.255 nmask=255.255.255.0
resolve_lmhosts: Attempting lmhosts lookup for name s2_casnet0x20
getlmhostsent: lmhost entry: 169.226.108.92 ss3f092 
getlmhostsent: lmhost entry: 169.226.108.98 ss3f098 
getlmhostsent: lmhost entry: 169.226.108.130 ss3f130 
getlmhostsent: lmhost entry: 169.226.108.129 ss3f129 
getlmhostsent: lmhost entry: 169.226.108.142 ss3f142 
resolve_hosts: Attempting host lookup for name s2_casnet0x20
resolve_wins: Attempting wins lookup for name s2_casnet0x20
bind succeeded on port 0
nmb packet from 169.226.25.32(137) header: id=9609 opcode=Query(0) response=No
header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=No
header: rcode=0 qdcount=1 ancount=0 nscount=0 arcount=0
question: q_name=S2_CASNET20 q_type=32 q_class=1
Sending a packet of len 50 to (169.226.25.32) on port 137
Received a packet of len 62 from (169.226.25.32) port 137
nmb packet from 169.226.25.32(137) header: id=9609 opcode=Query(0) response=Yes
header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes
header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
answers: nmb_name=S2_CASNET20 rr_type=32 rr_class=1 ttl=0
answers   0 char @.   hex 4000A9E21916
Got a positive name query response from 169.226.25.32 ( 169.226.25.22 )
Connecting to 169.226.25.22 at port 139
Sent session request
size=0
smb_com=0x0
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=0
smb_flg2=0
smb_tid=0
smb_pid=0
smb_uid=0
smb_mid=0
smt_wct=0
smb_bcc=0
 session request ok
size=91
smb_com=0x72
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=136
smb_flg2=1
smb_tid=0
smb_pid=3520
smb_uid=0
smb_mid=1
smt_wct=17
smb_vwv[0]=7 (0x7)
smb_vwv[1]=12803 (0x3203)
smb_vwv[2]=256 (0x100)
smb_vwv[3]=1024 (0x400)
smb_vwv[4]=17 (0x11)
smb_vwv[5]=0 (0x0)
smb_vwv[6]=256 (0x100)
smb_vwv[7]=0 (0x0)
smb_vwv[8]=0 (0x0)
smb_vwv[9]=64768 (0xFD00)
smb_vwv[10]=67 (0x43)