New Imac won't connect to Server

[Greg]

We have 3 Macs on our Windows 2000/2003 network. Our DC runs W2k server, and
our NAS and Exchange servers are running W2k3 server.
We just replaced an old Mac with a new iMac, hooked it up to the network,
installed MS Office 2004 for Mac Std, Edition, and all of of that works fine
(including Entourage).
However, when the user tries to connect to the NAS server...she can't. I've
used the "HELP" feature to try and get a clue, but nothing works. One of the
other Macs uses afp://(ip address) to connect to the NAS, and the other Mac
uses smb://(ip address) to connect. Neither of those, or anything else for
that matter, work on this one.

 

[William Smith]

We have 3 Macs on our Windows 2000/2003 network. Our DC runs W2k server, and
our NAS and Exchange servers are running W2k3 server.
We just replaced an old Mac with a new iMac, hooked it up to the network,
installed MS Office 2004 for Mac Std, Edition, and all of of that works fine
(including Entourage).
However, when the user tries to connect to the NAS server...she can't. I've
used the "HELP" feature to try and get a clue, but nothing works. One of the
other Macs uses afp://(ip address) to connect to the NAS, and the other Mac
uses smb://(ip address) to connect. Neither of those, or anything else for
that matter, work on this one.

Hi Greg!

You've described all of the problem except for what happens. What
happens when the user attempts the connection and fails? Do you get any
sort of error dialog?

As for the NAS server, do you mean that Mac volumes or Windows shares
shared from the NAS server through Windows Server don't work but that
Mac volumes or Windows shares that reside on the server itself do?

Finally, what versions of Mac OS X work and don't work?

A few pieces of information is you weren't aware...

First, before AFP will work (afp://ip address) you must either be
running File Services for Macintosh and have a Mac volume shared or you
must be running a third party application such as Group Logic's
ExtremeZ-IP. The second choice is preferred because Microsoft has not
upgraded AFP support in Windows Server for several years. It has many
compatibility issues with Mac OS X and will not even be supported after
Windows Server 2003.

If you are attempting to use SMB (smb://ip address) then your Windows
Server must have a group policy called "Digitally sign communications
(always)" disabled. That applies to Mac OS X 10.4 and earlier. Mac OS X
10.5 is suppose to allow digitally signed communications. However, Mac
OS X's implementation of its Windows file sharing client is poor and a
better option would probably be something like Dave or ADMitMac from
<http://www.thursby.com>.

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>

 

[William Smith]

We have 3 Macs on our Windows 2000/2003 network. Our DC runs W2k server, and
our NAS and Exchange servers are running W2k3 server.
We just replaced an old Mac with a new iMac, hooked it up to the network,
installed MS Office 2004 for Mac Std, Edition, and all of of that works fine
(including Entourage).
However, when the user tries to connect to the NAS server...she can't. I've
used the "HELP" feature to try and get a clue, but nothing works. One of the
other Macs uses afp://(ip address) to connect to the NAS, and the other Mac
uses smb://(ip address) to connect. Neither of those, or anything else for
that matter, work on this one.

Hi Greg!

You've described all of the problem except for what happens. What
happens when the user attempts the connection and fails? Do you get any
sort of error dialog?

As for the NAS server, do you mean that Mac volumes or Windows shares
shared from the NAS server through Windows Server don't work but that
Mac volumes or Windows shares that reside on the server itself do?

A few pieces of information is you weren't aware...

First, before AFP will work (afp://ip address) you must either be
running File Services for Macintosh and have a Mac volume shared or you
must be running a third party application such as Group Logic's
ExtremeZ-IP. The second choice is preferred because Microsoft has not
upgraded AFP support in Windows Server for several years. It has many
compatibility issues with Mac OS X and will not even be supported after
Windows Server


--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>

 

[Dan P]

Hi
I am using file share between a win 2000 machine and a Mac using Tiger. The
Mac finds the windows machine using smb// machine ID, User group easily. When
it was first set up file sharing worked well now opening the folders from the
Mac shows they are empty. The folders are not. I can place a folder in the
shared folder from the Mac and the windows machine sees it.

 

[William Smith]

Hi
I am using file share between a win 2000 machine and a Mac using Tiger. The
Mac finds the windows machine using smb// machine ID, User group easily. When
it was first set up file sharing worked well now opening the folders from the
Mac shows they are empty. The folders are not. I can place a folder in the
shared folder from the Mac and the windows machine sees it.

See what happens if you connect to the folder from the Mac and then view
its contents using the Terminal.

Open the Terminal application found in /Applications/Utilities and then
enter:

ls -hal /path/to/folder

You can easily add the path to the folder by simply dragging and
dropping it into the Terminal window. It may look funny but don't worry.
Then hit return to list the contents.

Does anything appear there?

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>

 

[Dan P]

Bill
Thanks for the reply. Here is a screen grab of the terminal window.

Last login: Mon Mar 17 10:42:40 on console Welcome to Darwin!
You have new mail.
[WOH:~] sccmas% 1s -hal/path/to/dell shared folder tcsh: 1s: Command not
found.
[WOH:~] sccmas% is -hal/path/to/dellsharedfolder tcsh: is: Command not found.
[WOH:~] sccmas% IVolumes/DELL\ SHARED\ FOLDER/
tcsh: IVolumes/DELL SHARED FOLDER/: Permission denied. [WOH:~] sccmas% I

I have also tried using capital I. It appears that something has changed in
the permissions as this link used to work
Dan

 

[William Smith]

Bill
Thanks for the reply. Here is a screen grab of the terminal window.

Last login: Mon Mar 17 10:42:40 on console Welcome to Darwin!
You have new mail.
[WOH:~] sccmas% 1s -hal/path/to/dell shared folder tcsh: 1s: Command not
found.
[WOH:~] sccmas% is -hal/path/to/dellsharedfolder tcsh: is: Command not found.
[WOH:~] sccmas% IVolumes/DELL\ SHARED\ FOLDER/
tcsh: IVolumes/DELL SHARED FOLDER/: Permission denied. [WOH:~] sccmas% I

I have also tried using capital I. It appears that something has changed in
the permissions as this link used to work

Hi Dan!

I'm not quite sure what you're doing. You've omitted the space after
"-hal" for starters. I'm not quite sure what "IVolumes" is.

Have a look at my instructions again. You won't actually type
"/path/to/folder". Type the first part and then drag the folder into the
Terminal window to automatically fill in the path for you.

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>

 

[Dan P]

Thanks Bill
What I actually wound up doing was building a new share folder and then
having to add everyone in the security tab of the share window. I am not a
windows person as you can see.
Dan

Bill
Thanks for the reply. Here is a screen grab of the terminal window.

Last login: Mon Mar 17 10:42:40 on console Welcome to Darwin!
You have new mail.
[WOH:~] sccmas% 1s -hal/path/to/dell shared folder tcsh: 1s: Command not
found.
[WOH:~] sccmas% is -hal/path/to/dellsharedfolder tcsh: is: Command not found.
[WOH:~] sccmas% IVolumes/DELL\ SHARED\ FOLDER/
tcsh: IVolumes/DELL SHARED FOLDER/: Permission denied. [WOH:~] sccmas% I

I have also tried using capital I. It appears that something has changed in
the permissions as this link used to work

Hi Dan!

I'm not quite sure what you're doing. You've omitted the space after
"-hal" for starters. I'm not quite sure what "IVolumes" is.

Have a look at my instructions again. You won't actually type
"/path/to/folder". Type the first part and then drag the folder into the
Terminal window to automatically fill in the path for you.

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>