Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 243
  • Last Modified:

How do I define a UNC?

I have a Solaris machine connected to some WIn95 machines. I'd like to be able to see the Solaris in Win95's
Network Neighborhood.
How do I name the Solaris machine so it will be recognized by the other machines on the LAN and
where exactly do I define this name?
0
sveta
Asked:
sveta
1 Solution
 
chytraceCommented:
Hi,

      for that purpose you must install & configure SAMBA on your Solaris box. Along with that some services for SAMBA must be configured and provided for W95 boxes ( fox example users' home directories, disk pool or printer connected to Solaris box).
It depends what you need to be shared by W95 boxes.

Regards

            Radovan
0
 
svetaAuthor Commented:
Thanks but I know about that already what I need is some instructions how exactly to define the needed definitions.
All I want is the W95 machines to see the Solaris root directory. no other sharings.
0
 
chytraceCommented:
Hi,
    bellow is an example of /etc/smb.conf file.

----------------    smb.conf    ------------------
---------------- For RedHat 4.2 ------------------

;================ Global  Settings ==============
[global]

; We present ourselves as W95 box
; Type of services
   announce as = Win95

; Allow our directories to be browsable by clients
   browseable = Yes

; Which NIC we are using for communication
   interfaces = 114.122.203.44/24

; Allow just hosts on our local network
hosts allow = 114.122.203.

; Define workgroup
; workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
   workgroup = NBU

; Define our NetBIOS name
   netbios name = SolGWSamba

; comment is the equivalent of the NT Description field
   comment = RedHat Samba Server SOLGW2

; volume = used to emulate a CDRom label (can be set on a per
;          share basis)
   volume = SoW2

; printing = BSD or SYSV or AIX, etc.
   printing = bsd
   printcap name = /etc/printcap
   load printers = yes

; Uncomment this if you want a guest account
;  guest account = pcguest
;  log file = /var/log/samba-log.%m
; Put a capping on the size of the log files (in Kb)
   max log size = 50
   log level = 2

; Options for handling file name case sensitivity and / or
; preservation
; Case Sensitivity breaks many WfW and Win95 apps
    case sensitive = no
    short preserve case = no
    preserve case = yes

; Security and file integrity related options
   lock directory = /var/lock/samba
   locking = yes
   strict locking = yes
;   fake oplocks = yes
   share modes = yes
; Security modes: USER uses Unix username/passwd,
;                 SHARE uses WfW type passwords
;                 SERVER uses a Windows NT Server to provide
;                        authentication services
   security = share
; Use password server option only with security = server
;   password server = <NT-Server-Name>

    password level = 1
    revalidate = True
; Configuration Options
; ***** Watch location in smb.conf for side-effects *****
; Where %m is any SMBName (machine name, or computer name)
; for which a custom
; configuration is desired
;   include = /etc/smb.conf.%m

; Performance Related Options
; Before setting socket options read the smb.conf man page!!
   socket options = TCP_NODELAY
; Socket Address is used to specify which socket Samba
; will listen on (good for aliased systems)
;   socket address = aaa.bbb.ccc.ddd
; Use keep alive only if really needed!!!!
;   keep alive = 60

; Domain Control Options
; OS Level gives Samba the power to rule the roost.
; Windows NT = 32
; Any value < 32 means NT wins as Master Browser,
; > 32 Samba gets it
;   os level = 33
; specifies Samba to be the Domain Master Browser
  domain master = yes
  preferred master = yes
; Use with care only if you have an NT server on your network
; that has been
; configured at install time to be a primary domain controller.
;   domain controller = <NT-Domain-Controller-SMBName>
; Domain logon control can be a good thing!
; See [netlogon] share section below!
;   domain logons = yes
; run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
; run a specific logon batch file per username
;   logon script = %u.bat
; Windows Internet Name Serving Support Section
; WINS Support - Tells the NMBD component of Samba to enable
;                it's WINS Server the default is NO.
;   wins support = yes
; WINS Server - Tells the NMBD components of Samba to be
;               a WINS Client
; Note:
; Samba can be either a WINS Server, or a WINS Client,
; but NOT both
;   wins server = w.x.y.z
; WINS Proxy - Tells Samba to answer name resolution queries
;              on behalf of a no WINS Client capable client,
;              for this to work there must be at least one
;              WINS Server on the network. The default is NO.
;   wins proxy = yes
name resolve order = host bcast
 
;============= Share Declarations ==============================
[homes]
   comment = Home Directories
   browseable = yes
   read only = no
   writable = yes
   preserve case = yes
   short preserve case = yes
   create mode = 0750

; Un-comment the following and create the netlogon directory
; for Domain Logons
; [netlogon]
;   comment = Samba Network Logon Service
;   path = /home/netlogon
; Case sensitivity breaks logon script processing!!!
;   case sensitive = no
;   guest ok = yes
;   locking = no
;   read only = yes
;   browseable = yes
; say NO if you want to hide the NETLOGON share
;   admin users = @wheel

; NOTE: There is NO need to specifically define each individual
; printer
[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   printable = yes
; Set public = yes to allow user 'guest account' to print
   public = no
   writable = no
   create mode = 0700

;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

; A publicly accessible directory, but read only, except for
; people in the staff group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = yes
;   printable = no
;   write list = @users

; Other examples.
;
; A private printer, usable only by fred.
; Spool data will be placed in fred's
; home directory.
; Note that fred must have write access to the spool directory,
; wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes
;
; A private directory, usable only by fred.
; Note that fred requires write
; access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no
; a service which has a different directory for each machine
; that connects
; this allows you to tailor configurations to incoming machines.
; You could
; also use the %u option to tailor it by user name.
; The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writeable = yes
;
;
; A publicly accessible directory, read/write to all users.
; Note that all files
; created in the directory by users will be owned by the default
; user, so
; any user with access can delete any other user's files.
; Obviously this
; directory must be writable by the default user.
; Another user could of course
; be specified, in which case all files would be owned by that
; user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no
;
;
; The following two entries demonstrate how to share a directory
; so that two
; users can place files there that will be owned by the specific
; users. In this
; setup, the directory should be writable by both users and
; should have the
; sticky bit set on it to prevent abuse. Obviously this could be
; extended to
; as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

Hope this helps.

Regards

               Radovan
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
chytraceCommented:
BTW it's samba-1.9.18p5-42.6 version
0
 
rgmisraCommented:
Are the machines on the same network? If not, you may have to
use the WINS capabilities of Samba.
0
 
mohammedgCommented:
It is quite simple just make your workgroup on your sun machine the same as the workgroup or NTdomain of your win95.

i.e. include the line :

workgroup = MYWORKGROUP

in the [global] section, in the /usr/samba/lib/smb.conf file
then you need to run nmbd (netbios name service, this is part of samba) on solaris
this should make your machine visible in the Network Neighborhood of win95 mahine.

basically you need a Netbios naming service running on solaris. Further if you would like to browse your root on solaris from win95, then you must run smbd server on the solaris machine. This allows solaris to share resources for windows.

both smbd and nmbd comes as part of the samba package.


0

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now