Older Clients cannot Authenticated to 10.10 Server ( Also SMB issues)
Hello
I am having a few issues with Server.app ( running on 10.10.2)
It appears older clients ( tested but 10.6 and 10.7) cannot log into the servers open directory. They can bind to it but cannot log in. If i log in with a local account they can still access file sharing etc.
10.10 clients are fine no issues whatsoever with logging in. ( i have not had a chance to test 10.9 and i don't have any 10.8 clients )
I am guessing its something to do with the way older OSs authenticate with the OD but i am not sure, don't have a huge amount of experience with OD outside of general admin.
My second issue is with SMB.
I am using SMB for file shares, everything was working well and then i started to have issues where users get a message saying the fire cannot be read or written error 36.
The file however would copy over no issue at all.
if i connect via cifs:// rather than smb:// it works ( this uses the older version of SMB ) but in an ideal world i would prefer if i did not have to use this as i would have to run a script on every client to force it to use cifs://
AFP works fine however i cannot use AFP for 2 reasons.
MS office for mac does not agree with it , accessing files over afp with this application causes files to be corrupted and become locked for editing. Apparently you need to have a globally writable folder called .TemporyItems in the root of the share for MS office to work correctly ( good design there microsoft) but this does not appear to work.
AFP does also not appear to make file inherit the permissions when you copy something into the directory so its no good for a shared folder .
Is there any way to force yosemite server to use SMB1 so i don't have to edit every single clients settings?
I would also be happy to use AFP if the 2 issues above can be solved.
This is so strange our old 10.6 server works just fine with MS office over AFP.
my 10.6 clients log in to new accounts with home folders on a new Yosemite server but take about 4 minutes...
Similar Messages
-
Windows VNC clients cannot connect to Snow Leopard Server native VNC server
I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
Does anyone have any solutions?
== QUOTED TEXT BELOW ==
Re: Newbie: Connect Windows -> OSX Server
Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless. -
Office document sharing failure on server 2003 (SMB issue?)
We have a major issue running Office 2003 and 2010 on Windows server 2003 in a corporate AD environment. Since upgrading workstations from XP to Windows 7 we find that many users loose locking of Excel and Word files between 20 minutes and 6 hours
after opening. This allows a second user to open the file, save it, then the original user saves and the first users changes are lost.
We have tried everything we can think of, removing AV software from severe and client, patching completely, wiping serve rand building from scratch, etc. We have run out of ideas from Microsoft tech support, cannot get any joy from our account manager,
and are out of ideas. Office 2013 also seems to have the same problem from our testing.
The issue is active for files from Excel and Word, and does not matter whether it is a file format in the legacy 2003 format or the newer 2010 format.
FYI - This cannot be replaicted using Widnows XP on the same network / server / document - It is specific to WIndows 7 !
Has anyone had this problem and can anyone help?
...Jon.
...Jon.Hi Jon,
When opening an Office file, a temp file will be created in the same folder. A second open session will check if any related temp file is already exists and if it does, Office will prompt that the file is "in use".
Thus please first check if a temp file will be created (it is a hidden file) when opening an Office file - have a try with creating a new shared folder with Everyone - Full Control for the test and if this will work, check permission settings of the original
shared folder.
If you have any feedback on our support, please send to [email protected] -
wireless authentication not working
I found the following in the radius
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 1/15/2014 2:07:57 AM
Event ID: 6273
Task Category: Network Policy Server
Level: Information
Keywords: Audit Failure
User: N/A
Computer: NAP01.test.local
Description:
Network Policy Server denied access to a user.
Contact the Network Policy Server administrator for more information.
User:
Security ID: doamin \user.a
Account Name: user.a
Client Machine:
Security ID: NULL SID
Account Name: -
Fully Qualified Account Name: -
OS-Version: -
Called Station Identifier: 00-0F-7D-C4-45-20:staff
Calling Station Identifier: 0C-74-C2-EF-Dd-0B
NAS:
NAS IPv4 Address: 192.168.9.10
NAS IPv6 Address: -
NAS Identifier: -
NAS Port-Type: Wireless - IEEE 802.11
NAS Port: 497
RADIUS Client:
Client Friendly Name: wcont1
Client IP Address: 192.168.9.10
Authentication Details:
Connection Request Policy Name: Wireless
Network Policy Name: wism
Authentication Provider: Windows
Authentication Server: NAP01.test.local
Authentication Type: EAP
EAP Type: -
Account Session Identifier: -
Logging Results: Accounting information was written to the local log file.
Reason Code: 22
Reason: The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server.
Please helpHi,
Anything updates?
In addition, this issue may also because your client didn't have CA certificate of your domain. Please make sure that your client has CA certificate.
Besides, the error "The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server" may be due to that the default maximum transmission unit that NPS uses for EAP payloads is 1500
bytes. You can lower the maximum size that NPS uses for EAP payloads by adjusting the Framed-MTU attribute in a network policy to a value no greater than 1344:
Configure the EAP Payload Size
Best regards,
Susie -
"System cannot connect to the application server" (Admin Client only)
Hello Experts,
I have a strange issue: I am getting "system cannot connect to the application server" when I am trying to launch BPC Admin.
I successfully connect to the same application server with Excel client on the same PC.
I am able to connect via Admin from another PC.
The installation in question is a new installation. The only difference between my PC and a troubled one is IE7 vs. IE8 - IE8 is the one giving issues.
BPC site is in Local Intranet zone. Windows Authentication is enabled. What am I missing? Local Policy? IE8 settings? Folder permissions (I'm local admin on both PCs)?
It's BPC 7.5 SP05.
Thanks in advance,
Akim
P.S. OS: Windows Server 2003 SP2 32-bit (Citrix box).
Edited by: Akim Zubarchuk on Mar 30, 2011 12:28 AMHi Akim,
Check client diagnostic for admin client can provide good information.
Any way if you are able to connect with excel client not with admin client I will say:
1. Check the rights of user used to connect with admin console
2. Check proxy settings
3. Disable antivorus or firewall into that computer.
4. Make sure the installation of admin client was correct done.
In my opinion it is a big probability to be point 3 or 4.
Regards
Sorin Radulescu -
6.1 Client cannot connect 6.5 Server?
We have two versions of Essbase Server. One is 6.1 and the other is 6.5. We want to connect both server using only one set of client software. I cannot connect to 6.1 server using 6.5 client software, it said version problem or something like this. When I connect 6.5 Server using 6.1 client software, I cannot connect the server at all, it said tcp/ip problem. I can ping or telnet to the server OS. Is it possible for me to connect both 6.1 and 6.5 server using the same client software?
Generally, client software is "forwards compatible" meaning an older client can usually connect to an older server. The reverse is not true, unless you are on Essbase 6.2 or greater (the Essbase 6.5 API can talk down to a 6.2 server, but not any older).When clients are looking to upgrade, I tell them that - but in the same sentence recommend keeping client software on the same version/patch as the Essbase server. Issues like the one you are having illustrate the types of issues you can encounter - and Hyperion will just tell you to use the proper client version.That aside - one thing to check for - Essbase 6.5 allows a DBA to change the listening port of the server. The default is 1423, which the 6.1 client will try to connect to. Make sure the 6.5 server listening port has not been changed (you have to set up the parameters, so it won't just happen for no reason).Regards,Jade------------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]
-
Windows Server 2008 Server Manager - The WinRM Client Cannot Process the Request.
Hello,
I have recently purchased a Dedicated Server, and I have installed Windows Server 2008 R2. I want to use Server Manager because I don't really have that much experience with command line commands, so I wanted to use server manager, I can remotely connect
to my server but when I use Server Manager I get the error "The WinRM Client Cannot Process the Request, if the authentication scheme is different from Kerberos..." I haven't set up a domain between my PC and the Dedi, as I do not know how/or know
if this is applicable in this situation.
Thanks for your time!
Bill Gates MateHi,
If you are using the non-domain management method, please refer the following article to add the trust host.
The related article:
Remoting Week: Non-Domain Remoting
http://blogs.technet.com/b/heyscriptingguy/archive/2013/11/29/remoting-week-non-domain-remoting.aspx
More third party article:
The WinRM client cannot process the request. If the authentication scheme is different
http://technico.qnownow.com/the-winrm-client-cannot-process-the-request-if-the-authentication-scheme-is-different/
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites;
therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from the Internet. ***
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. -
Exchange 2010 SP2 Active DAG Node. Cannot cannot to Exchange Admin Console with the following errors and these errors change from time to time ... and some times it works ...
attempt to connect to http://DAGNODE.domain.com/powershell using "kerberos" authentication failed: connecting to remote server failed with the following message: The WinRM Client cannot complete the operation
within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for windows remote management service is enabled.
thanks,Hi,Philip,
Are you running the DAG on Windows server 2008 R2?If so check the following KB to see if they apply to your issue
http://support.microsoft.com/kb/976839
http://support.microsoft.com/kb/2294243
And you can check if the solutions in these old threads with similar error message do the trick for you.
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/54af902c-d718-4656-8a25-7c150e4b0e81/
http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/baa1af25-001a-432d-86a0-25c05655e63c/
Regards,
Sharon
Sharon Shen
TechNet Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. -
Windows 7 pro client cannot access folders on server 2003 domain server
I added a windows 7 64 bit client to a server 2003 32 bit domain 3 weeks ago and file sharing was working fine until today, 5/4/12. Now, when trying to access shared folders that reside on the server,
I get the following "access denied" message:
[…folder…] 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 access permissions.
The user name could not be found.
Strangely enough...
The windows 7 client
can open shared folders that reside on the XP clients in the domain
All the XP clients in the domain can access the server 2003 folders
All the XP clients and the server 2003 machine can access shared folders and printers on the windows 7 client.
The windows 7 client can ping the server 2003 machine and vice versa
I can “see” the server in my network list, but when I click on it, I get the same “access denied” message listed above.
So... the only problem is that the windows 7 client cannot access folders that reside on the windows server 2003 machine. There must be some sharing setting that got changed
by a recent windows update.
Here is what I have done/verified so far on the windows 7 client:
In advanced sharing settings for Home/Work, Public and Domain profiles:
network discovery is enabled
file and print sharing is enabled
use user accounts and passwords to connect to other computers is selected (I also tried allowing windows to manage homegroup connections instead, but the problem remained.)
40 -56 bit encryption is enabled
In “gpedit.msc” Local Policies/Security Settings:
enabled the following policies:
Network access: Allow anonymous SID/name translation
Network access: Let Everyone permissions apply to anonymous users
disabled the following policies:
Network access: Restrict anonymous access to Named Pipes and Shares
Network access: Do not allow anonymous enumeration of SAM accounts
Network access: Do not allow anonymous enumeration of SAM accounts and shares
What am I missing? Are there policies on the server that need to be adjusted?
Please help! My business is crippled if I cannot access server files from this workstation. Thank you in advance.As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous
steps should be helpful for many similar scenarios. <o:p></o:p>
If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You
can also choose to unmark the answer as you wish. <o:p></o:p>
In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar
problems. <o:p></o:p>
Thanks!<o:p></o:p>
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread. -
Project Server 2010 Web services access with Client Certificate Authentication
We switched our SharePoint/Project Server 2010 farm to use client certificate authentication with Active Directory Federation Services (AD FS) 2.0, which is working without issue. We have some administrative Project Server Interface (PSI)
web service applications that no longer connect to server with the new authentication configuration. Our custom applications are using the WCF interface to access the public web services.
Please let us know if it is possible to authenticate with AD FS 2.0 and then call
Project Server web services. Any help or coding examples would be greatly appreciated.what is the error occurred when the custom PSI app connects?
can you upload the ULS logs here for research?
What is the user account format you specified in the code for authentication?
For proper authorization, the “user logon account” in PWA for the user needs to be changed from domain\username to the claims token (e.g.
'I:0#.w|mybusinessdomain\ewmccarty').
It requires you to manually call the UpnLogon method of
“Claims to Windows Token Service”. if (Thread.CurrentPrincipal.Identity is ClaimsIdentity)
{ var identity = (ClaimsIdentity)Thread.CurrentPrincipal.Identity; }
if (Thread.CurrentPrincipal.Identity is ClaimsIdentity)
var identity = (ClaimsIdentity)Thread.CurrentPrincipal.Identity;
Than you need to extract UPN-Claim from the identity.
Upload the verbose log if possible.
Did you see this?
http://msdn.microsoft.com/en-us/library/ff181538(v=office.14).aspx
Cheers. Happy troubleshooting !!! Sriram E - MSFT Enterprise Project Management -
Which clients are using my Sun One server for authentication?
We use Sun One ver. 5.2 .
Our LDAP clients use it for authentication.
How can I list which clients recently used the Sun One server to authenticate?
The reason I need that is because I want to upgrade the Sun One server and I want to notify the clients that I'm about to do it.
Thanks.https://www.redhat.com/archives/fedora-directory-users/2005-September/msg00010.html
Useful script to extract LDAP based user posixGroup memberships information
===
Assuming you are using posixGroup objectclass and memberUid attribute to
store your membership information, you may find my shell script useful
and handy.
It works on Solaris LDAP Client with "ldapaddent" and "ldaplist"
commands, and works against FDS, SUN DS or OpenLDAP.
===
Gary -
I have older version of itunes on Windows Vista, when i check for updates it states it cannot connect to itunes update server even though i am connected to the internet, i have an iphone that has songs in the cloud and i want to add them to my library?
Try updating your iTunes using an iTunesSetup.exe (or iTunes64Setup.exe) installer file downloaded from the Apple website:
http://www.apple.com/itunes/download/ -
8.8 Client cannot connect to Windows Server 2008 error -1102
SAP Business On 8.8 on PL 18
This is not the first time I have had this issue with Windows Server 2008.
however everytime the resolution was diffrent. Now this site is causing trouble.
The issue is the client cannot connect. We have the log on window, can see the company list. type on the password and we get a -1102 error.
The client on the Server itself can log on. It is the cleints that cannot.
I checked these below.
1 SQL Native client is installed and ok.
2. Licence server is configured and ok
3. The user has admin access to locl PC
4. The SAP user name and password are correct ( client on server can connect fine )
5. The ports 1433, 30000 and 30001 are open on the server.
6. Through SQL server configuration the named pipes and TCP are enabled.
7. SQL server browser is running
The only things I have not tried are
The Firewall is running on the server and I have not yet stopped it. Will try that tomorrow.
Do you have any other ideas please ?I have got this working but I am not confidant of the outcome - yet - I really need your expert advise here.
This is what I did. In that order.
1. As Owen suggested I checked if there was a specified Port for the instance. What I found was TCP Dynamic ports were enabled ( SQL server config manager | network configuration | tcp properties ) and there was no TCP port specified. Assuming ( ai may be wrong) that the system assigns a dynamic port to this instance I set it up so the Dynamic port does not happen and manually specified the Port 1433. Restarted the SQL Service. ( still having the Port 1433 open in the firewall). This did not solve the issue.
2. With the above setting still on, switched off the firewall. Went to the PC client and SAP can log on now. Now keeping the SAP client running, switched on the Firewall on the server. Log off SAP on PC client and log back in ( with firewall off ). SAP now can log on.
3. I had to do the above step for all PCs to get them working.
4. Currently the firewall is on and clients can connect
So what could be happening? I have no clue. It is apparent there is some setting that gets saved within the PCs ( may be user profile) after the first log on with the Firewall off - to say its safe ?
However I have no idea what will happen if the server is restarted u2013 this server we cannot restart any time we want as itu2019s a critical server and runs other things.
I would still like to get to the bottom of this to understand what is happening.
I have a SAP message running too and will ask them this same question. -
Fatal error: Client does not support authentication protocol
requested by server; consider upgrading MySQL client in
/homepages/28/d74942468/htdocs/cosmic/sites/onlinemove/Connections/db.php
on line 9
This is the error that comes up on the server where the site
sits. The database is working on my local machine with the local
settings, but wont connect due to the above.
I think im using MySQL client 3.23 How do i upgrade?
I found this on MySQL site:
http://dev.mysql.com/doc/refman/5.0/en/old-client.html
I'm not sure how to edit the connection string to make it
accept the vaules.The_FedEx_Guy wrote:
> Fatal error: Client does not support authentication
protocol requested by
> server; consider upgrading MySQL client in
>
/homepages/28/d74942468/htdocs/cosmic/sites/onlinemove/Connections/db.php
on
> line 9
> I think im using MySQL client 3.23 How do i upgrade?
The MySQL client that the error refers to isn't the version
of MySQL,
but the MySQL library bundled with PHP. It sounds as though
your hosting
company has upgraded to MySQL 4.1 or higher, but is still
using PHP 4.
> I'm not sure how to edit the connection string to make
it accept the vaules.
You can't. It's the way that the user account passwords are
stored in
MySQL. You need to get the hosting company to upgrade to PHP
5 or to
reset the passwords in MySQL using the OLD_PASSWORD()
function. This
needs to be done by someone with top-level administrative
privileges on
the database.
David Powers, Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/ -
Interesting db mail issue. If i click send test mail from sql mgmt studio, it works fine, but when i execute a SP to send a mail, it fails. One thing I noticed is that the "LastModified" column in the mail log shows the domain account when a test
mail was sent from mgmt studio, but show "sa" when the SP was used to send mail.
This is from SQL 2012, did not see this in sql 2008, looks like 2008 always used the service account. any ideas ?
Get this error:
The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 1 (2013-04-30T16:36:52). Exception Message: Cannot send mails to mail server. (Mailbox unavailable. The server response was: 5.7.1 Client does not
Thanks.
RangaHi Ranga,
I also use SQL Server 2012. I send a test email through SQL Server Management and the last modified By “sa”.
If you used stored procedure to send a test email. Please use the command below:
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'Adventure Works Administrator',
@recipients = '[email protected]',
@body = 'The stored procedure finished successfully.',
@subject = 'Automated Success Message' ;
I can both send test email through SQL Server Management Studio and SP. Make sure you have the right profile. Since you could send test mail via SQL Server Management Studio, please try again to send it via SP.
Thanks.
If you have any feedback on our support, please click
here.
Maggie Luo
TechNet Community Support
Maybe you are looking for
-
[SOLVED] Font Unreadable after XOrg 1.5 HELP!!!
Previoulsy on mi PC: All work right, including COMPIZ with all Effects Enabled. One Day: pacman -Syu cause update to xorg1.5 and BOOM all Fonts on Title bar of all windows became unreadable and the problem will be extended on all rendering windows of
-
How to populate the Sender and Receiver GLN/ID in the Seeburger Message Tracking
HI Team, Scenario : ECC--> PI--> Party Sending GS1 XML Message to party (Not EDI). Sender Party and Receiver Party appearing as expected. BUT User expecting to see the Sender GLN and Receiver GLN in Seeburger Message Tracking. It should be dynamical
-
Font problem in Photoshop CS5 ?
If i open my psd in CS4 and try to edit it it's ok, the Arial font doesn't change, but when i try in CS5, it's another story. The same font looks much compress. Can somebody explain what's the problem here ?
-
How do I reset my iCloud old inaccessible email and password with my new iTunes email and password currently working on a different device? Thanks for any suggestions ,
-
Just a week ago I lost all my starred songs! I need som help...