The alias could not be opened, because the original item cannot be found.

I also am having the same problem. I use a New Powerbook G4. Have been using it on our system for weeks. They were running windows 200 server. When they upgraded th 2003 server it gives me the allias problem. I followed the instructions by "andyoww". It did attempt to let me sign on to the server but it said I had an invalid username or password. I verified my identity and had someone elso try tolog on. No luck. What is the problem?

I wish I could tell you.
I tried it on my mac (10.3.9)
Go/connect to server
smb://servername/c$ (hidden admin share)
used my windows administrator and password
It mounted the volume with no problem.

I would guess that you are either not entering the correct user/pass or that particular user doesn't have access to that share.
Check the permissions on the share to see if the users in question have access.

I'm having the same problem from an IBook w/ OS X connecting to a Windows 2003 server. I've created new accounts and passwords on the 2003 server to no avail. I can connect to a share on an XP computer on the network.

Any advice would be greatly appreciated. I'm probably considered an expert Windows user/network administrator but without a doubt am lower than a novice Mac user :)

The following solution worked for me.  The key is the SMB usage.  This is disabled by default.  You need to ENABLE it at the server and workstation.

Microsoft network client: Digitally sign communications (always)

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options

Description
Determines whether the computer always digitally signs client communications.

The Windows 2000 Server, Windows 2000 Professional, and Windows XP Professional authentication protocol Server Message Block (SMB) supports mutual authentication, which closes a "man-in-the-middle" attack and supports message authentication, which prevents active message attacks. SMB signing provides this authentication by placing a digital signature into each SMB, which is then verified by both the client and the server.

To use SMB signing, you must either enable it or require it on both the SMB client and the SMB server. If SMB signing is enabled on a server, clients that are also enabled for SMB signing use the packet signing protocol during all subsequent sessions. If SMB signing is required on a server, a client is not able to establish a session, unless it is at least enabled for SMB signing.

If this policy is enabled, it requires the SMB client to sign packets. If this policy is disabled, it does not require the SMB client to sign packets.

Default: Disabled

Note

• SMB signing imposes a performance penalty on your system. Although it does not consume any more network bandwidth, it does use more CPU cycles on the client and server side.

For more information, see:

• Security Configuration Manager Tools
 

The site http://www.macwindows.com/Win2003.html#100603  also offers a variety of other solutions.

The solution that worked for me had to do with the default security policy in Windows 2003 server which always encripts network connections. By making the following change, my problem went away.

From Administrative Tools, open Domain Controller Security Settings.
Go to Local Policies then Security Options.

Scroll down to find the entry Microsoft network server: Digitally sign communications (always). Set this to Disabled.

I found this at the folowing site:
http://allinthehead.com/retro/218/accessing-a-windows-2003-share-from-os-x

I still do not have an a solution yet. I have not been able to get our systems administrator to look at the last two suggestions yet. We are going to try those this week.

hef001,

My advice will be to ask your own question. Using the questions of the others is not really a good idea :)

Venabili
Trying to Cleanup around

The last solution posted fixed my problem. Thanks.

As for the comments posted recently maybe I do not understand the system here but what is wrong with me asking the question the way I did? I got a solution from someone and it may have helped someone else.

Thanks