Trying to connect to Samba share

alright so I have a smaba server setup on a fedora core 5 box
I am trying to mount the share on os x. I go to finder and to the network and I see the server. I then click connect, sign in and it says "The alias Server could not be opened, because the original item can not be found" So, what does that mean? I try and connect through the terminal using start smb commands I say "smbclient //192.168.1.108/joe" and it goes
init_iconv: Conversion from UTF-16LE to CP0 not supported
init_iconv: Attempting to replace with conversion from UTF-16LE to ASCII
init_iconv: Conversion from UTF-8-MAC to CP0 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from UTF-8-MAC to CP0 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP0 to UTF-16LE not supported
init_iconv: Attempting to replace with conversion from ASCII to UTF-16LE
init_iconv: Conversion from CP0 to UTF-8-MAC not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP0 to UTF-8-MAC not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP0 to UTF8 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from UTF8 to CP0 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from UTF-16LE to CP0 not supported
init_iconv: Attempting to replace with conversion from UTF-16LE to ASCII
init_iconv: Conversion from UTF-8-MAC to CP0 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from UTF-8-MAC to CP0 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP0 to UTF-16LE not supported
init_iconv: Attempting to replace with conversion from ASCII to UTF-16LE
init_iconv: Conversion from CP0 to UTF-8-MAC not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP0 to UTF-8-MAC not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from CP0 to UTF8 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
init_iconv: Conversion from UTF8 to CP0 not supported
init_iconv: Attempting to replace with conversion from ASCII to ASCII
Password:
I then type in my password and press enter and I am in
I can move around and everything is good. So, why can't I mount the share? I know I am typing in the correct info.

You could try creating a new sharedpoint on your PC. An empty folder for example. Then try connecting to it from your mac. Then you can rule out a problem with any of the contents of your original sharepoint.

Similar Messages

Error -6602 while connecting to samba shares.

Hi everyone, i have some problems with samba client on MacOSX 10.5.8, the problem is that it connects to some shares and some not, and I don't know why, please help.
Here is my samba configurations on Ubuntu server, the problem starts after logging as a user kuba with password, it shows Erro -6602. Login and pass are correct, I use them with a parallel desktops windows xp, and it works. Mac is working with other server which stands on PLD Linux. I don't know if it will be usefull but if i can tell you that password doesn't contain any special chars, the only one is undescore char. The same password and user with some additional letters works on PLD.
I can connect to samba shares on this server with smbtree command, if I use
smbclient //server/share -U user with a password authentication it shows a wrong password (but it's correct).
When I delete the valid user definition I can connect to samba, but only with a readonly mode...
[global]
netbios name = ubunteon
server string = ubunteon
workgroup = *********
announce as = NT Server
announce version = 4.9
security = share
encrypt passwords = yes
update encrypted = no
unix password sync = no
smb passwd file = /etc/samba/smbpasswd
logon script = startup.bat
logon drive =
add user script = sudo /usr/sbin/useradd -g smbusers %u
delete user script = sudo /usr/sbin/userdel -r %u
add group script = sudo /usr/sbin/groupadd %g
delete group script = sudo /usr/sbin/groupdel %g
add user to group script = sudo /usr/sbin/usermod -G %g %u
add machine script = sudo /usr/sbin/useradd -g smbmachines -c 'Konto komputera %I' -s /bin/false -d /var/lib/samba/nobody %u
passwd chat debug = no
passwd chat = New*UNIX*password %n\n ReType*new*UNIX*password %n\n passwd:*all*authentication*tokens*updatedsuccess fully*
passwd program = /usr/bin/smbpasswd -L -a %u
nt acl support = no
nt pipe support = yes
map to guest = Bad User
log file = /var/log/samba/log.%m
max log size = 50
log level = 1
os level = 255
domain logons = no
preferred master = yes
domain master = yes
local master = yes
time server = yes
browse list = yes
enhanced browsing = yes
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
winbind enum groups = yes
winbind enum users = yes
winbind use default domain = no
winbind separator = +
unix charset = UTF8
display charset = UTF8
dos charset = CP852
wins support = yes
read raw = yes
write raw = yes
oplocks = no
level2 oplocks = no
max xmit = 65535
getwd cache = yes
dos filetimes = yes
dos filemode = yes
dos filetime resolution = yes
deadtime = 15
default case = lower
preserve case = yes
short preserve case = yes
case sensitive = no
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=16384 SO_RCVBUF=16384
dns proxy = no
name resolve order = hosts lmhosts wins bcast
guest account = guest
admin users = smbroot
invalid users = root
load printers = yes
printing = cups
printcap name = cups
[www]
comment = Webpages
path = /home/user/public_html
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[devel]
comment = Development Zone
path = /home/user/0-Developement
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[pdfprints]
comment = Development Zone
path = /home/user/PDF
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[home]
comment = Home
path = /home/user
public = no
read only = no
browseable = yes
writeable = yes
valid users = user
[oferty]
comment = Oferty
path = /home/user/public_html/2-Oferty
public = no
read only = no
browseable = yes
writeable = yes
valid users = user
#udostepnienia widziane przez wszystkich
#drukarki
[printers]
comment = Drukarki sieciowe
browseable = no
path = /var/spool/samba
printable = yes
writable = no
create mode = 0700
#drivery do drukarek sieciowych
[print$]
path = /srv/samba/printers
guest ok = yes
browseable = no
read only = yes
write list = smbroot
#katalog domowy
--------------------------------------------------------------

Hi Ramya,
Following checks may help to resolve the issue.
1) Whether Port 21 is open and allowed to connect with FTP.
2) Ping, FTP and telnet possible from PI box to FTP.
3) User mentioned in Communication channel have authorization for read and write on FTP server.
4) FTP ports are open.
5) Firewall setting done properly.

Can't connect to samba share via VPN

Hello all,
I am looking for an answer for few days now and still can't manage to fix it. I found two workarounds in the meantime, but it's not what I want!
My case:
Cisco vpn on one side and Mac vpn client (native). I can connect alright, can't only mount samba share. Via console I got invalid argument error, but when I go to finder > go to server it's just processing (no error). Left it for few mintes and nothing happened. I have a windows on virtual machine and I can mount samba alright. One more thing. I created a new user, logged in and it works! ****.
Can anyone say where should I look? What can be the problem on my old account? Don't want to switch and change all the things now, there must be a way to fix it...
Hope someone can help
Thanks in advance,
Regards,
Jake

Hi Richard,
Thanks for interest. It's a windows share 2003 smb. It's a company network. As I said its not the case of VPN itself.
About the new user, that's a yes, it's same username as my samba share name, but even tho it's the same it needs my authentication. For the more, when I am with my mac at work and connect via cable I can access everything alright from my old account.
How can VPN block me when I can access it from my windows virtual (which is not the same as my work username). I can access it from new user, I would say its not the case of VPN blocking me there, I guess it's something I have changed over the years with my previous VPN settings.
I have direct access to VPN and I know firewall is off right now as we are testing it, so its for sure my mac settings...
Question is where do I find it:)

Finder crashes when trying to connect to network share

Hi!
I've just upgraded my Mid 2012 MacBook Pro to Mavericks, and found that Finder always crashes when trying to connect to my office network share via an IPSec VPN connection. It's a Synology DiskStation NAS, so i have the options to connect via AFP or SMB, however both result in the same, the crashing of finder. Even after i relaunch it, i can't open finder, and can't even shut down or restart my system (only by holding the power button for 5 secs...)
At first i thought it's the result of the latest Little Snitch version, but the problem remained after completely removing Little Snitch.
Unfortunalely i won't be able to try connecting to the NAS on the local network until monday, but i'd really appreciate if someone could point me to the direction of some solution as this way i can't do any of my work.

Just a quick heads up. I finally managed to resolve the issue. It seems that mavericks doesn't handle the MTU of the vpn connection correctly, so i ended up modifying the MTU on the VPN gateway.

Can't connect to Samba shares after upgrading

Hi,
I recently upgraded to Samba 3.6.0-8 (among other things, including a new kernel 3.0-ARCH), and all my shares have become unavailable from Windows 7. I can't connect to any, nor can I see the shares list. My Arch box has essentially become invisible as far as CIFS shares go. I can still ping it normally, and access it through SSH, so it doesn't seem to be a major network issue, this is specifically with Samba.
I have since tried changing my workgroup in Samba, downgrading to 3.6.0-{1,4}, disabling firewalls, changing Win7's security settings, and restarting several times, to no avail. Nothing has changed with my Windows box, I only performed a major upgrade to Arch (it is currently up-to-date).
I don't see any relevant errors in the Samba logs, and I can browse the shares just fine locally in Arch, I just can't see them from Windows.
Anyone have a clue?
Thanks,
IM

Is your arch server configured to allow samba traffic? With the recent removal of hosts.allow and hosts.deny, I wonder if this could be the issue? Do you have ufw or iptables? I know you said you disabled the firewall, but it wasn't clear if that was on the client or server.
Scott
edit: here's the ufw rule I use (/etc/ufw/applications.d/samba):
[Samba]
title=Windows file and printer server for Unix
description=Tools to access a server's filespace and printers via SMB
ports=137,138/udp|139,445/tcp
Last edited by firecat53 (2011-09-21 18:18:59)

[solved] Can't connect to samba shares

This is probably my fault, but for the life of me I can't figure this out. I started out trying to get usershares to work by following the wiki at https://wiki.archlinux.org/index.php/samba, and I am unable to connect to the resulting shares either from the local host or from my netbook. It tells me permission denied. I then tried creating a public share with guest access, because I couldn't get the usershares to work. I am unable to get that working either. I have
chmod 777 -R
the folder I am sharing, as well as the
/var/lib/samba/usershare
folder. Please help. Here is my smb.conf:
#======================= Global Settings =====================================
[global]
workgroup = OSHANNON
server string = MDSHANNJARO
hosts allow = 192.168.1. 127.
log file = /var/log/samba/%m.log
max log size = 50
security = user
map to guest = Bad User
guest account = nobody
dns proxy = no
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = Yes
usershare owner only = False
#============================ Share Definitions ==============================
[Bleach]
path = /mnt/Data/Bleach
read only = no
guest ok = yes
I tried adding the nobody user since there was no users listed when running
pdbedit -L
using
pdbedit -a -u nobody
and just pressed enter for the password field. This did not help.
testparm says
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[Bleach]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
workgroup = OSHANNON
server string = MDSHANNJARO
map to guest = Bad User
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = No
usershare path = /var/lib/samba/usershare
idmap config * : backend = tdb
hosts allow = 192.168.1., 127.
[Bleach]
path = /mnt/Data/Bleach
read only = No
guest ok = Yes
Last edited by mdshann (2014-03-04 06:01:04)

uninstalled samba, reinstalled it. deleted old config file. created new config with just the contents that the wiki states is necessary for usershares to work. the current smb.conf looks like
[global]
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = yes
usershare owner only = False
added my user to samba using
pdbedit -a -u mdshann
started smbd and nmbd and enabled both. tried to share a folder, caja says samba is not installed. use yaourt to search for caja and find package mate-file-manager-share. installed said package, killed and restarted caja. shared folder and told it to add permissions automatically. checked the boxes to allow guest and to allow users to change files. still I cannot connect. just for reference, I have used the wiki article sections from the beginning of the article through adding a user. I did not use the creating a share section as I want usershares to work through MATE and CAJA. It creates the share and it is visible on the network, I just can't connect to it.
Pretty much the same as what I tired before, with the same result. Only difference is I haven't tried manually creating the share through smb.conf, but that didn't work before either. No reason to think it will work now, the problem was the same whether I used the gui usershares option or adding the share to smb.conf.
I was able to get samba working with a very similar config file as in my first post, on arch based manjaro on my server at work. I did not enable or use usershares at work, but creating the shares in smb.conf worked just fine. Why will the same procedure not work on arch? Same packages for the most part, manjaro just adds a few. In fact, when I set up samba on manjaro, I used the arch wiki article, as Manjaro's wiki is sparse. Main reason we used manjaro at work was the speed of installation was much quicker, and we needed the machine back up quickly so we could start backing up our customers data. (I own a PC repair shop.)
On a side note, this community has served me well in the past the few times I have have issues since I started using arch 5 years ago. Why my post has gone so long without a reply other than being chastised for trying to call attention to a 3 day old unanswered thread is beyond me, but I am not thrilled by it. It has now been a full 2 weeks since my original post. I have never had this issue before, and if I can't bump or somehow call attention to my thread I am unsure of how to get help. Am I supposed to keep posting new threads on the same issue? I would think those would get closed rather quickly if I had. Should I post nonsense on this thread, I mean anything other than the word bump. A discussion of cat videos maybe?

Error when trying to connect to deployment share MDT 2013 - Using Virutal Machine as Refernce image

Hello all
I cant seem to move forward on this build and capture. I am using Hyper-V on windows 8.1 to perform the B&C on VM but keep getting this error when I boot the VM
H
Phil Balderos

IT's common practice to add the credentials (domain\username+Password) directly into the bootstrap.ini and/or customsettings.ini file to allow for totally hands off building of corporate images. Check to see if have the right credentials added in.
Additionally, you may have network connectivity problems. Best thing to do while in WinPE is to press F8, that will bring up a cmd.exe window, allowing you to do some manual debugging.
ipconfig /all
ping opsit12226
net use * \\opsit12226\deploymentshare$ /u:opsit1226\administrator *
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

AutoFS + Samba share problems when share not online (especially in itunes)

I'm trying to look into having some or all of my media on a server for a couple of my macs, the main one of interest right now being a mac mini working as a HTPC under a tv, being operated 99% of the time with just the apple remote and frontrow.
A friend informed me that if you have your itunes library not managed and add files from a remote share then everything works pretty well. Namely if you try to play a file it will seemingly automount the remote file and start it playing. If the remote server is not available it will quickly discover this and after a short pause start giving explanation marks next to the broken tracks. Get the remote destination connected and then try to play a broken track and it will successfully mount the track and play.
Basically perfect.
I quickly tried accessing these files via a symbolic link or alias to them on the remote drive, in doing this i can be somewhat insulated from problems of trying to move the library to other machines/shares in the future. This all works fine but you do lose the ability for itunes to automatically mount the remote drive, which is a bit of a step back, but not a big deal on my normal machine. On my HTPC machine however i'd really like front row to be able to just work, hence automatically mounting the server as required.
The only problem was that when i tried with files directly added to the itunes library from a remote location frontrow would NOT automount the tracks/videos when you attempted to play them like itunes would do.
I've just spent the last few hours following the advice here
http://rajeev.name/blog/2007/11/22/autofs-goodness-in-apples-leopard-105-part-i/
to setup autofs in the hope that this would let me get auto mounting working as it does with itunes and directly added to the library remote files.
I boiled this down to the following settings
as root
vi /etc/auto_master
and add
/smb auto_smb
then create this new config file
vi /etc/auto_smb
and add
<Mount dir under /smb folder> -fstype=smbfs ://<share user>:<share pass>@<ip address>/<share point>
ie.
testMount -fstype=smbfs ://netuser:[email protected]/remoteMount
finally tell automount to throw away its cache
automount -vc
then the mount should be setup
df -h
shows the indirect map waiting
map auto_smb 0Bi 0Bi 0Bi 100% /smb
and by triggering it
ls /smb/testMount
you should connect and get a listing, a subsequent df shows
df -h
//[email protected]/Media 466Gi 325Gi 141Gi 70% /smb/Media
Everything worked well with the share getting mounted nicely when present, frontrow could just start playing the files it needed, perfect!!
The problem came when i wanted to simulate the media server being offline, basically frontrow, a lot of the system including finder, cd commands attempting to access the share, and itunes if you tried that would all freeze for long periods of time as they tried their best to get the files they were looking for.
I tried looking into getting this to gracefully time out and think i got somewhere by trying to setup the samba share to be soft linked.. I wasn't sure in what files i could add this to, first attempts didn't seem to do anything but adding this seemed to make a difference
/etc/nsmb.conf
containing something like
#Configuration file for example.com
[default]
minauth=ntlmv2
streams=yes
soft=yes
to turn soft samba shares on. Things like cd in a terminal seemed to behave quite well with this, when no remote share present you would get empty folders and the like. Finder would also seem to be reasonable with it.
Frustratingly itunes and frontrow both still have quite massive pauses even when finder and cds in the background show that perhaps the soft links are working and failing like they should.
I'm now left wondering what i can do to fix it, and resorting to perhaps having the files added via a symbolic link, using the login items to launch the remote share every boot and then having it so that all i need to do is reboot the HTPC mac mini if the server is on for it to pick it up and let me play the files. Otherwise they'll just be unavailable and will fail gracefully without locking up itunes. The perfect solution would be to either have a crontab running, or some applescript bound somehow to whenever frontrow is ran which manually tries to tell finder to do the equivelant mount the login items setup does.
It's frustrating though as its so close, and the autofs solution if it did work better would seem to be the perfect solution. Has anyone dabbled with this and got any suggestions as to options you can setup to make things not go horribly wrong when a remote share is NOT present, preferrably within the context of itunes or front row not complaining, but to be honest any suggestions i'll be able to try out myself.
Sorry i've written so much, perhaps some of it will be helpful reference as it took me a while to decipher that link at the top into just setting up a samba autofs.
Cheers.

It seems like it's not only the ArchLinux workstation that displays the norwegian letters wrong. The only machine that shows this correc is the machine that created the file/catalogue.
It seems like the windows 2000 displays the cataloge created by windows XP just fine.

Samba share problem with OSX client

hi all,
I've a well know problem with samba server, in my case linux samba server.
In my network 4 client Mac OSx with different OS version everyday are usually connect to samba share with smb or network finder, normaly without specifics configuration or other.
NOW, I've 3 macbook air client with different OS version that do not connect never.
Server log write WRONG PASSWORD but is not TRUE.
I've tried every solution without success.
There is a patch to be applied to client?
it's just a coincidence that only AIR does not work?
Thanks in advance
Regards

I'm noticing this in the job info as well:
Session setup failed: NT_STATUS_LOGON_FAILURE
and the logs show it trying to login as root when I am supplying my domain credentials.
If I add the printer by IP address it works fine. I tried to delete keychain keys but that didn't work for me.

Able to view new files from a samba share only after refresh

Hello Guys,
I'm currently trying to access a samba share from windows server 2012
When I access the share I'm only able to view 210 files out of 460 files
and the remaining files are only viewable after refresh(F5)
This Issue is also appear to be Intermittent, I'm freaked out with this strange behaviour
and unable to run my scripts on the share they end up with unable to find the files!!
Please help me in resolving this
Thanks in Advance

Hi, this is due to an issue with samba interoperability.update your samba drivers
http://blogs.msdn.com/b/oldnewthing/archive/2006/03/30/564809.aspx#comments
MCP/MCSA/MCTS/MCITP

Can't connect to Samba from Windows 8. Win 7 and XP work fine. Many popular solutions tried without success.

To cut the long story short, I have an android box on which is installed Servers Ultimate Pro app. I use this app to run a Samba server and share the contents of my 3TB external HDD connected to this box and use it as a media server over the wireless network.
This samba server is accessable from all my machines and devices - Win 7 Laptop, Win XP PC, and various other android devices using ES File Explorer. My Win 7 laptop has started to die on me, so I've got a new Win 8.1 laptop. The 8.1 laptop is unable to access
the samba server. I have tried various popular solutions (almost all the ones listed in http://social.technet.microsoft.com/Forums/windows/en-US/5dd9991b-78e7-4fa3-b17c-366e4ae0092f) to no joy. The bizzare thing is that I am able to map the samba server to
a network drive in Win 8.1, I am able to see the size of the samba server (says quiet accurately that 1.54TB free of 2.75TB total), but when I click the icon to open the drive, I get the infamous message: Z:\ is not accessible. The specified server cannot
perform the requested operation.
Of course the solution to the linked issue does not solve my problem since I presume Win 8.1 has this security patch KB2536276 built it and cannot be uninstalled. In order to completely rule out any Windows Update causing this issue, I did a clean reinstall
of Win 8.1 and still got the exact same issue.
Any suggestions?

Further checks reveal that my wife's Win 8.1 laptop and my Surface RT tablet are both unable to access the Samba share either... but are able to map the share to a network drive showing the free disk space.
Seems like a Windows 8.1 issue to me now... M$ where are you!!!

Trying to connect to a samba drive

I'd like to connect to a Samba share on a local linux with user authentication but I can't do it from the finder (command-k). I'm presented with the 'Sorry, you've entered an invalid username and password.'
When I try the same connection via smbclient on the command line, I am authenticated without issue. What's that about?

I have the same problem. Not with all of my shares, just with some.
Have you tried "mount_smbfs" from the command line? Some report that they can make that work. I get authentication failure on that also.

I's trying to connect my macbook pro to my pc so i can share files but i cant figure out how

i tried to connect my macbook to the pc through workgroup, but when i pressed on it it dissapeared. I cant figure out how to connect my macbook, to my Pc to share files.

http://macs.about.com/od/filesharing/ss/file-sharing-win7-snow-leopard.htm

"Windows Backup cannot read the backup destination" when trying to backup to Backup Once to Samba share on NAS

Environment:
Windows Server 2012 R2 Essentials running in VirtualBox in a Windows 7 host. Networking is configured and works fine.
Background:
My only backup needs are to copy the contents of two folders to a NAS folder every day at 2 AM.
I configured a backup schedule in Windows Server Backup (wbadmin) to a network location which is hosted as a Samba share on a Synology NAS.
For authentication, I created a backup user which has the same username and password as a user on the Samba share, with permission to read and write the backup folder. I added this user to the Backup Operators group.
Problem:
When I try to run the Backup Once operation to test my backup, I get the following error message:
"Windows Backup cannot read the backup destination."
What I've tried:
I verified that the location is directly accessible in Windows by copying and pasting the address from the Windows Server Backup destination into explorer. Providing the backup user credentials opened the location and creating/reading files worked fine.
Adding the backup user to the Administrators group did not have an effect.
Update 2014-02-18
I checked the backup destination and was surprised to find that the scheduled backup actually completes successfully.
However, Backup Once always results in the above error message.
So the problem is confined to the "Backup Once" operation.

Vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Provider name: 'Microsoft File Share Shadow Copy provider'
Provider type: Fileshare
Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
Version: 1.0.0.1
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
Vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Contents of shadow copy set ID: {5636adcf-668c-4761-9f10-93475904c341}
Contained 1 shadow copies at creation time: 2/19/2014 7:00:00 AM
Shadow Copy ID: {4ca86ed5-9da5-49ca-8591-bf56ebd43486}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {aa265dab-feaa-49ed-9b0e-7ed39ab7f9d6}
Contained 1 shadow copies at creation time: 2/19/2014 2:00:00 PM
Shadow Copy ID: {653a4fa5-4d37-4ea4-9d2a-5710b48cde09}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {9180a420-a6bd-490d-85da-8b81231502b9}
Contained 1 shadow copies at creation time: 2/20/2014 7:00:00 AM
Shadow Copy ID: {871d10ee-9034-4269-b841-4aeee9570464}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {d83afc4e-317f-488c-89d5-a0e65844b93e}
Contained 1 shadow copies at creation time: 2/20/2014 2:00:00 PM
Shadow Copy ID: {f6fbb4ff-bac8-4a82-88e8-dffba8656424}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {3774a3f2-cd36-4f36-9667-4f96c0dbe0b3}
Contained 1 shadow copies at creation time: 2/21/2014 7:00:00 AM
Shadow Copy ID: {91d6c61a-8b39-48dd-811d-e0dcf593c967}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {99be106c-a96d-4488-a9ae-6e92452393ee}
Contained 1 shadow copies at creation time: 2/21/2014 2:00:00 PM
Shadow Copy ID: {5bd57dff-0591-4b0f-9ee8-1b8857f59e54}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {299f4ca8-bffa-47b7-9bb2-12358e0282ce}
Contained 1 shadow copies at creation time: 2/22/2014 7:00:00 AM
Shadow Copy ID: {90b732ae-7ea8-4457-8a6d-84983e27b120}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {97225977-6687-4538-b627-1b33985c9ac1}
Contained 1 shadow copies at creation time: 2/22/2014 2:00:00 PM
Shadow Copy ID: {128d7818-ce91-4d35-ad9e-577856d17374}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy8
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {b196f043-a073-46e4-baa4-2eb99969cc7e}
Contained 1 shadow copies at creation time: 2/23/2014 7:00:00 AM
Shadow Copy ID: {931780f6-be5e-4ad9-9f4d-151ffd6b1942}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {f24e1101-8505-450c-a802-8ba65e46d8d5}
Contained 1 shadow copies at creation time: 2/23/2014 2:00:00 PM
Shadow Copy ID: {815dff7e-92df-449e-a1ed-eb8e5fa3baeb}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy10
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {d4213f80-6b73-418c-af73-b704007511ed}
Contained 1 shadow copies at creation time: 2/24/2014 7:00:00 AM
Shadow Copy ID: {e3bd9313-e7a3-4972-a138-e298e6c12eff}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy11
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {1587431c-1ca9-4276-8d33-dd13ae58a122}
Contained 1 shadow copies at creation time: 2/24/2014 2:00:00 PM
Shadow Copy ID: {e4c3e5b4-0314-4496-9215-369b3c973b25}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {b79771fa-666c-40ff-98c2-80580c1fdf85}
Contained 1 shadow copies at creation time: 2/25/2014 2:00:01 PM
Shadow Copy ID: {9d23803a-5d4e-4222-a389-ddd1e17b0472}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy13
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {5b472176-33e7-447f-aebf-da630cebe01d}
Contained 1 shadow copies at creation time: 2/26/2014 7:00:01 AM
Shadow Copy ID: {0d5a5d90-c9e7-42c0-ab0b-accf0d7d7304}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {879a32b4-48f3-434f-8d92-7202a9a25076}
Contained 1 shadow copies at creation time: 2/26/2014 2:00:00 PM
Shadow Copy ID: {887d8ff9-db0d-4eaa-9a75-df60015c2bb7}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy15
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {fc8d7e9e-c4d4-4010-b603-d88b99435338}
Contained 1 shadow copies at creation time: 2/27/2014 7:00:00 AM
Shadow Copy ID: {69ca835d-0130-4435-8621-83a716f1b621}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {7cebbd3b-c599-4800-91f5-da94ca038a42}
Contained 1 shadow copies at creation time: 2/27/2014 2:00:00 PM
Shadow Copy ID: {57320a15-e046-4128-8305-661984910fff}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy17
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Contents of shadow copy set ID: {702d2ca4-3f60-4d64-8578-50d9dd587ba6}
Contained 1 shadow copies at creation time: 3/12/2014 6:00:01 AM
Shadow Copy ID: {41c62c15-ad88-4191-8cc8-c2814da9a2f4}
Original Volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy18
Originating Machine: seattle-vm-win.GENE.local
Service Machine: seattle-vm-win.GENE.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers, Differential
Vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Shadow Copy Storage association
For volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Used Shadow Copy Storage space: 3.47 GB (8%)
Allocated Shadow Copy Storage space: 3.73 GB (9%)
Maximum Shadow Copy Storage space: 3.96 GB (10%)
Vssadmin list volumes
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Volume path: \\?\Volume{ca9edd16-98f7-11e3-80b0-806e6f6e6963}\
Volume name: \\?\Volume{ca9edd16-98f7-11e3-80b0-806e6f6e6963}\
Volume path: C:\
Volume name: \\?\Volume{ca9edd17-98f7-11e3-80b0-806e6f6e6963}\
Vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {004b7983-7f00-4abe-81de-36729db8355f}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {73682cd4-c469-4d00-b9b9-4b64f08af879}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {652f9dce-637f-447f-bbde-a16dc119e409}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {cd1dab9c-a9cb-4783-aff3-32fa2f9e625f}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {ba4c4bc6-9081-422a-9ed1-647c0eacfe8d}
State: [1] Stable
Last error: No error
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {4e4ca3e1-c62a-474f-a925-fadc1a534188}
State: [1] Stable
Last error: No error
Writer name: 'Windows Server Storage VSS Writer'
Writer Id: {e376ebb9-f0fe-4e1a-adaa-bfbdaf3ab488}
Writer Instance Id: {044b493b-829f-4bcd-9a8f-6d96a9d38daa}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {72c13a8c-4950-4abb-961a-2e0f612ea9b6}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {da138ec1-764b-4179-b2f4-70e94ac22276}
State: [1] Stable
Last error: No error
Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {dd729383-00a9-484c-9abc-3de903f5347c}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {a7c0287b-0e85-4d37-9649-d79928def55e}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {aca73317-e7ce-40a0-aac2-548fd6a987c3}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {d7753d0e-6b3b-4af0-95ea-9aa6733071f4}
State: [1] Stable
Last error: No error
Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
Writer Instance Id: {5971db7f-8508-438c-8f62-736f1b07750f}
State: [1] Stable
Last error: No error

Leopard 10.5.5 and Linux Samba shares not connecting

I have seen this talked about many times, but I have not found the answer. And my situation is always slightly different from others...so here it is!
when I try to connect to our samba share, here are my steps...
Go
Connect to Server
smb://10.xx.xx.xx
Connect
here's where the problem is: the enter username and password pops up, and asks me to put them in...there is no user/password on our samba shares, and I cannot connect via guest either.
in Tiger, there was a work around through terminal to connect, but that doesn't apply to Leopard. We only have 2 Leopard machines here, all the rest are still Tiger, but we are eyeing upgrades, and would be forced to go up to Leopard since we can't buy new Macs with Tiger anymore.

best answer...get rid of Linux share, replaced it with an OS X server, no problems at all...

Trying to connect to Samba share

Similar Messages

Maybe you are looking for