AL11 view of Intel Server Share via QNTC ?

Hello,
I am going to try read directory on Intel server from iSeries via QNTC.
I created on Intel server the same user and Password like iSerie.
Unfurtunatly, the procces work when I use "wrklnk" on 5250 screen, but it doesn't work wtih transaction AL11 from SAP.
Do you have some way to help us.
Thank you.

Hello Bruno,
which user did you create on windows and check the password ?
Was it sidofr, sidadm or sidnn ?
SAP typically uses sidnn only ...
In general, your approach works and is used by several customers.
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de

Similar Messages

Setting Default Views of Mounted Server Shares

In OS X 10.5 server, how do I change the owner of a volume? So I can do the stuff below? Do I change the owner in the Finder...? Or do you use the OS X Server admin utility type programs?
Thanks
Re: Setting Default Views of Mounted Server Shares
Posted: Dec 18, 2007 9:49 AM in response to: William Read
Solved
Have you tried this?
http://docs.info.apple.com/article.html?artnum=107482
You can set custom view options (window size, icon placement, and so forth) that clients see when they connect to a server volume via Apple File Service (AFP).
You can customize the size, position, and other view options of the window that clients see when they connect to a server volume via Apple File Service (AFP). You can do this on a per-volume basis.
To customize view options, follow these steps:
1. Log in to a client computer.
2. Using Connect to Server, connect to the target volume as the owner of the volume; the owner must not be an administrator account (see Notes 1, 2, and 3, below).
3. Make any desired changes to the window position, view mode (Icons, List, Columns), icon arrangement, or any of the settings found in View Options window (Command-J).
4. Disconnect from the server volume by dragging it to the Trash.

In OS X 10.5 server, how do I change the owner of a volume? So I can do the stuff below? Do I change the owner in the Finder...? Or do you use the OS X Server admin utility type programs?
Thanks
Re: Setting Default Views of Mounted Server Shares
Posted: Dec 18, 2007 9:49 AM in response to: William Read
Solved
Have you tried this?
http://docs.info.apple.com/article.html?artnum=107482
You can set custom view options (window size, icon placement, and so forth) that clients see when they connect to a server volume via Apple File Service (AFP).
You can customize the size, position, and other view options of the window that clients see when they connect to a server volume via Apple File Service (AFP). You can do this on a per-volume basis.
To customize view options, follow these steps:
1. Log in to a client computer.
2. Using Connect to Server, connect to the target volume as the owner of the volume; the owner must not be an administrator account (see Notes 1, 2, and 3, below).
3. Make any desired changes to the window position, view mode (Icons, List, Columns), icon arrangement, or any of the settings found in View Options window (Command-J).
4. Disconnect from the server volume by dragging it to the Trash.

Leopard client controls view of tiger server share point

Hi, recently purchased a Mac Mini running Leopard all patched. Connected via afp to a Xserve RAID, Xserve running a sharepoint using ACL's. In list view the leopard client controls the list view on the Xserve, meaning that all the other Tiger clients see the leopard clients folder structure when they connect to the sharepoint. I have not changed any settings on the Xserve, just re-propogated the permissions and ACL's.
Any ideas would be great,
Andy

ipb1962 wrote:
BUT When I use the DHCP service to specify my DNS to a Leopard Client from (Tiger Server on a G5)
it does not resolve to any internet address.
Can you clarify what you mean here?

Can't connect my Mac to my Windows 2003 server shares via SMB

Hello all
So my problem is I have my Powerbook running 10.4.7 with all the latest security updates and I cannot connect it to any shares on my Windows 2003 domain controller. Everything was working fine and I could connect to the server with no problem till about a month ago. However, I can still connect to the Windows 2000 domain controller with no problem. The error I get when trying to connect is "Could not connect to the server because the name or password is not correct". I did try clearing out my keychain, making sure all of the authentication policies on the server are correct (disabling the digitally sign commucations always policy), and I even went as far as editing a .conf file in /etc/ folder that allows for passwords to be sent without any encryption (I forget exactly what I changed but I can post that later when I get home from work) and none of this has worked. I unfortunately don't have another mac to test out connecting to the Windows 2003 server. Does anyone have any ideas of what I could do to try and get this issue resolved?

TO share out as afp you need to have file and print services for macintosh installed on the 2k3 Server.
O n the main management console click on the shares icon on the left. then click the "link" create a share. The wizard will guide you through the process. i forget the order of progression but i beleive its the second or third part in the dialog it will have 2 check boxes, the top one checked by default, is to share it for windows/smb the second (lower box) is to share as AFP for mac check this box and change the share name if you like. then proceed through the rest of the wizard. Make sure you configure the security/sharing prefs for access.. we typically remove the everyone policy and add one for Authenitcated Users, and ofcourse Administrators.

Windows 7 Client 'sees' an old version of windows 2012 server share

Hi All,
I have a problem which seems to be a common theme looking at other threads. Here's the overview of the problem:-
I have multiple windows 7 clients and a windows 8.1 client within a 2008 Server in a domain.
I also have a Windows 2012R2 Server which is not joined to the domain. There is a Share on the 2012R2 which has the Caching Option turned off. Everyone full control on Share & File permissions.
One of the Windows 7 machines in Explorer when it looks at
\\2012server\share sees an old version of the folder. It seems that SMB 2 chaching is working too well. Not even pressing F5 or clicking View, Refresh updates windows explorer.
It took a reboot to get the workstation to see the up to date contents of the share on the 2012 server.
We don't seem to have that behaviour with that client against the 2008 server.
I have seen this behaviour on another machine un-related to us at another location which was in a workgroup with a 2012 server and no domain.
Questions:-
Is there some sort of problem with Windows 7 workstations working against 2012 Servers in a non-domain setting or is it just Windows 7 against 2012 servers period?
I understand that Windows 7 utilises SMB1 & SMB2. SMB2 introduced caching. If the server has turned off the share cache option should the client cache the contents of the share or the information about the files & folders & 'file not found'
information?
I want to open a file handle to a file on a network share so I can read and write data to it. But I also want to know that when I look at the folder to open the file I'm actually looking at the live version of the folder and files in the folder and
not a cached version of the folder. If it's a cached version the file might be there already but I won't see it.
Is there an API call that tells the client to get a fresh view of the server share so I can be absolutely sure that when I look for a file on the server I'm getting the correct answer and not one from cache.
I first posted the question with the same subject "Windows 7 Client 'sees' an old version of windows 2012 server share" in the Windows 7 Networking Fourm
https://social.technet.microsoft.com/Forums/en-US/23bf3627-987b-4c27-8062-85a284a2cda4/windows-7-client-sees-an-old-version-of-windows-2012-server-share?forum=w7itpronetworking and it was suggested I repost in here. Please do take the time to read
the thread which will save time with suggestions that have already been covered.
As the computers that can be affected by this problem are not mine I cannot enforce or guarantee that any of my 'client base' will apply any hotfixes. I will also not have the ability to tweak registry settings as I can't guarantee Admin Access.
It seems that we need to go back to SMB1 as all the tweaks to SMB since those days have introduced problems with the basic requirement of sharing files from a share on a server for Read/Write purposes. I have tried turning a network back to SMB1 and that
has resolved a lot of the issues but then I found a post/MS blog that states not to leave the network on SMB1
The Caching option of the share had already been turned off. Surely Windows clients should not cache any information about the share but I think that is not the case.
Thanks is advance
Robert

Hi Shaon,
Thanks for looking into this.
If this is a known issue, why isn't the hotfix rolled into a general windows update if this is a known problem? However this doesn't just affect domain joined workstations.
Surely it's basic functionality for a networked computer to access files and folders on a network file server. It's what networks were invented for at the end of the day.
I am unable to apply hotfixes to these computers that are having the problem due to the fact they are not mine but my customers.
At one of my customers sites I disabled SMB2 from the server and network clients as well as disabling the network adapter power saving option. This seemed to resolve the issues that I saw on one client that seemed to be 30 minutes behind the rest of
the network. The hotfix you link to states that it is for Domain joined computers. At my customer site the PC's are not in a domain at all, just a workgroup with workstations and a 2012r2 server. Will the hotfix be applicable to non-domain machines?
Also many clients seemed to loose the file handle to an open file on the server. I'll get them to turn SMB2 back on at some point after I send out some updates but all the problems I see seem to be caused by the caching functions in SMB2. SMB1 is good and
stable. It's SMB2 that seems to be causing the problems as it was designed from the ground up for caching.
Has this networking issue been resolved in Windows 8, 8.1 and 10?
As I am unable to apply a hotfix to 1000's of PC's that are not mine, is there an API call or something where I can get the windows client to stop lying and get me the current state of a folder on the server?
Will Turning off ClientSideCaching fix the issue? HKLM\SYSTEM\CurrentControlSet\Services\MrxSmb\Parameters\
CSCEnabled
Or will every machine need to be tuned individually according to the following guide:-
https://social.technet.microsoft.com/Forums/windowsserver/en-US/7bd9978c-69b4-42bf-90cd-fc7541ccb663/forum-faq-troubleshooting-network-file-copy-slowness?forum=winserverPN ?
Robert

Mavericks 10.9.5 cannot connect to windows share on server 2008r2 via SMB or CIFS

hey anyone,
on several macs at a client all running Mavericks 10.9.5. everything was working smooth.
then all of a sudden anytime i try to connect to a specific share on server 2008r2 via SMB or CIFS.
it connects (with authentication). but the share wont open. and crashes the finder. everytime.
i can open other shares on the same server without any problems.
i've tried this on several machines all with a similar result.
all permissions on the server are correct as well as on all Macs.
anyone have any similar issues and a way to get the finder from crashing?
will updating Yosemite help? or create more problems with SMB connectivity
help
GT

2) Try to connect using AFP address:
9/20/14 3:43:54.980 PM NetAuthSysAgent[540]: AFP error -1 mapped to EIO
9/20/14 3:43:54.980 PM NetAuthSysAgent[540]: ERROR: AFP_GetServerInfo - connect failed 5
9/20/14 3:43:54.980 PM NetAuthSysAgent[540]: AFP error -1 mapped to EIO
I'm getting the same error messages when trying to connect over a VPN to a Mountain Lion server, from a Yosemite (10.10.2) iMac. The same Yosemite iMac at the same time has no trouble connecting to a Snow Leopard server on the same network.
By the way, there is no such thing as a "G5 (Intel) Mac". What you have is a Mac Pro tower. The G5 processors predated Intel. A lot of people tend to use "G5" as a generic term for a Mac aluminum tower. Why does it matter? Because if you not had not said "Intel", you would be getting replies having to do with the age of the computer in question.

Iphoto can't share via email; error message: Your email did not go through because the server did not reply.

I can never share via email, using iPhoto. The error: Your email did not go through because the server did not reply. always pops up. I have no problems with my server or internet connection.
Any ideas?
thanks.

Go into iPhoto's Accounts preference pane and delete the email account there. Then add it back. If that fails you can select Mail as your email client in iPhoto as that's more reliable and flexible. It also offers stationary for photos that are not unlike those in iPhoto's client:
and using Mail as the client will allow you to have a Sent copy automatically.
OT

Access to Samba\vfiler share via shortname

I wasn't sure which section to post this under as it occurs on different
operating Systems (Windows XP SP3, WIndows 7, Windows 8, Server 2003, Server
2008) and is random.
Basically, some of our end users experience problems accessing shares to a
vfiler for example with shortname \\example\share.
They can access this specific share via ip address or fqdn
\\example.domain.local\share. The
user can even access \\example and be
able to
view shares there but when clicking on the share it comes back with network
error or access denied.
This does not happen to all users at a time and on the same
workstations\servers and there are no specific times. On the end users
workstation DNS and wins is working, they have
no problems accessing other
vfilers or F&P Windows shares.
I tried all flushing DNS and wins cache, tried rebuilding CSC (Offline files)
to no avail. We don't have this enabled in our environment in any case
but
gave it a try.
One way I got it working via shortname is by adding a new security group to
the security permissions on the share. The group only had my account as a
member
and exsiting groups remained. After this the end user was able to map
via shortname.
I've tried many things and just can't figure this out or where to look. My
team doesn't manage the vfilers or samba shares so
can't look at the logs or
anything.
Another scenarion I have is for a Samba share, very similar situation but
this time its accessing the share on a Windows 2008 R2 server.
Basically
similar symptoms, can't access via shortname, get 'Network Error', tried several
things, even Windows Network Diagnostic
where it states that "The remote
device or resource won't accept the connection', "The device or resource (samba)
is not setup to accept connection
on port "The File and printer sharing
(SMB)". Port 139 is open, can access other shares on different storage devices
successfully.
What's weird is that after some time, An hour, 2 or 3 later functionality
returns without any changes. Obviously restarting the server resolved this
quicker.
There are no scheduled tasks or tasks running in the background,
Windows firewall is disabled, disabled AV etc.
I managed to get a log from this Samba device but not sure if its
related or not.
[root@samba] [09:30:52] /var/log/samba
# tail /var/adm/messages
Apr
3 08:33:06 samba adbindd[24524]: [ID 323999 auth.error] ERROR samba.adbindd2
Task exit with cims error: Error sending response: Broken pipe
Apr 3
09:10:07 samba adbindd[24524]: [ID 323999 auth.error] ERROR samba.adbindd2 Task
exit with cims error: Error sending response: Broken pipe
Only other thing I can think of is that is may have something to do with the
device, folder redirection, cache or something of that sort.
I'm stuck, anyone have any ideas. I would like to know what else to try if
the issue re-coccurs.
MCSE: 2003, MCITP: Enterprise Administrator, MCITP: Enterprise Messaging Administrator

Hi,
I installed KB 2194664 and haven't had the problem since.
http://support.microsoft.com/kb/2194664
If it happens again I will revisit.
Thanks.
MCSE: 2003, MCITP: Enterprise Administrator, MCITP: Enterprise Messaging Administrator

Accessing Windows CIFS Shares via Nautilus

Hi,
I've recently installed and configured Solaris 11, am having problems accessing Windows CIFS shares via Nautilus.
I've installed both samba (needed for CUPS to print to printers connect to a windows pc) and smb/client. The smb/client and samba services are running. The smb/server service is not installed.
I can print to any printer on the windows PC I'm trying to access via Nautilus, so I know my username/password for accessing the pc are correct.
I can also manually mount any share on the windows PC via the cli (eg mount -F smfs -o user=elin //elink/users /mnt), and browse the files directly that way, except the file permisssions don't seem to align with any unix user. Again this just shows that the username/password combination is ok.
For Samba, I'm using the default smb.conf file as /etc/samba/samba.conf. Workgroup is set to WORKGROUP in smb.conf.
On the Windows pc, in the security event viewer, I can see the auth request, however is failing with bad password (event ID 4776, error code 0x006a). In the default group policy object for networking, I've set to accept "LM & NT, NTLMv2 when neogiatated", as this allows legacy clients to connect. (Legacy meaning NT4, Win95, etc, and also has the benefit of allowing other OSes to connect as well).
I'm also able to access the WIndows PC CIFS shares from an Arch Linux based setup (running GNOME 3.2 w/ Nautilus 3.2), so I doubt it's the Windows side of things causing the problems. Additionally, when I was running Solaris 10u9 (just before upgrading to Sol11), I was able to access the shares via Nautilus as well.
So my question is:
1. Does Nautilus use Samba or the Oracle smb/client service to handle mount windows CIFS shares?
2. What log files or configuration files do I need to looking at to help with this error?
As a side question,
I've found that on a clean installation running the "Print Manager" accesses CUPS fine, but once you install a printer, it'll no longer connect to CUPS, unless run from the cli "sudo system-config-printers". So this is a permissions issue, where's the best place to fix/handle that one.

Replying to my own thread, as I have a possible but very-hackish solution.
To add some further details to my original post.
There are 4 PCs on the LAN.
1. Hellfire - OS = Solaris 11 11/11
2. Brimstone - OS = Arch Linux
3. Elink - OS = Win7 Pro x64 SP1
4. IsaacPC - OS = WinXP Home SP3
Attempting to connect to Elink from Hellfire, accessing CIFS shares via Nautulis fails. (Mounting shares via Nautulis fails, but works fine from CLI using 'mount' command which to my understanding uses the smb/client service to work). Elink also hosts all the printers on the LAN, a HP LJ1200 and an Epson Fax/Printer/Scanner.
Helfire does attempt to authenticate, as listed in the event logs on the Win7 PC (elink), but is returning bad password when using Nautulis. (but printing from hellfire to either printer on elink works fine, as does mounting CIFS shares using 'mount').
Booting the live CD of Solaris 11, also exhibits the same non-working behaviour when attempting to mount CIFS shares in Nautulis.
Attempting to access CIFS shares on elink from Brimstone (via Nautulis 3.2 within GNOME 3.2), or from IsaacPC works fine.
Hellfire configuration.
Samba is installed, but NOT running (samba is needed for accessing the printers on elink, as CUPS needs smbspool which is part of the samba package), and the native smb/client service is also running.
smb.conf is a direct copy of the default *.conf file, except the WORKGROUP is set to 'WORKGORUP'. There is a symlink to smb.conf in /etc/sfw/smb.conf -> /etc/samba/smb.conf
Onto the hackish-fix.
I've noticed that there are 2 copies of libsmbclient.so installed on the system, one in /usr/sfw/lib (part of the "libsmbclient" package) and another in /usr/lib/samba (part of the "samba" package).
"libsmbclient" appears to be based on samba 3.5.8 codebase, and is linked to the gvfsd-smb daemon (this is the software that Nautulis uses to talk SMB to access CIFS shares).
"samba" is based on the samba 3.5.10 codebase, and it's installation has nothing to do with GNOME or Nautulis in any manner.
Using any of the samba included tools to test SMB/CIFS functions, work with 1 minor exception (which I'll list below). eg, using smbclient I can list all shares on any PC on the LAN, etc.
So as a hunch, I renamed the libsmbclient.so.0 in /usr/sfw/lib, and symlinked /usr/sfw/lib/libsmbclient.so.0 -> /usr/lib/samba/libsmbclient.so.0 (so that gvfsd-smb is linked against the slightly newer version of the libsmbclient.so as included in the samba package located in /usr/lib/samba).
I rebooted Hellfire, and now I'm able to access CIFS shares via Nautulis, provided that some form of authentication is needed (that is a username and password is needed - guest access and blanks passwords don't work - but these IMO should be disabled immediately as part of a baseline security package in regards to Windows - so no harm there).
Now to the minor exception I noted earlier. When using smbclient to actually connect and transfer files, I get:
ld.so.1: smbclient: fatal: relocation error: file /usr/lib/libreadline.so.5: symbol tgetent: referenced symbol not found
As far as I know, tgetent is part of libtermcap.so, so I guess when building smbclient or libreadline.so, the link reference to termcap was left out? (or something like that). Anyway, that's another issue...

Unable to view files from windows share

Hi guys,
I am wondering if you can help me out. I have 10 mac ocnnected to a windows domain. Five machinies are OSX 10.5.8 and five are OSX 10.6.8. The problem I am having is I can connect to the windows share via smb but I am unable to view the files. I can connect the server and see the folder listings but I am unable to view the contents of each directory. The users permissions are fine as they can log into a windows PC an are able to access the files as needed. I have tried different user accounts and all are getting the same issue. Each account has admin rights as well. I was wondering if anyone else has seen this issue before?
Thanks in advance!

files like movies or pdf files. Under the apps section, I can't see any way to transfer files.
Also do I need to completely sync my ipad, if i click sync then after a while it says can't sync all the apps present on the ipad

Server 2012 R2 SMB - The process cannot access the file '\\server\share\test.txt' because it is being used by another process.

Hi,
We are having issues with Server 2012 R2 SMB shares.
We try to write some changes to a file, but we first create a temporary backup in case the write fails. After the backup is created we write the changes to the file and then we get an error:
The process cannot access the file '\\server\share\test.txt' because it is being used by another process.
It looks like the backup process keeps the original file in use.
The problem doesn't always occur the first time, but almost everytime after 2 or 3 changes. I have provided some code below to reproduce the problem, you can run this in a loop to reproduce.
The problem is that once the error arises, the file remains 'in use' for a while, so you cannot retry but have to wait at least several minutes.
I've already used Process Explorer to analyze, but there are no open file handles.
To reproduce the problem: create two Server 2012 R2 machines and run the below code from one server accessing an SMB share on the other server.
Below is the code I use for testing, if you reproduce the scenario, I'm sure you get the same error.
We are not looking for an alternative way to solve this, but wonder if this is a bug that needs to be reported?
Anybody seen this behavior before or know what's causing it?
The code:
string file =
@"\\server\share\test.txt";
if (File.Exists(file))
File.Copy(file, file +
".bak", true);
File.WriteAllText(file,
"Testje",
Encoding.UTF8);
The error:
System.IO.IOException: The process cannot access the file '\\server\share\test.txt' because it is being used by another process.

Hi,
There is someone else having the same issue with yours. You could try code in the article below:
“The process cannot access the file because it is being used by another process”
http://blogs.msdn.com/b/shawncao/archive/2010/06/04/the-process-cannot-access-the-file-because-it-is-being-used-by-another-process.aspx
If you wonder the root cause of the issue, the .NET Framework Class Libraries forum can help.
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How do I create a view in SQL Server in Visual Studio Express 2013 for Desktop?

Hi
I've got a SQL Server database set up using the internal SQL Server in Visual Studio Express 2013 for Desktop. I want to create a view (using tables with one to many relationships) but I don't
know how to do it.
Where can I find a good tutorial on creating views in SQL Server in Visual Studio Express 2013 for Desktop? I think Visual Studio Express 2013 for Desktop doesn't have some view designer that
exists in the non-express version of Visual Studio (if I'm not mistaken). So I think I'd need a tutorial on how to do the actual SQL, unless there is some tool I don't know about.
Thanks

Hi ,
According to your description, if you install SQL Server SQL Server 2014 Express and SQL Server Manager Studio tools (SSMS), if you want to create a view, you can use SSMS. Then if you want to connect to and Diagram your SQL Express Database in Visual Studio
2013, you can attach the database file by using the .NET Framework Data Provider for SQL Server in Visual Studio, and create a database diagram via expanding the “Database Diagrams” node.
For more information, there is similar issue about how to connect to and Diagram your SQL Express Database in Visual Studio 2012 , you can review the following article,
http://blogs.msdn.com/b/bethmassi/archive/2011/10/27/how-to-connect-to-and-diagram-your-sql-express-database-in-visual-studio-lightswitch.aspx.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Flat file connection: The file name "\server\share\path\file.txt" specified in the connection was not valid

I'm trying to execute a SSIS package via SQL agent with a flat file source - however it fails with Code: 0xC001401E The file name "\server\share\path\file.txt" specified in the connection was not valid.
It appears that the problem is with the rights of the user that's running the package (it's a proxy account). If I use a higher-privelege account (domain admin) to run the package it completes successfully. But this is not a long-term solution, and I can't
see a reason why the user doesn't have rights to the file. The effective permissions of the file and parent folder both give the user full control. The user has full control over the share as well. The user can access the file (copy, etc) outside the SSIS
package.
Running the package manually via DTExec gives me the same error - I've tried 32 and 64bit versions with the same result. But running as a domain admin works correctly every time.
I feel like I've been beating my head against a brick wall on this one... Is there some sort of magic permissions, file or otherwise, that are required to use a flat file target in an SSIS package?

Hi Rossco150,
I have tried to reproduce the issue in my test environment (Windows Server 2012 R2 + SQL Server 2008 R2), however, everything goes well with the permission settings as you mentioned. In my test, the permissions of the folders are set as follows:
\\ServerName\Temp --- Read
\\ServerName\Temp\Source --- No access
\\ServerName\Temp\Source\Flat Files --- Full control
I suspect that your permission settings on the folders are not absolutely as you said above. Could you double check the permission settings on each level of the folder hierarchy? In addition, check the “Execute as user” information from job history to make
sure the job was running in the proxy security context indeed. Which version of SSIS are you using? If possible, I suggest that you install the latest Service Pack for you SQL Server or even install the latest CU patch.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

SL server share mounting not working for 10.7.4 Mac Mini

I'm running about seven Macs on a network with a 10.6.8 Mac Mini server.
The older Macs (PPCs and 10.4.11) mount the share immediately.
Newer Macs recently have had a problem.
My 10.6.8 MBP can mount the share, from a dock icon, but it can take minutes.
Another Mac Mini (10.7.4) now refuses to mount the share manually. It can't make contact with the server share. I've tried via Ethernet and WiFi. It just hangs with Connect to Server.
And yet, it has no problem with the iCal server running on the server.
Another older MB and 10.6.8, mounts the share immediately.
Has anyone had newer hardware with 10.7.4 develop server connection problems?

Hi iToaster,
These were all good tips, and I tried or investigated them.
As it turns out, I noticed my SL Mac server needed a Java and securtiy update.
After installing, mount time on my Lion and SL client Macs was near normal, not minutes. (Again, my older Macs had mounted the server share quickly and normally, when the newer ones did not.)
My suspicion is that a modern OS sensed that the Java and security updates were not in place and took extra time to check the share mount in some manner.
Thank you for your time, experitse and ideas, iToaster!

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.

AL11 view of Intel Server Share via QNTC ?

Similar Messages

Maybe you are looking for