Doug:
I got the Mac services working. Apparently it wasn't a problem on
the Mac side. The one item that the NT manual left out is that the directory
in which the UAM volume resides has to be shared and have the permissions
set. I found a Web page dealing with this setup. So, when I shared the
directory on the NT Server, the directory was visible by the Mac client. All
machines are on the same subnet. The NT Services for Mac is set with routing
enabled because there are no other Mac servers on the net. This is per the
SFM docs. Thoughts?
Now, I need to get printing working. I have a PS laser printer
connected to the server. Is shared printing a possiblity?
> Re-reading the NT docs, I'm supposed to see
the
>AppleShare icon in the
> Chooser, which I don't. I only see AppleTalk. Hmmm...
>???
I was having all sorts of problems at this point. In the MacTCP
control panel, I would only have LocalTalk and no Ethernet. I rebooted and
reinstalled from the Network Installer disk and then the Asante disk. Then,
EtherTalk appeared. Originally, in the Chooser, when I selected AppleShare,
no zones showed-up (which was fixed by the above).
I've been using TransMac to move disk images to the ci. Moving them
across the network doesn't work because the type/creator information is not
moved. As far as I can tell, neither TransMac or HFV work with remote
(network) drives, so I can't get their translation benefits. Also, using a
null-modem setup doesn't transfer the credtor information. So, the
transferred programs are not usable. So, I've been relying on TransMac 4.1c
which works well.
I'm making images of System 7.5.3 plus the update.
I also want to get Web access on that machine. I've got a simple
browser, an email and telnet program moved over, but I have to work on the
broadband access. I have a cable modem connected to a NAT firewall. All
internal machines are on the same subnet with the firewall (192.168.1.x).
Could you make me a BinHex or SEA image of the 3.6.4 client disk?
Thanks.
Rich
==========================
Richard A. Cini, Jr.
Congress Financial Corporation
1133 Avenue of the Americas
30th Floor
New York, NY 10036
(212) 545-4402
(212) 840-6259 (facsimile)
-----Original Message-----
From: Douglas Quebbeman [mailto:dhquebbeman@theestopinalgroup.com]
Sent: Friday, November 17, 2000 1:26 PM
To: 'classiccmp(a)classiccmp.org'
Subject: RE: AppleTalk over NT
Does anyone have any experience with Mac-NT
compatibility? I want
the Mac
to have access to my NT server so that I can move
large files across my
home
network which is decidedly Windows-based.
I run Services for Macintosh for a very few legacy Macs here...
Here's the setup. NT4 Server has the Services for
Macintosh
installed. The
NT configuration is set for routing, seeding the
network, and a node range
of 11-254.
Ok, I don't have SFM set for routing. It's simply bound to the
Ethernet adapter. In that mode, the NIC is in the "default zone".
The IIci has an Asante NuBus Ethernet card which
passes internal
diagnostics and indicates "link". So, I know the connection to my hub is
good.
Ok.
I have the AppleShare 3.0.1 client installed. The ci
runs System
7.0.1.
Re-reading the NT docs, I'm supposed to see the
AppleShare icon in the
Chooser, which I don't. I only see AppleTalk. Hmmm...
???
I don't see AppleTalk in the Chooser; I see AppleTalk in Control Panel.
In Chooser, I see icons for each type of printer driver I'm using,
and I also see the AppleShare icon.
However, none of our legacy Macs are that old; System 7.5.5 is the
oldest in use, OS 8.1 the newest. ISTR that AppleShare Client 3.6.4
is the oldest version of the client in use here.
I configured the MacTCP to point to my firewall for
Internet access.
Maybe
this should point to the NT Server? It's a private
subnet configuration
where the NT server is for file and print sharing only; the Internet
connection is through a broadband firewall/router.
NT Services for Macintosh doesn't have the capability introduced in
the AppleShare Fileserver IP 5.0 that permits clients to make connections
over TCP/IP; and the earliest AppleShare Client that supports the TCP/IP
connections is 3.6.4 (we had to make that the baseline while we were
still running a Mac fileserver).
If you're trying to access the NT Server across anything other than
the LAN that the NT Server's NIC is connected to, you're out of luck.
No bridges, routers, etc.
Additionally, you have to create a directory somewhere, share it for
access by Windows clients, then use NT File Mangler to create a Mac
Volume from that shared directory before the macs can see them. But
it sounds like you're having trouble before you get that far.
Hope some of this helps...
-dq