>>on 3/12/01 8:54 PM, Bookout at [EMAIL PROTECTED] wrote:
>>
>>> Whenever I try to set PC's (not just one machine) connected to a Local
>>> Area EtherNet to Multi-User eBase opened in FileMaker Pro v.4.1, I get the
>>> following error:
>>>
>>> "Filemaker cannot host a file because of a network error. Files marked as
>>> Multi-User will not be available over the network [-10]."
>>>
>>> If I open a Mac on the same network to Multi-User and then try to open a
>>> PC to guest via the "Host" button, the Mac does not show up as the Host
>>> machine in the PC's window.
>>>
>>> FMP shows that TCP/IP is loaded successfully on startup on both Mac
>>> (Quadra 610, System 7.5.3) and
>>> the PCs.
>>>
>>> The EtherNet LAN PCs work normally via Client for Microsoft Network using
>>> NetBui and TCP/IP protocol in other respects. They share "print and file"
>>> with each other in a peer to peer network..
>>>
>>> Is there some TCP/IP configuration in Windows 95 that the PCs run that I
>>> have overlooked? I also wonder how to set TCP/IP in Open Transport of the
>>> Mac: if "manually," I am required to set the Mac's IP address to a static
>>> setting. The PC's are set to "automatic" addressing. Should the PC's be
>>> given static addresses by means of Hosts file?
>>
>>If you host on a PC, can the other PCs open via hosts but not the Mac?
>>
>>Are you using DHCP server? Try having the Mac get its IP address from the
>>same address server as the PCs. It doesn't make sense, I think, for it to
>>have a static IP address if there's a server responsible for assigning IPs.
>>You don't mention whether the Mac can see printers or servers in the Chooser
>>dialog box.
>
>
>Colin, there is no server responsible for assigning IP's. I'm not
>using AppleShare, Windows NT/2000 Server or NetWare on a dedicated
>server machine.
>All the Council has is plain vanilla Windows 95 Client for Microsoft
>Networks peer-to-peer networking with NetBeui and TCP/IP bound to
>it. Therefore, the Mac cannot "see" printers or servers in the
>Chooser dialog box as would be possible using a server to client
>arrangement. This is apparently a completely different situation
>from the kind of interoperability offered by FMP/ebase PC to Mac
>connectivity in which FMP "loads" TCP/IP and makes reciprocal
>visibility possible? What I am wondering also is just what
>configuration of TCP/IP does FMP "load"? Do the individual settings
>of TCP/IP in Mac Open Transport and Windows Properties make any
>difference to what FMP "loads"? or does FMP configure TCP/IP for
>itself? There isn't a word on this subject in the ebase
>Administrator's Manual, in the FMP 4.1 manual or in FMP 4 Bible
>(Schwartz). Mac Open Transport using Ethernet allows only "manual as
>opposed to server settings with BootIP, DHCP or RARP." Since no
>servers are being used on the network, I am left with manual
>configuration of the Mac as the *only* possiblity. Does this mean
>that the Windows 95 TCP/IP, IP addresses must also be *manually*
>set? How does Windows assign IP addresses "automatically" in a
>peer-to-peer network?
>
>The Council has applied with Semantec recently for additional copies
>of FMP for its other PCs but at the present time we are working with
>only one PC on which THE single copy of FMP 4.1 we own is installed.
>The other machine I am talking about is a Mac which was donated to
>the Council on which there was already a copy of FMP 4.0 and on
>which we installed ebase.
>
>So I've tried both approaches: to open the Mac and PC (first) as
>host to the other machine, in which cases I get a net work error on
>either the PC or on the Mac that FMP/ebase cannot be set to
>Multi-User; also, when an attempt to open either machine as guest
>the host, of course, does not appear in the appropriate window.
>
>We had an arrangement between two Macs working fine via LocalTalk
>but the complaint was that the machines were too slow to make
>entering data into the 29 ebase relational files feasable (25 Mz!).
>We switched to the PC as host so we could cook at the amazing speed
>of 133 Mz! (No one should underestimate the extent to which
>non-profits try to survive with obsolete equipment--there is not one
>penny in the Council's budget for computer hardward, software or
>supplies. Everything is "crufted" together from donations--"ugly but
>temporarily functional."
>
>My difficulty is probably the result of this first attempt at
>networking and also of a relatively greater familiarity with Macs
>than PCs.
>
>Thanks, Colin, for your speedy reply to our delimma. I'd like to
>thank Barry Madore also who has tried to help, but he anticipated
>himself that using NetBeui alone would leave the Mac stranded.
>
>Henry Bookout
>North Fork Environmental Council
>P.O. Box 799
>Mattituck, NY 11901
>
>631-298-8880
I'm glad to say I got the Mac Multi-User enabled and the PC connected
to it as a guest via ethernet. This, by manually configuring Mac
TCP/IP, IP address in Mac Open Transport, essentially, as explained
for DAVE by Thursby Software Systems, Inc.
(http://www.homepcnetwork.com/pcmacp2ovr.htm). The PC that talks to
the Mac had its TCP/IP, IP address configured manually also as
explained on the website above.I don't understand why three other PCs
on the same network can talk to my guest PC with their TCP/IP, IP
address not manually, but automatically assigned, but it works
anyway. The subnet mask is manually assigned 255.255.255.0 on both PC
and Mac. I didn't enable the hosts file on the Mac as suggested on
the webpage, but it still worked (The webpage did not mention a hosts
file for the PC which I would have thought necessary if the Mac
needed one.)
Henry Bookout
NFEC
Mattituck, NY
------------------
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address
you used to subscribe to the ebase support list:: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------
