Re: OS X Clients had connectivity...Now they lost it
- From: "Jim Seifert [MSFT]" <jimsei@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 8 Jun 2005 09:14:34 -0700
A couple of things you can take a look at and a request for more information
follow:
1.) Verify SFM is running - "sc query Macfile" from cmd.
2.) See if Appletalk is still set to accept inbound connections on the
correct adapter.
3.) Try connecting from a Mac using afp://serverIP
4.) Try connecting via Appletalk if you support it - afp:/at/servername.
5.) Try connection from a Mac using smb://serverIP
Can you connect from a PC using the same accounts that are denied
connections on a Mac client?
--
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"mjknapp" <mjknapp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C7D0FCD8-6B67-4EB3-950A-36BCCC85947D@xxxxxxxxxxxxxxxx
>I have a W2k3sp1 server (member server)with Mac Shares on it. The Clients
> X.3.9 use the Microsoft UAM to connect to the server. We had a server
> lockup
> and now after a reboot the clients can't connect to any of the shares. I
> restarted the File Services for Macintosh and no luck. Anyone have any
> ideas
> why it took a dive or where I can go and look for answers? The Event log
> doesn't get very descriptive about what happened. It just says that user
> so
> and so failed to connect. I even rebooted the domain controllers thinking
> something got messed up there. I can login into a pc and map the shares
> no
> problem so it doesn't seem to be a permission problem.
.
- References:
- OS X Clients had connectivity...Now they lost it
- From: mjknapp
- OS X Clients had connectivity...Now they lost it
- Prev by Date: Indivdual Quota view
- Next by Date: cannot copy files, object name no longer available
- Previous by thread: OS X Clients had connectivity...Now they lost it
- Next by thread: Windows 2003 SP1
- Index(es):
Relevant Pages
|
