Authenticating Mac 10.2 on an NT Legacy Domain

[ybn1197]

Hopefully this is the right place as I have looked around and not found a similiar post.

Here's the situation. I'm a total Macintosh newbie. I administer a NT 4.0 Legacy domain (Some of the hardware does not support Active Directory. Once that hardware has been replaced, we will migrate to AD). Our research department has just purchased three Mac workstations, all running OS 10.2. What do I need to do for those users to authenticate and access files located on a Windows NT domain server with as few changes (read preferably none) to the windows machines. We'd like to keep all software changes on the Mac side as Windows has enough security holes without us mucking about to enable the Macs access. I'm a noob at Mac so as much detail as possible please.

 

[Welshbird]

When I first started at my current company they didn't have a laptop for me to use, so I used my personal mac.

All I seemed to need to do was to connect the ethernet cable and use [apple] + [k] to connect to a shared network resource.

Fee

"The cure for anything is salt water – sweat, tears, or the sea." Isak Dinesen

 

[ybn1197]

Thanks Willif. It didn't solve the issue outright, but it put me on the path I needed to be on in order to solve it. The default protocol on the machines was A something something (don't remember off the top of my head, definately three letters starting with A.) Once I wrote smb:// into the line, I was able to attach and authenticate to the server and domain.

 

[Zelandakh]

afp you mean. That's the language the Mac uses to talk to other Macs. Just using smb will get the Mac to talk to Windows as a Windows box.

Why did someone buy 10.2 machines? a) They are very old and b) 10.2 was awful.