Difference: 2 network share icons

What is the difference of the function, when there are one of these icons?
Example:
Showed in the screenshots below. An external drive plugged into my time capsule. In the first screenshot mounted with clicking on Finder sidebar and then the drive icon in the time capsule. In the second screenshot mounted with 'Go to' or the apple script below.
mount volume "afp://TREASURE._afpovertcp._tcp.local/Black Bible"
Is there a way to mount with the wifi icon with a bash script, applescript or php script?
with sharepoint icon with external drive wifi icon

well I do, but a short while later.
or some weeks or even month later, I can do it again.
this is a problem because I need to connect to it from my server.
the server is a Dell PowerEdge 1650 (I know, old, but it was cheap and it does the trick) which is running Linux Ubuntu Server 9.10 "Karmic Koala", since it's a server I did not install a DE(desktop environment) so I need to use the bash or shell (depending on what I do, since it has both)
how I connect it like this (on the sever):
+mount -t nfs "emac.local:/dev/macintosh HD" /storage/nfs/emac/+
the problem here: I use a DHCP, with DHCP reservation.
since I use DHCP reservation the IP should not change.
but the DHCP reservation doesn't really work correctly,
because of this, if my mac is offline (A.K.A off, I never disconnect it), the IP is in the pool, and thus can be assigned to a other computer.
since the IP may change depending on if it is on at a given time.
I need a way to always successfully identify my emac.
for this I use the network name.
and now it changes too!
which means that in order to find it I need to know if it still has the same network name, or what it's IP is.
I can find the IP from a web browser since it's my router who is my DHCP.
but the server doesn't have one.
so I'd have to use a other computer, since the router doesn't allow SSH/TELNET connections.

Similar Messages

File loss moving files to a network share

While moving some files (silly me to use move vice copy and delete later) to a SMB network share about half way through the move OSX lost connection to the share. Error message popped up telling me it couldn't complete the move and the files yet to be moved were deleted! Fortunately they were just some podcasts but I certainly didn't expect that a move operation would delete unmoved files. Is this common behavior under the Mac OSX?
Lawrence

Satoru Murata wrote:
And moving a file from one directory to another on the same drive is "physically" possible?
Actually, yes. They are fundamentally different. The actual file itself does not change. There is one copy of the file. There is also (at least) one hard link to the file. The hard link is what you actually see in the file system as a "file". In a true move operation, you create two links to the file. There is then one physical file with two pointers to it. Then, after that 2nd link is successfully created, you "unlink" the first one. Correspondingly, to "delete" a file, you just "unlink" the one and only link to it. Time Machine, for example, make extensive use of links to create snapshots of your files. These links are only possible on a single file system.
Why shouldn't we expect the Finder to be able to do that properly?
We should. But this is not a bug that should really affect anyone. I'm quite sure that there are more people who, after hearing about this, have tried to use a move across volumes than have ever tried it before. Yes, it is a bug. Yes, you could lose data. But it is a minor operation that few people knew about until recently.
And there's no guarantee that when you hit the "Send" button in Mail your e-mail will reach its destination. Perhaps you should snail mail it. Strike that, the USPS is even less reliable. Go deliver the mail in person.
That is a poor analogy. You still have a copy of the sent mail in your system. A better analogy would be to click "send" and then immediately deleting your copy of the sent message. Surely, that would be foolish. And I prefer DHL. I have had much better luck with them.
No one friggin' needs to use a computer, but a lot of people WANT to. And I'm saying there are people, if you can get it in your stubborn little head, who WANT to use Move instead of Copy, go back to original file/directory, click icon, drag to trash, empty trash, and click OK in confirmation dialog (which, by the way, is a few more than "one additional key" that you allude to).
My goodness! No need to get so upset
You can move files to new volumes all you want to. It is always going to be a risky operation, riskier than copying and then deleting. When Apple releases a fix, the risk will decrease, but I would not advise using it, on any platform.
First of all, who the heck are you telling me I'm the minority so I should just bite the bullet? Since apparently you're such an aficionado of the Terminal, which only 5% of Mac users use on a daily basis, I guess you would be just fine and dandy if there was a glaring bug in Leopard that prevented you from using it "until the software update is available", huh?
I'm "random guy on the Internet". I thought you knew that. That is an interesting question. I have always liked UNIX and I'm particularly fond of the Mac giving me the best of both worlds. But, I have to admit, I was a very happy Mac user long before MacOS X, so I think I could survive.
And second of all, you obviously think I'm some Vista troll or something, but I certainly am not, and it's quite insulting. I'm usually the first one to come to Apple's defense when need be. And, as I mentioned in my first post, I agree that this "problem" is totally overblown on various sites. HOWEVER, you are just an idiot fanboy of the worst kind if you maintain that there's really nothing wrong with this bug and suggest that, and I quote:
Really, the only reason for even attempting this operation is so you can get on the Internet and post a message about how Apple's horrible bug has caused you to lose data.
No, I didn't think that much about you at all. I was just trying to explain the difference between moving vs. copying and how those operations changed when performing them across two different file systems. I admit I am a bit sensitive about the Mac. I try not to evangelize anymore. I do try to respond to FUD when I see it. There has been a lot of that recently with Leopard.
I never said this wasn't a bug and that it shouldn't be fixed. I said it was a bug in a non-default behavior that few people even knew about. I also said that even attempting a move across file systems (even without this bug) is not a wise idea. It has a fairly high risk factor, a fairly low convenience factor, and no savings of space or time. It is my opinion that the only reason people care about it is so they have something to bash Apple about. I wasn't including you, personally, in that category. I was just trying to explain my thinking.
I know I'm fighting a losing battle here. In the "marketplace of opinions" the matter is already decided. Leopard is just as buggy as Vista, if not more so. I've never used Vista, so I can't say for sure. I know the Leopard is perhaps the best, fastest, most bug-free system I have ever used in 25 years. But you wouldn't think that from reading the Internet commentary-du-jour.

Multiple Users Mounting the Same Network Share?

Hello, first time posting...
I'll cut right to my main question: Is it possible, on OS X v10.3.9, for multiple users to simultaneously connect to the same network share?
Here in my office, we have a single Mac that is used by multiple people throughout the day. It has two accounts on it, 'Communications' and 'Studio'. 'Communications' is an Admin account that is used by a co-worker who spends the most time on the Mac. He created the no-limitation 'Studio' account for the rest of us to use.
There is a certain Windows network share that we both frequently use. We've found that if one user connects to the share first, the other user will not have access to it; using 'Go -> Connect to Server' will result in the share being greyed out in the list, and the share will not show up in the Finder.
However, there is one way around it. If Studio connects to the share first and then Communications (the admin account) attempts to make a connection of it's own *through a shortcut on the dock*, then a 'clone' of the share will be created on Comm's desktop, with a "-1" after the name (though it might be some other number).
This may sound like I've answered my own question, but what I'm looking for is a way for the non-Admin account to access the share after the Admin account already has (so that we don't have to log-in and disconnect Communications everytime Studio needs to manage files on the share).
We have Thursby Software's DAVE installed on the Mac, but I'm not sure how it fits into all this.
Any thoughts, suggestions or advice?
Thanks.

Bizarre. It turned out I could merge them, but only in to the mapped drive - L: - and only by explicitly clicking on the drive icon - if I typed L:\series in to dialog box it converted it back to \\nas\share\series... Not helpful.

AppV 5: Sequence shortcut to application located on network share

Hello,
We have an application which is programmed to run directly from a network share.
However, it needs some parts installed locally on the client too, to make it work.
During sequencing using App-V 5.0, I installed the parts necessary on the client, and I created a shortcut to the network path e.g.: \\server\share\application.exe
The sequencing process works fine, and the application gets published correctly to an App-V client.
However, when launching the application we receive an error "The application was unable to start correctly (0xc000142). Click OK to close the application."
In Event Viewer we notice following error in Applications and Services > Microsoft > AppV > Client > Virtual Applications: "The virtual applicatoin '\\server\share\application.exe' could not be started because the App-V Subsystem 'Virtual Shell'
could not be initialized. {error:0x8DC02325-0x52E}"
We notice that the sequenced application shortcut references: "\\server\share\application.exe /appvve:557B23AE-4942-4E3E-BE5F-1DA010EA7DAE_C7B3C423-6E9A-4CE9-AC18-59C7F18F3FA1"
When launching the application directly (\\server\share\application.exe - without appvve parameter) it works fine (but at that moment it's missing the locally installed client components).
When running the same application with parameter 'appvve', it fails (error message above).
When copying the application to a local drive, it does run succesfully when using the 'appvve' parameter, but unfortunately this is not a supported scenario for the application we're talking about. It has to be run from the network share.
So am I correct to say that App-V does not support running an executable located on a network share in the virtual bubble? Are there any solutions/workarounds to make this work anyway?
I tried mapping the network share to a drive letter, but that didn't help either.

I have used a vbscript to start the exe from within the package, install whatever you need, then make the vbs in the installdir locally (c:)
Dim objShell
Set objShell = WScript.CreateObject( "WScript.Shell" )
objShell.Run("K:\Whatever")
Set objShell = Nothing
Make a shortcut to the VBS and change the icon and stop the capture

How to get "fast user switching" and network shares playing nice

I've been alternating between banging my head against a wall and reading every forum I could find to try and get a reasonable compromise between using "Fast user switching" and sharing a folder from a file server. It baffles me how the network share/mount model of OSX/AFP is completely killed by fast-user-switching; this is a big problem with Apple requiring users to be actively logged in to share music/video from iTunes which therefore essentially requires fast-user-switching if anyone else wants to use the computer. (anyone find it odd that you can share files without being logged in, but sharing songs requires an active login for each user who is sharing? Apple: time to make iTunes sharing a service!)
For the sake of example, lets just say I want to share my /Groups folder from my desktop and have it be accessible to my laptop. Here are all the things that I tried:
Apple Method 1) Share /Groups in the Server.app on the desktop (running Lion Server), use finder on the laptop and drag the share icon to "Login Items", alternative use a startup Apple script using "mount volume" Both of the options work and will mount the /Groups folder under /Volumes/Groups, of course when the second person logs in via fast-user-switching (and occasionally the first person for no apparent reason), they will get /Volumes/Groups-1 since /Volumes/Groups is already taken. Tomorrow we log in a different order and now the previously /Volumes/Groups-1 user has their mount at /Volumes/Group and vice versa. Any links, aliases, finder sidebar references, and application settings which pointed to yesterday's location are now BROKEN. Not very user friendly to my mother-in-law who is trying to find those pictures of the kids and doesn't know anything about mount points. I also can't reasonably mirror the file location structure on the desktop so that application preferences that are synced between the two (portable home directories) work. fail.
Apple Method 2) Use automounter and set up by hand direct maps for /Groups or an indirect maps for the children of /Groups. Now it will automatically get mounted to /network/servers/SERVER/Groups/ on the laptop and on the desktop it will automatically create a similar symlink structure so that the same path (/network/servers/SERVER/Groups) work both on desktop and laptop. Cool. Except when the second person logs in, the /network/servers/SERVER/Groups/ mountpoint is already owned by the first user and they don't have any permissions to access it. Fail.
Apple Method 3) Use mount_afs and specify directly the mount-points. Have each user have their own startup AppleScript which mounts /Groups to a different location (e.g. /Users/Shared/username/Groups) that way they don't conflict with multiple users. On the desktop, set up symlinks from /Users/Shared/username/Group to /Groups so that it will be the same as the client and applications settings will work when synchronized back/forth by portable-home-directories. Will it work, yes it does, but what a bear to maintain. Is this really what I should expect to do just to have multiple users on my desktop and laptop (which again is essentially required now if I want to do any type of iTunes sharing). This can't be what apple expects.
What I ended up doing - the "not quite apple" solution.
Non-Apple Method 4) After a read of "Autofs: Automatically Mounting Network File Shares in Mac OS X" (http://images.apple.com/business/docs/Autofs.pdf) at the very end there is a single paragraph of "Kerberized NFS": "A Kerberized NFS mount can have multiple connections from multiple users, each using the correct user’s credentials for each transaction. This allows administrators to support multiple users, each authenticated with their own credentials to the same mount point. This is very different from AFP and SMB mounts," (emphasis mine)
It appears that by using good 'ole NFS (abeint with Kerberos for security!) you can actually have multiple users on the same mount point. Roughly following the guidance at https://support.apple.com/kb/TA24986?viewlocale=en_US. What I needed to do was:
1) create /etc/exports on my desktop and add a single line "/Groups -sec=krb5". The existence of /etc/exports triggered a start of nfsd which no longer has any GUI options in Lion.
2) Add a line to /etc/auto_master on my laptop "/- auto_mymounts" to reference a new direct map.
3) Create /etc/auto_mymounts and add a single line "/Groups SERVER:/Groups" to create the direct map.
THAT'S IT. Three lines in three files.
Now when I log into my laptop, there is a /Groups that is a network mount of my desktop's /Groups, same location AND it works for all of my users, even simultaneously.
In the end I'm happy with what I've got, but man was this a difficult path just to support fast-user-switching. In Lion, Apple appears to be getting away from NFS (no longer turned on by default and remove from the GUI controls) but clearly this really useful functionality which doesn't exist in AFP.
I'm really curious, after all this work. Any other ways to accomplish this?

In my example above, yes I chose to mount the share "Groups" to the top of the root since that is where I put it on my server and I wanted to keep them similar; but that was just my preference, it isn't a requirement. You can export and mount from other directories.

How do I merge multiple instances of the same network share?

In my (large) Lightroom 5.2 (Windows) library I have three instances of, essentially, the same network share (a Drobo NAS) which appear separately in the library.
One appears as Share (\\nas) L:, one as \\nas\Share and one as \\nas\share. The contents of the share are spread randomly across the three - so one might contain the folders series\event1, series\event4 and series\event5 and another series\event2, series\event3 and series\event6.
Is there an easy way to convince Lightroom that they're all the same physical location and merge them in the library? No amount of dragging, dropping, importing or synchronization seems to have had any effect so far!
Guy

Bizarre. It turned out I could merge them, but only in to the mapped drive - L: - and only by explicitly clicking on the drive icon - if I typed L:\series in to dialog box it converted it back to \\nas\share\series... Not helpful.

How Do I find out what app is auto-mounting a network share and stop it?

I have a new laptop, the 13" rMBP. I installed Steam and wanted to use the network share on my server to store the game files. Everything went OK. I closed Steam, disconnected the share and shutdown my laptop. When I opened my laptop later on at work, it started to try and mount the network share.It keeps on going it. I removed the Steam app and all files related to Steam that I could find. I've looked at fstab, auto_home, auto_master and a large list of other files and directories and I *still* cannot find the offending file that's auto-mounting the share. It's really frustrating.
The share auto-mounts when I am home but not on the desktop or in finder. I find it by looking at /Volumes/ in terminal. If I mount the share manually under /Volumes/ it shows as Games-1 and mounts on the desktop under Games.
Does anyone have any ideas on where I should be looking to find the offending process/file/daemon?
Thank you!
Trevor

thanks for the reply but are you sure about this? What difference would it make? Why 5 apps?
Even if it does work, which I doubt, at some point, I will have to resync ALL my apps again and surely the same thing will happen again, and I will be none the wiser. I still won't know which app it is. There must be a way of finding this out.
Any ideas?
What is really freaking me out is how it is connecting to my carrier (who is charging me) with Cellular data switched off.......?
Thanks again.

Is it possible to prevent the OS from dropping and deleting a network share shortcut?

One thing that has always bugged me about Mac OS is that when a network share becomes unresponsive or unavailable the shortcut on the desktop disappears and you get a glaring messaging that the share has been disconnected.
Is there any way to prevent a network share from being removed just because it becomes momentarily unavailable?
As an example, on a Windows machine the network share shortcut remains, you simply cannot use it but it is there and ready to go the moment the share comes back online. Is there some way to make OS X behave in this manner? Or is there a way to extend the time out interval for a network share?
Thanks.

Drag the icon into the sidebar of a Finder window under FAVORITES.

Windows 8.1 Network Share 0x8007003b Error Copying Files

Hi All,
I'm having an issue when copying files from a Windows network share. If the file is above 5MB it will start copying and then after a minute or two I will get an error such as:
Interrupted Action
An unexpected error is keeping you from copying the file. If you continue to receive this error, you can use the error code to search for help with this problem.
Error 0x8007003B: An unexpected network error occurred.
The network share is in a different office and is accessible over a point-to-point VPN, so the connection is not that fast.
But before everyone tells me to start diagnosing the router and or VPN please take note of the following:
My colleague who is running Windows 7 can copy files from the network share fine
If I run a Windows 7 VM on my Windows 8.1 laptop I can copy the files across fine
I also know it isn't an issue with this particular file share. I set up a little lab, where I had one VM which had a shared folder and 2 other client VMs one running Windows 7 and one running Windows 8.1. I limited the bandwidth to the two client
VMs to a similar speed we see across our VPN. The result was that the Windows 8.1 failed with the same error above, whereas the Windows 7 copied fine.
There is also a noticeable difference visually when copying using Windows 8.1 and Windows 7:
Windows 7 - The progress bar progresses smoothly giving the current speed and estimated time remaining
Windows 8.1 - The progress bar progresses in a jumpy fashion. E.g. it shows no progress, then after a minute it jumps and shows 16% progress, then shows no further progress, then jumps by another 18%. There is no estimated time remaining.
I ran Wireshark to investigate what was going on at the network layer. I see the following behaviour:
Windows 8.1 - The file is copying fine then all of a sudden there are a lot of TCP dupack packets. After which the Windows 8.1 client sends a RST packet and then the error pops up.
Windows 7 - The file is copying fine then you also see a load of TCP dupack packets, however no error is displayed and it continues copying fine.
I'd appreciate any help with this I'm hoping there are some settings I can change to make Windows 8.1 behave more like Windows 7!
FYI originally posed here (but was advised to ask on Technet) - https://answers.microsoft.com/en-us/windows/forum/windows8_1-files/windows-81-network-share-0x8007003b-error-copying/300bc9a4-597b-402a-b885-9dd6f6fb51a2
Thanks,
Zak

Hi MeipoXu,
Sorry, it has taken me so long to reply. I thought I had subscribed to receive updates on this thread, but I didn't see anything!
I've ran the commands you gave but some of them did not work, I got the following error:
Set global command failed on IPv4 The parameter is incorrect.
However, output of current settings are below.
TCP Global Parameters
Receive-Side Scaling State : disabled
Chimney Offload State : disabled
NetDMA State : disabled
Direct Cache Access (DCA) : disabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : none
ECN Capability : disabled
RFC 1323 Timestamps : disabled
Initial RTO : 3000
Receive Segment Coalescing State : disabled
Non Sack Rtt Resiliency : disabled
Max SYN Retransmissions : 2
To answer your original questions.
Do you mean the file below 5 MB will copy fine ?
5MB is not a hard limit. If the file is small enough it will copy before it errors out. A file of around 5MB or so fails with an error.
Have you tried to copy the files from another Windows 8.1 machine (This will help us to verify whether the issue is casued by the specific machine)?Have you tried to copy another file from the network share to have a check ?
Yes I've tried from another Windows 8.1 machine and have the same behaviour. It is the same with different files from the network share. And the same with different network shares.
I am seeing nothing in the event viewer when the error occurs. I do not believe this to be a VPN issue because I can recreate this situation perfectly. As I mentioned in the original post- I
also know it isn't an issue with this particular file share. I set up a little lab, where I had one VM which had a shared folder and 2 other client VMs one running Windows 7 and one running Windows 8.1. I limited the bandwidth to the two client VMs to a similar
speed we see across our VPN. The result was that the Windows 8.1 failed with the same error above, whereas the Windows 7 copied fine.
Basically, I had virtual machines all on the same local network. One virtual machine was hosting a file share with files on it. I created one Windows 7 VM and one Windows 8.1 VM. Using VMWare Workstation you can limit the network bandwidth to the VMs. When
I did not limit the network bandwidth I could copy all files of all sizes fine. However, when I limit the network bandwidth to a speed of around 30-50KBps, the Windows 8.1 VM fails to copy files with the same error. But Windows 7 VM copies the files fine.
The point of limiting the bandwidth in this way is to create a similar scenario to that I see when connecting over the VPN.
This all leads me to believe there is some sort of issue with copying files from fileshares over slow connections using Windows 8.1.
Cheers,
Zak

Unable to save MS Word and Excel 2010 and 2013 onto the network share

Hi,
I have read similar cases, but did not work out on the problems we face.
We are using Office 2010 and Windows 7 and it seems like only this combination will encounter saving problem on the networe share (but local / removable disks are fine) -
Other combinations:
Windows XP and Office 2010 - no problem
Windows XP and Office 2003 - no problem
Windows 7 and Office 2003 - no problem
In Microsoft Word 2010, when saving a new document, it will save but create a 0KB file in the network share drive and I notice the blue menu bar of the Microsoft Word 2010 still displays "Document1" instead the new file name.
And only when I click save icon or exit button, Word actually prompts another "Save As" dialog to save the file, and as a result, I have to save the same file and answer MS Word prompt to replace the existing file - and this is the real time that
the document and its contents really got saved. And the blue menu bar then displays the actual file name.
In Microsoft Excel 2010 (also Powerpoint I suppose so), in saving a new excel file, after typing in a file name for the new file in the network share location, it will prompt a dialog box indicating the "File is currently in use"
Similar to MS Word, it will still create a 0KB file in the network share, and only a second time saving and replace the 0KB file, is able to save the file again.
I have tried a lot of ways from Safe Mode, Disable Add-in, Added Trusted Locations to the network share in MS Word and Excel, Uninstall Antivirus software, redo NTFS permission on the network share server folder, etc but the problem cannot
be solved.
Any help is appreciated. Thank you in advance.
Kind regards,
Daryl

Thank you Max.
I have tried various storage configurations and share the folders out in Windows Servers and grant user accesses with AD.
These drives configuration involves iSCSI drives, using NAS drive, using internal SAS RAID drives in Windows 2008 servers, all having the same errors, but the latter one was having the most errors almost every first time the users
save their files (includes saving from email attachments), the files will get 0KB.
I have tested LAN cables, switch LAN points in panels and switches, and comes to no avail.
I have patched with the latest office updates (the latest being Office 2010 SP2) also to no avail.

Mounting a network share via Applescript or Automator causes errors in MS Office apps

If I connect a network share using an automated process, either using Applescript or Automator, though the share shows up on the Desktop and I can open it and view the various folders and files, MS Office apps including Powerpoint, Excel and Word are unable to open the files. Each gives a slightly different error message. In Excel, it looks like this:
In Word, it's:
In Powerpoint, it's:
BUT, if I connect to the server share manually (using Cmnd-K in Finder), all files and folders are properly accessible. I cannot see any differences between the shares connected by the two different means on the Desktop. They have the same name, are the same size, etc.; in short, everything about them seems identical. I even took screen shots of the Get Info page from one of them connected by the different methods:
"home" connected by Automator:
and connected manually:
Does anyone have any ideas as to why this is happening or how to fix it?

I had the same issue. After upgrading kernel to 3.4.5 today the cifs share mounted with original fstab settings. I believe it was caused by this bug:
kernel changelog wrote: The double delimiter check that allows a comma in the password parsing code is
unconditional. We set "tmp_end" to the end of the string and we continue to
check for double delimiter. In the case where the password doesn't contain a
comma we end up setting tmp_end to NULL and eventually setting "options" to
"end". This results in the premature termination of the options string and hence
the values of UNCip and UNC are being set to NULL. This results in mount failure
with "Connecting to DFS root not implemented yet" error.

XP Mode Crashes When Accessing Network Shares

I am using Windows 7 Professional and have installed XP Mode to use a legacy accounting application.
In the Virtual Machines folder on the host under settings I have set the network adapter to Realtek PCIe GBE Family Controller.
Under XP Mode, I have set XP to be a member of the workgroup and I am logging on with a user who can access network. When I run XP Mode I can access the internet with Internet Explorer.
If I then go to "My Network Places" "View Workgroup Computers" I can see all the workgroup computers on the network. If I then double click on a computer name Windows Explorer shows me all the shared directories on that computer.
This is where the problem occurs. If I then click on a shared directory XP Mode instantly exits and restarts. (Windows 7 is unaffected.)
Does anyone have any idea's as how I can access all the shared directories to view the files stored on the network.

Miya Yao, Thank you for your reply.
Can other computer in the workgroup see the shared directory in Windows XP Mode? I don't know exactly what you mean by this. No other computers in the workgroup are running XP Mode. They are running native XP Professional. (It was my original idea to run
a physical XP laptop together with Windows 7 desktop to access the data files required, before I read about XP Mode.)
All workgroup computers can access network shares, if the user has appropriate permissions. I have shared the "Shared Documents" under XP Mode and this share can be accessed by all other computers on the network including the host. However, if I access this
share from the guest via "View Workgruop Computers" as in my first post, XP Mode instantly quits and restarts. For information the XP Mode user name and password is the same as the host user name and password.
I have checked the Event Viewer both before I first posted and again today. There are no entries recorded. However, I should have mentioned that upon restarting XP Mode I get "The system has recovered from a serious error" the details of which are:-
BCCode : 10000050 BCP1 : FFFFFF8A BCP2 : 00000001 BCP3 : F7F23661
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1
If I send the error report I am taken to thsi web page:-
http://wer.microsoft.com/responses/Response.aspx/603/en-us/5.1.2600.2.00010100.3.0?SGD=316378af-10a1-428a-9016-074d398ed1a1
The page talks about testing RAM. RAM is fine. There is 8GB of physical RAM. It was tested with memtest86+ v2.10 and v4.20 separately. v4.20 was run for 12 hours plus with no errors detected. I have tried adjusting XP Mode RAM under settings but this makes
no difference.
The issue happens when accessing all shared directories including empty ones.
I clean booted the computer and yes the issue still exists.
If I use dos to view a directory under XP Mode the problem exists, by typing
\\SERVER\SHARE\FOLDERNAME .
By using the host I can map a shared directory. Then under XP Mode I can access the share from my computer. I have noticed by mapping S: to a Network Share that in Windows Explorer in XP Mode the path is
\\tsclient\S\ . Is this normal?
Under Windows 7 the same share appears as S:\ as I would expect.
However, I would prefer not to have to map and un-map different Network Shares to drive letters.
It should have been mentioned in my first post, host is Windows 7 Professional 64 bit. I don't know the build but it is full retail version (not upgrade) from when first released - prior to SP1. All updates have been applied including SP1.
Any help would be appreciated.
Thanks.

Time Machine Can Be Made to work with a Network Share

FYI I am just posting this here for the benefit of the community. The source of this info is: http://forums.macrumors.com/showthread.php?t=375047
As I write this, I am doing a Time Machine backup to a ReadyNAS NV+ afp mounted share. Here is a summary of what the thread above says you need to do. It worked for me.
Take any supported USB standalone drive and plug it in to an available USB port.
Use Disk Utility to format the drive (or partition on the drive) and name that partition to whatever you want your network share to be called. In my case, I called it "office-tm".
After you do this, open the Time Machine preference panel and select that new drive (in my case "office-tm") to be the Time Machine backup drive.
After Time Machine sets up the drive, it will start counting down before the next backup. Press the little X on the right side to cancel the backup.
Now open a terminal session and change directories to /Volumes/<drive> where in my case <drive> was office-tm (cd /Volumes/office-tm).
When you do a ls -a -l, you will see two important files. One starts with a period (.) and contains numbers after it. The other one is called .com.apple.timemachine.supported.
What you need to do is copy these two files to your network share. The trick is that you want your network share to have the same name as this drive you just prepared (again, in my case it was called office-tm). I first created a new share on my ReadyNAS+ called office-tm and set the quotas properly.
Then you need to copy the files. There are several ways to do this but the way I did it was that I temporarily mounted the network share at a different mount point in terminal just to get the files over. So for example, I did:
sudo mount -t afp afp://<ip.addr.of.share>/office-tm /Volumes/office-tm2
Then I copied the two files over (substitute your appropriate volume names):
cp /Volumes/office-tm/.00whateveryourfilenameis /Volumes/office-tm2/.
cp /Volumes/office-tm/.com.apple.timemachine.supported /Volumes/office-tm2/.
Turn off Time Machine so you can unmount.
Now you can unmount both the USB drive and the network share and then you remount the network share as the proper name. The same one that the USB drive was named so as far as Time Machine is concerned, the volume is still there. The two files are on the network share so all is fine and Time Machine can find the volume it expects.
Wait for Time Machine to start it's hourly backup and away you go.
PLEASE NOTE THIS DISCLAIMER - There is probably a good reason why Apple disabled this feature so you might want to think carefully before you rely on this hack published in the MacRumors forum to back up your Mac. I am using this for testing purposes only and I am still using traditional backup techniques for my "real" backup of my office machine. If you don't get good Time Machine backups and you have relied upon them for critical data, don't blame anyone but yourself.

Name: RAIDiator
Version: 3.01c1-p6
Date: Tue Dec 12 17:46:22 2006
Size: 46566912 bytes
Reason: Final 6.
We should probably start a new topic in networking on this. I am seeing some strangeness with afp shares as well.
I have most shares set up to allow access by both CIFS/SMB and AFP. If I use Sidebar and try to access the shares by AFP, it says it can't connect to the server. But the same shares via CIFS works fine. (I can click on the "Windows" server icon and connect.) But for any of these shares, I can manually connect with the normal Go > Connect to Server... method, specifying afp://<ip address> and that works fine.
In the case of the Time Machine share that is the subject of this post, I disabled CIFS and am only using AFP because I wanted to make sure I connected to the share only via AFP for Time Machine purposes.
BTW, I do not use USER or DOMAIN security mode in my case and my shares are set up as SHARE security mode.

Windows Network Shares do not work properly

Ever since installing LEOPARD (now running 10.5.2) my network shares on our Windows server are not working properly. I can connect in the office via cifs:// and the share appears. I cannot copy a file to the share. I get the following message:
"The operation cannot be completed because you do not have sufficient privileges for some of the items."
There is an icon with a size of 0kb on the share, and if I try to open it or trash it, I get a message telling me it is in use by the MAC OS. I can open a file from the share, but if I try to save it back to the share or save from an application I get a "There has been a network file permission error."
If I try to copy the file to my desktop. I get a message that tells me that I don't have permission.
If I try to connect using https:// I get a username or password not valid message. Both of the connection methods worked BEFORE I installed LEOPARD. The install was a clean install, not an upgrade. I NEED to be able to access the shares for my work. The shares are on a server running Windows Server 2003 Service Pack 2.
How can I solve this? I actually have administrator privileges on the server with my login credentials, but this does not seem to matter.

Experiencing the same exact problems here. Brand new Mac Pro on a Windows 2003 Server network. Somehow I don't think it is any rights problems in my case, as I can create and erase folders (created by me or others), and the Mac writes the .DS_Store files to the server...
However, if I try to copy a single file or a folder containing files to the server, I get only a 0k file (inside the folder if I copy a folder) and after a while an error message saying the same things William Colvin2 mentions above (not sufficient privileges).
Everything I have read seems to indicate that there is huge problems with Leopard with regard to this, and if that is true, they need to be fixed ASAP. I think I've tried and tested all the possible "solutions" (disabling SMB digital signature, GPO policies, disabling IPv6...) but still no solution in sight.
Can we get some info from Apple on this whether it's being worked on, or what we can do to SOLVE this problem? As far as I know, Windows 2003 Server hasn't changed in that respect recently, whereas OSX has gone from 10.4 Tiger to 10.5 Leopard...
Any help with solving the problem is greatly appreciated, so feel free to respond with anything that might be helpful. I would also be interested in hearing from people who have HAD this problem, but has gotten them solved. And if so, what solved it for you.
Thanks in advance.

Network shares disappear from desktop

Hi,
I have searched but cannot find a thread which outlines the problem I am having.
I have a 40 strong iMac network with 2 Mac Mini servers. All iMacs are running Mountain Lion (10.8.2) with the Mac Mini's running Mountain Lion (10.8.2) and Server (2.1.1). I have a number of network shares defined which are hosted on a Pegasus array connected via a thunderbolt cable to one of the Mac Mini's. The shares mount as part of the login profile for each user.
The problem I am having is that the desktop icons for the shares randomly disapear from the desktop. This typically happens to 2, 3, or 4 of the shares but never all of them at once. When I go into the Connect to Server option in Finder and connect to the server hosting the shares they appear as available for connection (i.e. they are not greyed out as if an existing connection exists with the share).
As a general rule, the end users leave their machines on overnight and don't usually shut them down.
Can anyone shed any light as to why these shares seem to be randomly disconnecting / ejecting?
Cheers,
Tzukius.

Kevin,
All shares are done via AFP. When I look at the stats on the CPU on the server app it is hovering around 3-5% for a 4hr average.
One thing I have noticed is that on my machine I never lose the connections, co-incedentaly, my machine never enters sleep mode whereas the other machines are set to sleep after 30mins. I'm starting to think that this may be the cause of my problem, even though the ethernet interface is used for connecting the machines to the network and not the wireless connection (I had read on a couple of other threads that this can cause the disconnection of network shares).

Difference: 2 network share icons

Similar Messages

Maybe you are looking for