Iomega 2003 Storage Server AFP Shares not visible since upgrading to 10.5.6

Iomega suggested that I post here. No AFP shares are visible since I installed the suggested 10.5.6 OSX upgrades. Nothing changed on the Iomega 2003 storage server side and it been running fine with the shares visible for over two years. What has changed in OSX? DO I need to open something up now for security purposes?? PLease advise as I am dying here!!
Peace,
DIGJOE

After working with it some more... Have figured out that the "lock" screen is a security measure from the server software. somehow, I have it set [didn't mean to do this] to show that upon each reboot now, and I'm not sure how to disable it. I'll get into the server manuals and have to research that.
It also seems that the server software sees each HD as another computer somehow... and each partition as well. Curious... Anyway, once I got past the "loced" screen, the fresh install of the server software was in effect, and the primary HD is showing both patitions.
All is happy... [doing little apple happy dance]...
I zero'd out both of the new HD's, and am forgoing the install of the newer 10.5.6 on them. My 10.4.11 server is just fine actually, had no problems with it until I tried to upgrade. I suspect that the server software either wants only 10.4.11 server on everything, or somehow I must "tell " it to accept the other 10.5.6. Not real sure how to do that, however will put my muscles inbetween my ears in gear to think about for awhile.
Thanks for your assistance.

Similar Messages

Windows storage server 2012 share not connecting by share name but connecting thru IP address from windows XP machines

We have a windows storage server 2012 (HP storage server) in our domain. All of sudden We had a issue, connecting the server shares using the share name only from XP machines, but it is connecting through IP address with a delayed response. We are getting
the below error message from all the windows XP SP2 machines in our domain.
"\\<share name> is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have a access permissions.
Login Failure: The target account name is incorrect."
But it is connecting while we are trying from windows 7 machines. Also the other server shares (Windows 2003 server) are connecting without any issues using the share name. In addition to this we gave everyone permission for this share. And it worked
well before but not now. Could you please suggest any solution for this complex issue?
Thanks,
UdayaKumar S

Hi,
We are getting the below critical alert mail often from our storage server. This could be the problem?
vent from Blade NODE01.*****.com, In Enclosure: EM-E83935ED70F6, Network Interface Lost Connectivity.
Description: "A network interface has failed. An Ethernet adapter's status changed from OK to Error, or an Ethernet team's status changed to Error from another state."
Source: CIM Indication from CSP Provider
Date: 02-06-2014 Time: 18:52:26
Blade: NODE01.****.com
NetworkAddresses:
Severity is Critical
Recommended Actions: Check the network cables, switches, and hubs for the cause of the failure.
Note: For More information please refer the Windows System Logs in the Event Viewer

Printer shares not working since upgrade to samba 3.5.0 - SOLVED-ish

I share my printer with my wife's XP laptop and another linux box. This has been the position for the past 2 years or so, without any problems at all. Yesterday I did my first reboot for a couple of weeks, and the first, therefore, since samba / smbclient upgraded to 3.5.0. I can no longer print from the XP or other linux boxes. Samba logs the error as :
laptop (10.0.0.5) connect to service Oki initially as user visitor (uid=1001, gid=1001) (pid 12634)
[2010/03/13 18:31:51.509666, 0] printing/print_cups.c:108(cups_connect)
Unable to connect to CUPS server /var/run/cups/cups.sock:631 - Interrupted system call
Setting cups logging to debug, the closest entries to the above attempt is as follows :
D [13/Mar/2010:18:31:21 +0000] cupsdAcceptClient: 13 from localhost (Domain)
D [13/Mar/2010:18:31:21 +0000] Report: clients=1
D [13/Mar/2010:18:31:21 +0000] Report: jobs=500
D [13/Mar/2010:18:31:21 +0000] Report: jobs-active=0
D [13/Mar/2010:18:31:21 +0000] Report: printers=1
D [13/Mar/2010:18:31:21 +0000] Report: printers-implicit=0
D [13/Mar/2010:18:31:21 +0000] Report: stringpool-string-count=1334
D [13/Mar/2010:18:31:21 +0000] Report: stringpool-alloc-bytes=6496
D [13/Mar/2010:18:31:21 +0000] Report: stringpool-total-bytes=18208
D [13/Mar/2010:18:31:21 +0000] cupsdReadClient: 13 WAITING Closing on EOF
D [13/Mar/2010:18:31:21 +0000] cupsdCloseClient: 13
D [13/Mar/2010:18:31:21 +0000] cupsdAcceptClient: 13 from localhost (Domain)
I [13/Mar/2010:18:31:21 +0000] Generating SSL server key...
E [13/Mar/2010:18:32:12 +0000] Unable to create SSL server key file "/etc/cups/ssl/server.key" - No such file or directory
D [13/Mar/2010:18:32:12 +0000] cupsdCloseClient: 13
I am guessing tht the "WAITING Closing on EOF" part may be important.
Other aspects of samba do not appear to be affected. I can mount shares on the remote computers, use smbclient etc.
Googling is not getting me anywhere.
Any help will be greatly appreciated.
Last edited by perseus (2010-03-14 18:54:41)

I have had similar issues at my office.......I had a hylafax server (also sharing a couple printers via samba) running on debian 5 (samba 3.2) and upgraded it to debian 6 (samba 3.5). and it was samba printer sharing hell after that. What would happen is I would get samba logs full of the same jibberish
[2011/02/25 15:11:20.201234, 0] lib/util_sock.c:1432(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2011/02/25 15:11:20.201249, 0] smbd/process.c:79(srv_send_smb)
Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
[2011/02/25 15:43:20.134201, 0] lib/util_sock.c:675(write_data)
[2011/02/25 15:43:20.134220, 0] lib/util_sock.c:1432(get_peer_addr_internal)
getpeername failed. Error was Transport endpoint is not connected
write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2011/02/25 15:43:20.134234, 0] smbd/process.c:79(srv_send_smb)
Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
I only post this here since I think it was more of a samba problem than a debian problem and we seem to be the only ppl out there talking about it......... the getpeername seemed to be the problem (to me anyway) and what would happen on our 25 or so XP home clients is that you would print but it wouldnt go ANYWHERE. Cups was not even recieving the jobs since samba was not passing the jobs to cups.
It seems to me that the XP machines were not finding the server by its hostname so I messed around with changing the clients to map the printer by ip address instead of by hostname and it helped "some" but it still had big time glitchyness.
the only conclusion I could come to in my mind is that this reminded me of back in the day when we had a win98se computer sharing a printer and the windows XP systems would hang for up to 2 min while trying to access the printer. The problem back then amounted to win XP not wanting to downstep to the older way of windows98's password encryption. So I started changing my smb.conf to allow guest on the printer, changed the mask to 777 and I even wrote up a whole new smb.conf from scratch to work on security = share no authentication, allow from everyone 777 etc etc.............STILL had problems.
So I ended up throwing together a new server from a spare machine and installing debian 5.0.3 (with samba 3.2.5) and swapping it out yesterday........now EVERYTHING works fine.
my educated guess here is that the new samba is probobly geared more towards vista & win7 than it is XP (since XP is a pretty old dog these days). I would loved to have worked this issue out but we just could not have the downtime any longer......so it looks like I am not going to be updating for a long time (which I now is not really the best policy) but it has to work.
I hope this helps.....trust me you are not the only ones having this problem.

Font files corrupted via smb Win 2003 Storage Server

Files are accessed on a Windows 2003 Storage Server via smb.
I just received a "re-furbished" 27" iMac with Mac OS 10.8.2 installed. Any and all folders on the network containing Postscript font files show those files as grayed out. It appears to be limited to just Postscript fonts, NOT Truetype (.tt) or OpenType (.otf) fonts. It appears something is not recognizing the resource fork portion of the files (is it because they have no file extension?).
All other Macs on the network running older versions of the OS do NOT have a problem accessing Postscript Font files.
I'm just an end user looking for information I can pass along to our Network IT folks who apparently have limited Mac knowledge.
Any and all advice and/or technical resources would be greatly appreciated.

I do greatly appreciate the info in the "Font Management in OS X" article, but this does not begin to address the problem I tried to describe above.
The fonts in question reside in job folders on a network, running Windows Storage Server 2003 software and Mac users access those files via smb.
As needed, those fonts are copied from the network location to the application's font folder or to a local hard drive for loading via Suitcase Fusion. The activation of these fonts is NOT the problem. The font files, (specifically Postscript Font files), are marked as corrupted BEFORE they can be copied and activated.
This issue came about ONLY after I connected my new 27" iMac running OS 10.8.2 to the server. All other Mac users running older versions of the Mac OS did not have any issues, until the new Mac was thrown in the mix. Something in the Mac OS 10.8.2 or on the server is not recognizing the resource fork portion of the Postscript font files.
Once the folders containing Postscript fonts have been accessed by the Mac running OS 10.8.2, those fonts are then "corrupted," meaning any other users can no longer load those fonts as needed, because they are grayed out.
To underscore the significance of this issue, please understand that this is a prepress production workstation. The iMac was added because we could not install Adobe's CS6 Suite on existing hardware. Because of these issues, I can only use the new Mac to open InDesign CS5.5 and/or CS6 source files provided by customers, I then export an .idml file and work the job on my older "stable" Mac running Adobe's CS5 Suite.
So I hope you can come to understand that access to the exact versions of fonts used to create print production files is critical. Any substitution of fonts results in countless additional hours spent verifying that text wraps match previously printed samples exactly.
Few things are more frustrating than not having confidence in the integrity of files stored on one's own network. This is compounded by the fact that the "IT" function was outsourced to our company's headquarter's (offsite) years ago where the "IT" people seem to have minimal high-end knowledge of Macs.
Any other OS 10.8.2 users out there having this particular problem? Any other ideas?

HT3258 My Parallels program is now not working since upgrading my MacBook Pro to OS X Mountain Lion. I was wondering if there is a solution to getting this working again?

My Parallels program is now not working since upgrading my MacBook Pro to OS X Mountain Lion. I was wondering if there is a solution to getting this working again?

You just need to update it to the latest version. See:
http://kb.parallels.com/114449

Home sharing on apple tv not working since upgrade to yosimite

home sharing with my Apple TV (gen 3) and iMac not working since upgrading iTunes (12.0.01.26) and installing Yosemite (10.10) on my iMac (2008).
everything worked fine before this!

Hey stephenfromdominion,
Thanks for the question. I understand that you are experiencing issues with Home Sharing after upgrading to OS X Yosemite. For troubleshooting information, check out the following resource:
Troubleshooting Home Sharing
http://support.apple.com/kb/ts2972
Thanks,
Matt M.

Premiere Pro CC not will not open since upgraded to Yosemite on Mac early 2008?

Premiere Pro CC not will not open since upgraded to Yosemite on Mac early 2008?@

Have you informed Apple of your problem?
Yosemite sometimes has problems, often related to "default" permissions needing to be changed
-one person's solution https://forums.adobe.com/thread/1689788
-http://blogs.adobe.com/creativecloud/creative-cloud-and-yosemite/
-https://helpx.adobe.com/x-productkb/global/mac-os-yosemite-compatability.html

OS X 10.6.5 Server AFP share - can't change group from 'staff' ???

Hi,
I'm running a new 10.6.5 XServe within a corporate AD environment. Well, when I say 'running' I mean testing - I could never let this odd beast loose on anyone with the awful state it's in.
Trying to set up the AFP shares, I simply wanted to assign one of our AD groups as the POSIX group for the share, just as I do on our existing Tiger server. 'simply' he says... oh I wish!
Server Admin 'lets' me change the group, then puts it right back to 'staff' again as soon as I hit Save. Same result when trying to change the Owner too, but I'm not needing to change that.
From Terminal, the usual permissions commands have no effect either. Try chgrp MyGroupName MyFolderName.
Tried changing while logged in as either root or admin, no difference.
So, all I want to do is change the group that's assigned to a share's POSIX permissions. Am I expecting too much from SL? Anyone else had this problem, and know the trick to solving it?
Can't believe this is happening - something so basic and important. I've wasted countless hours already with numerous other SL issues. Wish I'd never set eyes on the thing but it's been forced down my throat - we needed a new XServe, which turned up with SL installed of course. I'd gladly do a clean install of plain Leopard over the top, but apparently that's asking for (even more) trouble.
This POSIX nonsense is just the latest obstacle I need to get sorted.
Thanks for any help,
Paul.

Hi,
I'm running a new 10.6.5 XServe within a corporate AD environment. Well, when I say 'running' I mean testing - I could never let this odd beast loose on anyone with the awful state it's in.
Trying to set up the AFP shares, I simply wanted to assign one of our AD groups as the POSIX group for the share, just as I do on our existing Tiger server. 'simply' he says... oh I wish!
Server Admin 'lets' me change the group, then puts it right back to 'staff' again as soon as I hit Save. Same result when trying to change the Owner too, but I'm not needing to change that.
From Terminal, the usual permissions commands have no effect either. Try chgrp MyGroupName MyFolderName.
Tried changing while logged in as either root or admin, no difference.
So, all I want to do is change the group that's assigned to a share's POSIX permissions. Am I expecting too much from SL? Anyone else had this problem, and know the trick to solving it?
Can't believe this is happening - something so basic and important. I've wasted countless hours already with numerous other SL issues. Wish I'd never set eyes on the thing but it's been forced down my throat - we needed a new XServe, which turned up with SL installed of course. I'd gladly do a clean install of plain Leopard over the top, but apparently that's asking for (even more) trouble.
This POSIX nonsense is just the latest obstacle I need to get sorted.
Thanks for any help,
Paul.

AFP shares not showing in Sidebar

I am having problems getting afp shares to show in the Shared section of the Sidebar. The Sidebar is showing two of the SMB shares but nothing else. All of the AFP shares show on the other two Leopard computers. I have tried the following:
1. Turned Bonjour computers on and off in Finder Preferences.
2. Use DiscWarrior to clean the disc and have repaired permissions several times.
3. Tried deleting the com.apple.network.identification.pist file.
Any other ideas?
Thanks for any help.
Peter

I have this problem from time to time. To get them to show, in the Finder I go to Go > Connect to Server > then click on Browse. The will not show them in the left sidebar, but will show under the Network. I know it does not solve the problem. I'd like to know a fix as well.

Visa server security tab not visible

I want to enable the visa server for remote visa connections to the serial port, when I go into MAX to setup the visa server security the tab is not visible. I have a 2nd system and I can see the tab. Is some setting needed to enable the security?

Hello Chris,
I would expect that this is because of a version difference in your two machines. What OS are they? What version of VISA are they using? You can see the VISA version in MAX under the software folder. Also, to clarify, are you speaking about the "VISA Options" tab that appears when you select NI-VISA from the software folder, or something else?
If you need to download a newer version of VISA, see here for all VISA versions:
http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BAC002C51FA?opendocument&node=132070_US
Hope this helps.
Scott B.
Applications Engineer
National Instruments

Server side includes not visible on apache

Hi when i upload an HTML file with includes on an apache server the includes are not visible. I used the "virtual" parameter. on a windows server it works, also local works everything great. i also tested with PM "file" didn't work. can someone help me out? Thnx

>Hi when i upload an HTML file with includeson an apache server the includes are not visible.
The includes are not visible, but is the include code visible in the source code? That will tell whether the server is parsing for includes. By default, the server is probably set not to parse .html files for includes. Read the link that SnakEyez suggested, but also be aware that you can configure your server to parse .htm(l) for includes.

Trouble connecting to Lion server AFP shares after changing server's hostname

Hello everyone,
I recently changed hostname of my Lion server box (via Server application) and now my clients are having a problem when trying to connect to its AFP shares via aliases. It takes 160 seconds of "resolving alias to <sharename>" before it finally works. Aliases were created by navigating to the server, connecting with "Connect As", providing valid credentials, then navigating one level up and dragging the share icon (blue disk with three white people outlines) to the Desktop with Option-Command.
What is interesting, if I create a new account on a client machine, create an alias, and click on it - it works without any delay, as it was for the clients that are having problems now; so I'm assuming some details about the previous server name got cached somewhere.
The clients with long delay problems can access the shares quickly if they click on the server in the Finder window drawer, then "Connect As" and provide their login credentials - it works instantly then.
I've been digging around quite a bit (deleting Keychain saved Network passwords for any and all references to the server I could find), and also by looking at kerberos logs on the server. What is interesting, the newly created clients I mention above who don't have delay with connecting, don't leave any records in the kerberos log file; but the ones that have 160 second delay do - there's nothing for 160 seconds, and then there is a flurry of activity, as the connection is finally established.
When a client who has trouble connecting uses the "Connect As" method described above, entries in the Kerberos log are created instantly when client clicks connect.
Probably also worth noting that renaming of the server was related to me setting up Open Directory on it.
Any pointers would be greatly apprecited.

I experienced almost exactly the problems you described. I also found that connecting via command line using mount_afp worked right away... and once the connection is established, mounting via finder was super fast.
Tried all kinds of craziness on the client, even a full Time Machine restore.
Tried fixing Open Directory.
I was absolutely stumped by what was happening, but then thought, Hmm. I'm wondering if it's related to MobileMe going down? I noticed it started to happen after July 31...
Success! That was it! Signing out of MobileMe in System Preferences made everything work the way it should!
CDPlayer2: check if the clients are signed in to MobileMe, and if signing out fixes things - I'd appreciate it if you could post your results. Thanks.

Account Assignment data in Shopping Cart not visible after upgrade of R/3

Hello,
We are currently working with SRM 5.0 and R/3 4.6 Backend system.
We are now upgrading our R/3 system from version 4.6C to ECC 6.0.
When we try to create a shopping cart, the account assignment Tab is not visible.
We checked the RFC (SRM-R/3 and R/3-SRM) and they our working fine.
Now we think the problem is caused by a configuration setting in which one defines the Backend System. In this configuration, the system category is still set to 4.6C (for the logical System of the Backend System)
We want to change this but in our list of system categories, the ECC 6.0 option is not present!
Questions:
1. Is this configuration setting the cause for our account assignment tab problem?
2. How can one add the System Category ECC 6.0 so it will appear in the configuration setting "Specify Backend System" ?
Anyone had experience with this? Please give us a clue.
Thanks in advance.
Aart

Hello Aart,
You can choose the ERP_2.0 option. It contains the correct structures for the new ECC 6.0 system.
You can change it and retest.
Kind regards,
Ricardo

HT1338 outgoing e-mail server not working since upgrade to mountain lion

unable to send mail on one of my e-mail accounts since upgrading to mountain lion

I had this problem as well after upgrading to 10.8.
For all e-mail accounts SMTP servers seemed to be unavailable to Mail, regardless of setting TSL/SSL on or off. It turned out, even Thunderbird was unable to send any mail.
After trying every hint on this forum twice – and to no avail; I found the culprit to my problem. Upgrading my iMac to Mountain Lion had changed the name, that my machine was using in my home network. The new machine name had "(2)" added to the old name. The brackets seem to have disturbed the SMTP servers I use. After changing the name back to anything w/o special characters I was able to send mail again.
Very strange, since no error message lead to this direction, and only the SMTP was affected, everything else on the internet worked like a charm.
So if you run into this problem, and no other solution works for you, make sure your LAN-name is not including any special characters, just letters, numbers and "-".
Mind you: the name I am relating to is not necessarily the one you give your Mac in System Preferences > Sharing. It is the name your home router derives from that name. I am using a Fritzbox as a router and DSL modem; and had to access its web interface to check the actual name that my iMac was using to communicate to the web. That's also where I had to change the name back again.
Don't know why ML caused the name to change in the first place, maybe the whole thing was unrelated and purely incidental to upgrading to 10.8. Using another router your mileage may also vary. You may still give it a try.

AFP won't connect since upgrading to Mavericks

Since upgrading to Mavericks I cannot connect to my QNAP TS-210 via AFP; this means my Time Machine can no longer find my backup disk and no longer works. Anyone else having similar issues?
I have tried the usual quick fixes:
Firmware is up to date
All OS updates installed
Server reset
DHCP renewed
DHCP switched to try manual setup
IP changed on server and Mac
It's odd as when connecting to server I can enter my login ID and it seems to be validating it ok but then doesnt connect to the server at all?
Any suggestions welcome!

Use a supported Time Machine configuration.
OS X Mountain Lion: Disks you can use with Time Machine
"Note: Some AFP disks from manufacturers other than Apple don’t support Time Machine. If your network uses an AFP disk, but the disk doesn’t appear in the list of devices available for Time Machine backups, contact the disk’s manufacturer."
Your complaint is very common with NAS devices. Some work and some don't. If they appear to work, they may fail upon attempting to restore from the backup, or they may fail every time Apple updates OS X. Given the goal of a backup strategy, using anything other than a supported TM configuration is not an option.

Iomega 2003 Storage Server AFP Shares not visible since upgrading to 10.5.6

Similar Messages

Maybe you are looking for