LOGON TO WINDOW SERVER 1

[UNIX72]

Hello have 20 emacs running OX 10.3.3, need to access windows 2003 server. I go to finder and type Ip address smb:// 192.168.1.1 and i can connect, then ask me for WORKGROUP/DOMAIN, USERNAME, PASSWORD, I put all the require fields, but i can can't logon. Error states "cannot log into server because username and password are incorrect" So I tried out network browser again I can see the server name but when i tried to access it states "The alias "Server" could not be opened, because the orginal item cannot be found". Can OS X 10.3 access windows 2003 server without 3rd party software? Any clues or directions? Thanks so much

 

[greenhorse]

I'm having the exact same issue and I'm hoping you have made some progress with it.

 

[Zelandakh]

I don't think you need smb prefix any more. I have no problem attaching that way.

Have you tried leaving out the domain name?

 

[greenhorse]

I'm pretty sure I tried without the domain. Is the smb:// prefix optional or out of spec? You're getting this to work in a Panther ==> Windows 2003 domain environment?

 

[UNIX72]

Forget that I use thursby AdmitMac, works great with windows 2000 or 2003 activy directory structure.

 

[Zelandakh]

Not using AdmitMac. Just native out of the box. 10.3 to 2000 Server although any PC with a share is fine - got it to 98 this morning!

 

[zeeGerman]

Try afp://<IP>

There are no problems to logon to WinServer.

 

[UNIX72]

Exactly panther 10.3 works fine with windows 2000 or 2003 with Active Directory. You can logon and map drives just fine. Now i need to lock down Mac workstations with a policy, does anybody know how? I know you can lockdown or restrict access to local user accounts, but with network accounts you don't have that option. Any clues? Thanks.

 

[greenhorse]

Unix72,
Thanks for the update but I am still not sure how you resolved the issue. Can you elaborate?

 

[UNIX72]

Hey greehorse , what MAC OS are you running? I think the Active directory feature only works on 10.3 and above. Let me know.

 

[EllenM1]

Hi - I am having the exact same problem at work, and it started suddenly. Everything had been working fine, now suddenly I can't connect to my windows shares (from a win2K box). I can see the server but can no longer connect. It says I have the wrong name or password.

I'm running 10.3.4 on a mac in an otherwise totally windows environment. I need to reach a share on my Windows 2K computer. I have tried remaking the share, specifying other workgroups in Directory access on the mac, etc. nothing works.

I don't understand what the solution that was referred to above is - please elaborate if possible.


Ellen

 

[EllenM1]

Well I solved this one on my own. I did several things, and am not sure which of them fixed it ultimately:

1. I turned on Active Directory in Directory Access on the Mac.
2. I un-installed the checkpoint VPN client from the PC, which I remembered I had installed around the time the network problems started. I had installed it to get some settings off it to use on my home mac, but perhaps it was interfering with drive sharing.
3. I remade the shares on the pc being careful to share the entire drive and the folder.
4. I made sure the share of the drive was not just an administrative share, but the other kind (whatever the heck they call it). So instead of D$ it's D.
5. I double checked the permissions on the shares to make sure what workgroup and what names were allowed.
6. On the mac, I connected using "command-K" and then
smb://my.full.machine.nameandpath/D instead of
smb://my.full.machine.nameandpath/shared_foldername

where D is the shared drive which contains the shared folder. When I changed the smb:// path and hit "connect" it asked for my workgroup, name and password! No more "not found" messages. yay!

I hope this helps someone else!

_______________________________

http://thedesignspace.net

 

[imeldesign]

We set up a separate users folder just for Mac Users. They are not a member of Users in Active Directory. We then set up a global group policy for all Mac Users to allow terminal services (we have one propriatary app that is pc only and mac users access it with RDC.)Then we used the regular groups policies to set their share access. This keeps them out of where they don't belong and limits what they can do when connected directly to the term server.
They access shares via smb://server.domainname.org then all shares are listed in drop down menu. They can see all shares but only access the ones they have permissions to.
This will work with ip address of server (10.3.3.1 with no smb:// in front)as well.

 

[UNIX72]

Download the UAM from Microsoft.