Member Avatar for viber101

i join linux machine in windows server 2000 AD domain using likewise-open5 but i cant access files and folders in a file server even i have full permission to those files or folders. Anyone can help me to fixed this. thanks

  • 2 Contributors
  • 2 Replies
  • 181 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by viber101

Dani AI

Generated

Quick troubleshooting notes for (and follow-up for ) — the symptoms you describe (joined with likewise‑open5, GUI “Unable to mount location / Failed to mount Windows share” when browsing, but “Connect to server” works) usually mean the AD join/auth is probably fine while the desktop’s SMB browsing/negotiation layer is failing. Confirm the join first with Likewise’s CLI and check that the AD account resolves locally. (docstore.mik.ua)

Try these quick checks from a terminal to separate authentication, name-resolution and GUI/back-end problems:

sudo domainjoin-cli query
id 'DOMAIN\\someuser'         # does the domain user map to a uid?
wbinfo -u                     # list domain users (winbind)
smbclient -L //fileserver -U 'DOMAIN\\someuser'

If smbclient can list the shares and accept credentials, the server and permissions are OK — the problem is the file‑manager/GVFS layer or protocol negotiation. (samba.org)

Common fixes that match your symptom (browse fails, direct connect works):

  • Install the SMB/CIFS and GVFS backends so GNOME/Thunar can browse and mount shares: e.g. sudo apt install gvfs-backends cifs-utils smbclient.
  • If browsing still shows nothing, try connecting by IP (smb://IP/sharename) — that sidesteps NetBIOS/WINS name issues. (help.ubuntu.com)

If explicit mounts fail or you’re on an old Windows box, try mount.cifs with explicit protocol/security flags (experiment with vers= and sec=): 

sudo mount -t cifs //fileserver/sharename /mnt/share \
  -o credentials=/root/.smbcreds,iocharset=utf8,vers=1.0,sec=ntlmssp

The vers= and sec= options control SMB dialect and auth; modern clients disable SMBv1 by default so you may need vers=1.0 for legacy servers — but SMBv1 is insecure and should only be a short‑term workaround. Check kernel/syslog and gvfs logs (dmesg, journalctl --user) for the concrete error string if a mount fails. (man7.org)

Priority order: (1) verify AD join + domain user resolution, (2) test with smbclient, (3) install gvfs/cifs packages and try smb://IP/share, (4) experiment with vers/sec only if the server is legacy (and plan to upgrade).

Recommended Answers

All 2 Replies

Member Avatar for tje210

how far do you get? are you able to see what you want to access, but are unable to access them? what error message do you get (f any) ?

Member Avatar for viber101

thanks for the reply...im getting error "Unable to mount location" Failed to mount Windows share" when browsing windows network.

i can access the files using "connect to server" in linux.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.