Windows não reconhece servidor fedora9

1. Windows não reconhece servidor fedora9

Herculano Junior da Silva
herculano-jr

(usa Fedora)

Enviado em 03/07/2008 - 14:10h

Olá a todos, sou novato aqui no forum e no uso de linux como servidor de arquivos, antes trabalhava com windows 2003 server, estou com um problema para as máquinas com windows xp reconhecerem o fedora, já instalei todos os pacotes do samba.
samba-client
samba-common
samba
samba-swat
samba smb4k
e nenhum destes programas fazem as máquinas se conectarem, peço um help para configurar este servidor

Valeu a força


  


2. Re: Windows não reconhece servidor fedora9

Marcus-RJ
marcus-rj

(usa Arch Linux)

Enviado em 03/07/2008 - 14:58h

O servidor esta num dominio ou num WorkgrouP


3. webmin

ep
eatti

(usa Debian)

Enviado em 03/07/2008 - 18:56h

Voce conhece o webmin?

é uma interface gráfica que ajuda muito a configurar vários serviços no linux.. é fácil de instalar e depois vc clica na quia Servers e em Samba.. ai vc vai ter um pouco mais de facilidade em configurar os shares linux no windows ou vice e versa...


4. Grupo de Rede

Raphael Kennedy
raphakd

(usa Slackware)

Enviado em 03/07/2008 - 18:56h

Veja se os computadores estão nas mesmo grupo de trabalho. Todos devem estar no mesmo dominio


5. Re: Windows não reconhece servidor fedora9

Julian Castaman
maninhx

(usa Slackware)

Enviado em 04/07/2008 - 08:36h

voce ja configurou o smb.conf?
ja iniciou o samba?

coloca o smb.conf ai para nós vermos.


6. Em grupos de trabalhos

Herculano Junior da Silva
herculano-jr

(usa Fedora)

Enviado em 04/07/2008 - 08:51h

As máquinas estão todas em grupos de trabalhos não tenho nenhum dominio.
segue o smb.config

#
#--------------
#
#======================= Global Settings =====================================

[global]
#--authconfig--start-line--

# Generated by authconfig on 2008/07/03 16:27:57
# DO NOT EDIT THIS SECTION (delimited by --start-line--/--end-line--)
# Any modification may be deleted or altered by authconfig in future

workgroup = cpd
security = user
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
winbind use default domain = false
winbind offline logon = false

#--authconfig--end-line--

# ----------------------- Netwrok Related Options -------------------------
#
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
#
# server string is the equivalent of the NT Description field
#
# netbios name can be used to specify a server name not tied to the hostname
#
# Interfaces lets you configure Samba to use multiple interfaces
# If you have multiple network interfaces then you can list the ones
# you want to listen on (never omit localhost)
#
# Hosts Allow/Hosts Deny lets you restrict who can connect, and you can
# specifiy it as a per share option as well
#
; workgroup = cpd
server string = Samba Server

; netbios name = MYSERVER

; interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24
; hosts allow = 127. 192.168.12. 192.168.13.

# --------------------------- Logging Options -----------------------------
#
# Log File let you specify where to put logs and how to split them up.
#
# Max Log Size let you specify the max size log files should reach

# logs split per machine
log file = /var/log/samba/log.%m
# max 50KB per log file, then rotate
max log size = 50

# ----------------------- Standalone Server Options ------------------------
#
# Scurity can be set to user, share(deprecated) or server(deprecated)
#
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.

; security = user
passdb backend = tdbsam


# ----------------------- Domain Members Options ------------------------
#
# Security must be set to domain or ads
#
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
#
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
#
# Use password server option only with security = server or if you can't
# use the DNS to locate Domain Controllers
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *


; realm = MY_REALM

; password server = <NT-Server-Name>

# ----------------------- Domain Controller Options ------------------------
#
# Security must be set to user for domain controllers
#
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
#
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
#
# Domain Logons let Samba be a domain logon server for Windows workstations.
#
# Logon Scrpit let yuou specify a script to be run at login time on the client
# You need to provide it in a share called NETLOGON
#
# Logon Path let you specify where user profiles are stored (UNC path)
#
# Various scripts can be used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
#

; domain master = yes
; domain logons = yes

# the login script name depends on the machine name
; logon script = %m.bat
# the login script name depends on the unix user used
; logon script = %u.bat
; logon path = \\%L\Profiles\%u
# disables profiles support by specifing an empty path
; logon path =

; add user script = /usr/sbin/useradd "%u" -n -g users
; add group script = /usr/sbin/groupadd "%g"
; add machine script = /usr/sbin/useradd -n -c "Workstation (%u)" -M -d /nohome -s /bin/false "%u"
; delete user script = /usr/sbin/userdel "%u"
; delete user from group script = /usr/sbin/userdel "%u" "%g"
; delete group script = /usr/sbin/groupdel "%g"


# ----------------------- Browser Control Options ----------------------------
#
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
#
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
#
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; local master = no
; os level = 33
; preferred master = yes

#----------------------------- Name Resolution -------------------------------
# Windows Internet Name Serving Support Section:
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
#
# - WINS Support: Tells the NMBD component of Samba to enable it's WINS Server
#
# - WINS Server: Tells the NMBD components of Samba to be a WINS Client
#
# - WINS Proxy: Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
#
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups.

; wins support = yes
; wins server = w.x.y.z
; wins proxy = yes

; dns proxy = yes

# --------------------------- Printing Options -----------------------------
#
# Load Printers let you load automatically the list of printers rather
# than setting them up individually
#
# Cups Options let you pass the cups libs custom options, setting it to raw
# for example will let you use drivers on your Windows clients
#
# Printcap Name let you specify an alternative printcap file
#
# You can choose a non default printing system using the Printing option

; load printers = yes
cups options = raw

; printcap name = /etc/printcap
#obtain list of printers automatically on SystemV
; printcap name = lpstat
; printing = cups

# --------------------------- Filesystem Options ---------------------------
#
# The following options can be uncommented if the filesystem supports
# Extended Attributes and they are enabled (usually by the mount option
# user_xattr). Thess options will let the admin store the DOS attributes
# in an EA and make samba not mess with the permission bits.
#
# Note: these options can also be set just per share, setting them in global
# makes them the default for all shares

; map archive = no
; map hidden = no
; map read only = no
; map system = no
username map = /etc/samba/smbusers
; encrypt passwords = yes
; guest ok = no
; guest account = nobody
; store dos attributes = yes


#============================ Share Definitions ==============================

[homes]
comment = Home Directories
browseable = no
writable = yes
; valid users = %S
; valid users = MYDOMAIN\%S

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
; guest ok = no
; writable = No
printable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /var/lib/samba/netlogon
; guest ok = yes
; writable = no
; share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
; [Profiles]
; path = /var/lib/samba/profiles
; browseable = no
; guest ok = 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 = +staff

[Download]
comment = Pasta de Downloads
path = /root/Download
writeable = yes
; browseable = yes
guest ok = yes

[Documentos]
path = /root/Documentos
writeable = yes
; browseable = yes
valid users = cpd


7. Re: Windows não reconhece servidor fedora9

Julian Castaman
maninhx

(usa Slackware)

Enviado em 04/07/2008 - 11:39h

Qual a classe da sua LAN?
Se você tentar acessar teu servidor qual o erro que ele retorna?


8. Re: Windows não reconhece servidor fedora9

Herculano Junior da Silva
herculano-jr

(usa Fedora)

Enviado em 07/07/2008 - 11:53h

Olá maninhx

ele retorna que está com acesso negado, contate o administrador de rede e a classe que voce perguntou é 10.0.0.0

Valeu pela força


9. Re: Windows não reconhece servidor fedora9

Julian Castaman
maninhx

(usa Slackware)

Enviado em 07/07/2008 - 16:24h

tenta liberar tua classe de Ip.
adiciona no global do smb.conf

#hosts allow = 10.0.0.

quando voce tenta acessar o servidor ele ta pedindo senha?






Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts