Ok, here's the list of questions that people have actually asked on the list, and the answers we've given them. (Unless i think that the answers were wrong, in which case i've taken the FAQ admin's perogative to make things right.)
Assuming both computers have 10-Base-T ethernet jacks (they look like oversized phone jacks, with 8 pins instead of 4), go to your local electronics store and ask for a 10-Base-T crossover cable. This will have pins 1&2 swapped with pins 3&6. Plug one end into each computer. Next you'll need either DAVE or PC MACLAN (What is this obsession with all cap product names?), detailed below. Oh, and if you have Mac OS 8 or FrontPage for either platform, you could make your machine into a mini web server and share files that way. (WARNING: Be careful with this, as you will be sharing your files with the whole world if and when you're connected to the Internet!)
Pete Jones <pejones [-at-] pop.dn.net> writes:
I've been using Dave 2.0 since March 98 and have nothing but rave reviews for it. I think that what some folks may miss about Dave is that it's really (IMHO) designed to do only one thing... put a Mac on a Windows NT-served network. At this it really shines. Using Dave to link a single Mac and a single PC (or any peer-based network) is possible but requires faking the network with hard-coded IP addresses to start, and no doubt Wingate is a much better solution. But if you have an NT network, preferably using DHCP, Dave works magnificently, and you don't have to install Services for Macintosh. Just let it run.
DAVE is available at ( <http://www.thursby.com>)
There's a cool rumor that MacOS 8.5 will come with an integrated SMB client, obviating the need for DAVE. (Ooh, bet the Thursby people will love that.)
Well, if you're running Windows NT Server, then you should use the included Services for Macintosh. It's in the manual. But if you need further help, check out: <http://www.macwindows.com/netbasc2.html#WindowsNT>
It's been confirmed that NT 5.0 will "beef up" the Macintosh support, in the form of support for Apple Remote Access Protocol (ARAP) as well as AppleShare IP (AFP over TCP).
Rick Kent <maverick [-at-] maverickmedia.com> writes:
We use PC-Mac LAN from Miramar systems. It works flawlessly for accessing anything that appears on our Mac Appletalk Ethernet network. The only requirment for printers, is that you have the PC versions of the drivers for that printer. That is not a problem for the Epson 800. We use an Epson Stylus Pro in much the same way. You will also have the advantage of being able to see any shared drives from the PC, and to share any of the PC drives onto the network. The manual is well written, and their technical support was great the one time we called. them.
Moderators comment: PCMacLan is an absolutely wonderful connectivity product both in its Windows95 and NT iterations. It adds feature sets to a PC that need connectivity to Macs that really is unavailable in singular products, and for accessing Mac printers it is without peer. We use it all of the time on our NT machines.
PC MACLAN is available at <http://www.miramarsys.com>
BTW, another rumor (actually, it's confirmed>) has it that AppleShare IP 6.0 will include SMB support. (i think Apple should call it "Services for Windows" as a nod to Windows NT's SFM. :-)
The consensus was that Windows .PST files (at least for messages) are not readable by the Mac Exchange client or Outlook. (Not sure whether Outlook Express does any better, as Ed Humes suggested.)
A workaround that was suggested was to use a Windows client to put the mail back on the server, and then access them with the Mac client.
A search in Microsoft's support database confirms that this is true for the Mac Exchange client versions 4.0 and 5.0:
See Microsoft Support article Q148271
That page also offers an ugly workaround for importing your e-mail addresses.
You're probably running OS 8.x, right? Well, that'd be the dancing or jumping icon bug. Here's info on fixing it on:
Two NT products are:
What you'll need is something to do IP forwarding of packets in your local "private network" to the Internet. There are several routes (no pun intended :-) you can take:
Additionally, Gabriel Lawrence <gabe [-at-] mediaone.net> mentioned
that Vicom has some FAQs about cable modems:
Derek K. Miller <dkmiller [-at-] pobox.com> recommended a a Mac Resource feature on the subject:
And finally (maybe) Greg Jewett <r4183c [-at-] email.sps.mot.com>
gives us a FAQ from Time Warner's site that claims you'll have to pay
for each additional computer (if you're using their Road Runner
service):
But i think that's bunk.
PGP: <http://web.mit.edu/network/pgp.html>.