Re: Database Access Issue
From: William Smith (mecklists_at_REMOVETHIS.mn.rr.com)
Date: 10/21/04
- Previous message: bighdaddy1: "Database Access Issue"
- In reply to: bighdaddy1: "Database Access Issue"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 20 Oct 2004 22:54:47 -0500
In article <58624910.0410180931.7787b5b3@posting.google.com>,
bighdaddy1@yahoo.com (bighdaddy1) wrote:
> Hello,
>
> I reciently attempted to migrate a database application and a number
> of file shares from an NT4 server to a Windows 2000 server. The
> clients accessing the file shares and database are a mix of Windows
> XP, Mac OSX, and Mac OS 9.x.
> Does anyone have any clue how to get all of the clients to access the
> database on the remote W2K server without enabling Appletalk on all
> the routers?
In today's network environment, Appletalk is used only to browse a
network server. When a connection is made (selecting an item in the
Chooser) the Windows 2000 server and the Mac negotiate an IP connection.
Fear of Appletalk is probably unfounded in your network.
To address your problem, when your Mac OS 9 machines connect to the
server, they are using AFP (Apple Filing Protocol) over IP. They are
still using the Windows Server's File Services for Macintosh sans
Appletalk. (This is all relevant unless you're using a third party
product on your Macs such as Dave.) These machines are not using the
Windows share. Instead they are using a Mac volume. This is similar to a
Windows share but is not the same connection that Windows users connect
through. You can think of a Windows share and a Mac volume as being the
front doors to a server. They both let different clients into the server
but once inside, the permissions are the same for both.
You may need to make the Mac volume and Windows share "read only" to be
able to access the database from multiple machines. This will connecting
Macs from opening the file and showing it to be in use to the server.
This only works in a situation where you need to just read data and not
write.
Since I'm not familiar with your database, the above may not apply but
this is the most I can suggest based on your description so far.
Hope this helps! bill
-- William M. Smith (Microsoft Interop MVP)
- Previous message: bighdaddy1: "Database Access Issue"
- In reply to: bighdaddy1: "Database Access Issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
