Thread View: csu.unix.linux
5 messages
5 total messages
Started by vishwanath parakala
Wed, 09 Feb 2000 00:00
Smb.conf
Author: vishwanath parakala
Date: Wed, 09 Feb 2000 00:00
Date: Wed, 09 Feb 2000 00:00
33 lines
1198 bytes
1198 bytes
Hey .. does anyone have an idea what's wrong with my smb.conf ... I'm unable to access it from Windoze machines .... [global] keep alive=30 os level=2 security=share guest account=nobody printing=bsd printcap name=/etc/printcap load printers=yes workgroup=WORKGROUP [homes] create mode=0750 browseable=no comment=homedirectory read only=no [printers] comment=All Printers browseable=no printable=yes public=no read only=yes create mode=0700 directory=/tmp -- VISHWANATH PARAKALA __________________________________________________________________________ Home Page: http://www.cs.colostate.edu/~vishu finger : vishu@miller.cs.colostate.edu
Re: Smb.conf
Author: Adam Carheden
Date: Thu, 10 Feb 2000 00:00
Date: Thu, 10 Feb 2000 00:00
80 lines
3167 bytes
3167 bytes
Well, workgroup is set to WORKGROUP. You might want to change that to
whatever workgroup/domain your windows machines are using. Also, try
setting a netbios name such as 'netbios name = myWinMachineName'. If
you have an NT server on your local net, you might want to 'wins server
= 129.82.ntmachine.ip' For security reasons, you might also want to add
the following line: 'hosts allow = 129.82. 127.' This would limit
connections to IP that start with those octets (csu and loopback). The
trailing . are important.
The easiest way to do stuff is to use SWAT, the Samba Web Administration
Tool which is installed with samba as a web server on port 901. Go to
http://samba.server.ip.addr:901 and log in as root. You can then modify
smb.conf using a nice gui interface.
--
Adam Carheden
carheden@holly.ColoState.EDU
Here's my smb.conf if you want to take a look:
# Samba config file created using SWAT
# from dialup0028.PPP.ColoState.EDU (129.82.52.127)
# Date: 2000/02/10 08:17:54
# Global parameters
[global]
workgroup = CNHP
netbios name = FTP
netbios aliases = walrus
server string = CNHP Samba Server
security = SERVER
password server = OTTER
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
add user script = /usr/local/samba/bin/addsmbusr %u
dns proxy = No
wins server = 129.82.197.251
hosts allow = 129.82. 127.
[homes]
comment = Home Directories
read only = No
browseable = No
[downloads]
comment = CNHP local software repository
path = /home/samba/cnhp
guest account =
read list = @cnhp
write list = @cbt
read only = No
[ftp_pub]
comment = CNHP ftp site /pub directory
path = /home/ftp/pub
guest account =
write list = @cbt,@cnhp
read only = No
[GIS North]
comment = DRG's from Norther Colorado
path = /home/samba/gis_north
guest account =
write list = @cbt
read only = No
[GIS South]
comment = DRG's from Southern Colorado
path = /home/samba/gis_south
guest account =
write list = @cbt
read only = No
[web]
comment = Web Site
path = /home/httpd
guest account =
write list = @ecoweb
read only = No
Re: Smb.conf
Author: J. Thomas Sapienza
Date: Thu, 10 Feb 2000 00:00
Date: Thu, 10 Feb 2000 00:00
42 lines
1815 bytes
1815 bytes
Well, it seems to be caught in a nasty wind from the left... vishwanath parakala <vishu@cs.colostate.edu> smurfing smurfed: > Hey .. does anyone have an idea what's wrong with my smb.conf ... > I'm unable to access it from Windoze machines .... > [global] > keep alive=30 > os level=2 > security=share > guest account=nobody > printing=bsd > printcap name=/etc/printcap > load printers=yes > workgroup=WORKGROUP > [homes] > create mode=0750 > browseable=no > comment=homedirectory > read only=no > [printers] > comment=All Printers > browseable=no > printable=yes > public=no > read only=yes > create mode=0700 > directory=/tmp > -- > VISHWANATH PARAKALA > __________________________________________________________________________ > Home Page: http://www.cs.colostate.edu/~vishu > finger : vishu@miller.cs.colostate.edu -- +-----------------------------------------------------------------------+ Tom Sapienza Thank you, and OK! Score: -8 http://www.worldwidemart.com/sapienza/personal/ ICQ: 3532821 Favorite Mammal: Lemur Favorite Waterfowl: Duck
Re: Smb.conf
Author: Michael Dwyer
Date: Thu, 10 Feb 2000 00:00
Date: Thu, 10 Feb 2000 00:00
17 lines
1214 bytes
1214 bytes
vishwanath parakala <vishu@cs.colostate.edu> wrote: : browseable=no This won't help. :) If this is your problem, you will be able to reach your shares by typing them directly in, but they won't be published on a master browser, and so won't be browsable. Try changing that to YES, or in a Win32 "Run..." dialog, enter \\10.0.0.0\username Where the 10.0.0.0 is your IP, and the username is... uh. Your username (other than Root) -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Michael J. Dwyer I doubt, therefore I might be. mdwyer@holly.ColoState.edu http://WWW.CS.ColoState.EDU/~dwyer/ Computer Science Major Amateur Radio Tech N0ZAP
Re: Smb.conf
Author: vishwanath parakala
Date: Sun, 13 Feb 2000 00:00
Date: Sun, 13 Feb 2000 00:00
99 lines
3953 bytes
3953 bytes
Tried all tyhe stuff ... I just realized that I could access the stuff from the CS dept as \\machine.name.sdfdf.adsd\\username ... But its unaccessible from my own domain ... ie. engr its also unaccessible as \\netbiosname\ even tho the m/c appears in the network neighborhood of other machines .... It says this "The account is not authirized to login from this station" It works fine when I boot it in Windows too ... ideas? A Adam Carheden <carheden@holly.ColoState.EDU> wrote: > Well, workgroup is set to WORKGROUP. You might want to change that to > whatever workgroup/domain your windows machines are using. Also, try > setting a netbios name such as 'netbios name = myWinMachineName'. If > you have an NT server on your local net, you might want to 'wins server > = 129.82.ntmachine.ip' For security reasons, you might also want to add > the following line: 'hosts allow = 129.82. 127.' This would limit > connections to IP that start with those octets (csu and loopback). The > trailing . are important. > The easiest way to do stuff is to use SWAT, the Samba Web Administration > Tool which is installed with samba as a web server on port 901. Go to > http://samba.server.ip.addr:901 and log in as root. You can then modify > smb.conf using a nice gui interface. > -- > Adam Carheden > carheden@holly.ColoState.EDU > Here's my smb.conf if you want to take a look: > # Samba config file created using SWAT > # from dialup0028.PPP.ColoState.EDU (129.82.52.127) > # Date: 2000/02/10 08:17:54 > # Global parameters > [global] > workgroup = CNHP > netbios name = FTP > netbios aliases = walrus > server string = CNHP Samba Server > security = SERVER > password server = OTTER > log file = /var/log/samba/log.%m > max log size = 50 > socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 > add user script = /usr/local/samba/bin/addsmbusr %u > dns proxy = No > wins server = 129.82.197.251 > hosts allow = 129.82. 127. > [homes] > comment = Home Directories > read only = No > browseable = No > [downloads] > comment = CNHP local software repository > path = /home/samba/cnhp > guest account = > read list = @cnhp > write list = @cbt > read only = No > [ftp_pub] > comment = CNHP ftp site /pub directory > path = /home/ftp/pub > guest account = > write list = @cbt,@cnhp > read only = No > [GIS North] > comment = DRG's from Norther Colorado > path = /home/samba/gis_north > guest account = > write list = @cbt > read only = No > [GIS South] > comment = DRG's from Southern Colorado > path = /home/samba/gis_south > guest account = > write list = @cbt > read only = No > [web] > comment = Web Site > path = /home/httpd > guest account = > write list = @ecoweb > read only = No -- VISHWANATH PARAKALA __________________________________________________________________________ Home Page: http://www.cs.colostate.edu/~vishu finger : vishu@miller.cs.colostate.edu
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads