In article <eKRMoOK4GHA.2228.DeleteThis@TK2MSFTNGP03.phx.gbl>,
"Eco" <eco.DeleteThis@hotmail.com> wrote:
> Just replace win2k memeber server by new win2003 member server box and has
> tried to set all macintosh related things same as old server.
>
> Mac OS X client, they will connect server at Network > Local > locate
> server. Then click connect here. But it will try to connect server and count
> down 117 second for timeout to pop up the logon screen.
>
> But connecting at old win2k server, it will immediatly popup the logon
> screen.
>
> What does it happen connecting at server 2003? Why neeed one more minute to
> connect server? Though can connect it lastly, it seems not good for users.
> Please help me to fix it.
Instead of using "Network > Local" to find the server, what happens if
you enter its name directly in the Connect To Server dialog?
Try something like:
afp://servername
afp://servername.domain.com
smb://servername
smb://servername.domain.com
If your server has File Services for Macintosh installed you should be
able to use one or both of the AFP connections above. Otherwise, you'll
need to use the SMB connection.
Hope this helps! bill
--
William M. Smith
(Microsoft Interop MVP - Mac/Windows)