Re: MAC computer access windows server

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 10/05/05 

Date: Wed, 5 Oct 2005 12:10:05 -0500

Hmm. Incompatible lan manager authentication level settings could also cause
a problem. Use secpol.msc and make sure that ntlm is allowed. This and other
security settings and resultant incompatibilities are explained in the KB
article below. I would think a Mac computer would be considered equivalent
to a Windows 98 computer in regard to problems with security settings.
Netbios over tcp/ip needs to be enabled on the Windows 2003 server and port
139 TCP needs to be available to the Mac computer. The command netstat -an
will show if port 139 TCP is listening on the Windows 2003 computer. If you
have ipsec filtering policy enabled or the Windows Firewall enabled try
disabling them at least temporarily if it will not put your Windows 2003
Server at risk. The Windows Firewall can also log dropped packets. ---
Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;823659

"Ray" <ray@utah.edu> wrote in message
news:e4FLP3cyFHA.3312@TK2MSFTNGP09.phx.gbl...
> Yeah, the server is a memeber server of my domain and "Digitally Sing
> Communications (always)" has been set to Disabled.
>
> I still got problem, what's wrong? Thanks.
>
>
> Logon Failure:
>
> Reason: Unknown user name or bad password
>
> User Name: chris
>
> Domain: CS
>
> Logon Type: 3
>
> Logon Process: NtLmSsp
>
> Authentication Package: NTLM
>
> Workstation Name: \\CSLYONLAP1-
>
> Caller User Name: -
>
> Caller Domain: -
>
> Caller Logon ID: -
>
> Caller Process ID: -
>
> Transited Services: -
>
> Source Network Address: xxx.xxx.xxx.xxx
>
> Source Port: 0
>
>
>
> Ray
>
> "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
> news:ejOYA6TyFHA.156@tk2msftngp13.phx.gbl...
>> Make sure that you have compatible security settings [secpol.msc for
>> Local Security Policy] and for SMB signing and lan manager authentication
>> level. I just tried it and was able to access a share on an XP Pro
>> workgroup computer and a Windows 2003 domain controller from my iMac but
>> not my Windows 2003 domain controller and interestingly enough failed
>> "logon" events using ntlm were recorded in the security log of my Windows
>> 2003 Domain Controller of my logon attempts. I then configured the
>> security setting for Microsoft network server:digitally sign
>> communications(always) to be DISABLED, ran gpupdate, and then was able to
>> access the share on my Windows 2003 domain controller from my iMac. ---
>> Steve
>>
>>
>> "Ray" <ray@utah.edu> wrote in message
>> news:eRRBwcRyFHA.2132@TK2MSFTNGP15.phx.gbl...
>>> Yes, it can browse computers in our domain, but the username and
>>> password cannot log on our server, if try on windows xp, everything is
>>> fine, if try on MAC machine, it doesn't recognize, and lock out if tried
>>> three times.
>>>
>>> What's wrong? Thanks.
>>>
>>> Ray
>>>
>>>
>>> "Robert Moir" <robspamtrap+msnews@gmail.com> wrote in message
>>> news:eN2dHZRyFHA.3000@TK2MSFTNGP12.phx.gbl...
>>>> Ray wrote:
>>>>> Hi there,
>>>>>
>>>>> Does anybody happen to know how MAC computers can access shared fold
>>>>> on windows server?
>>>>
>>>> Assuming you're on the network with a good IP address...
>>>> Open finder, click Go, click Connect to Server, then type in
>>>> smb://servername/sharename
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Relevant Pages

  • Re: Huh? "Login failure: the user has not been granted the requested logon type at this compute
    ... I'm a pretty experienced Windows user and programmer, ... the user has not been granted the requested logon type ... on the appropriate OU to see the Group Policy for that OU]. ... > administrators' group to the domain controller. ...
    (microsoft.public.security)
  • Re: Remote User Needs to Change PWD without connecting to domain
    ... On our windows NT machines users receive the no domain controller ... With Windows 2000 User DO NOT receive any notification. ... >> When they would take the laptop in the field they were unable to logon ...
    (microsoft.public.win2000.security)
  • Re: Domain authenticating non-domain accounts
    ... I limited the tests to Windows ... a machine running Windows 98 can still access file shares ... for a logon but were able to authenticate me as long as I entered the same ... it does not explain why this domain controller was LESS strict about ...
    (microsoft.public.platformsdk.security)
  • Re: cached logons
    ... Microsoft Windows 2000 Security Hardening Guide ... Disable Caching of Logon Information ... If the Domain Controller cannot be found during logon ... how many user account entries Windows 2000 saves in the logon cache ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Windows 2003 member server with Windows 2000 Domain Controller
    ... If anyone is having a Windows 2003 member server with a Windows 2000 ... Windows cannot obtain the domain controller name for your computer ... There are currently no logon servers available to service the logon ...
    (microsoft.public.win2000.security)
Quantcast