[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Macintosh, AppleShare IP Users
- Subject: Re: [cobalt-users] Macintosh, AppleShare IP Users
- From: Dave Shugarts <Azimuth@xxxxxxxxxxxxxx>
- Date: Wed Apr 4 22:22:06 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Thanks for the comeback, Aaron.
They are an assortment from OS 8.1 through OS 9.0.4.
I get the impression that the Macs fail to receive, or lose, their DHCP
leases, then I think they self-assign themselves an "Apple" IP in order to
be able to share folders that they are set up to share.
I don't know if it is germane, but, under the OS 9 control panel for File
Sharing, there is a check box about "Enable file sharing clients to connect
over TCP/IP," and the same for Program Linking. This check box is not
present in the OS 8 control panel. I have these check boxes turned off for
the OS 9 machines, but perhaps I should turn them on?
I believe that when we go to Appleshare 6.3.3, we will get new client
software for all the machines--I am just guessing from the literature.
--Dave Shugarts
>
> Hi Dave,
> What system are you running on your Mac's? I have had similar problems
> at work and it was a OS9 issue with DHCP.
>
> Aaron Anderson
>
>
> ----- Original Message -----
> From: "Dave Shugarts" <Azimuth@xxxxxxxxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Sent: Wednesday, April 04, 2001 3:21 PM
> Subject: [cobalt-users] Macintosh, AppleShare IP Users
>
>
>> I have set up a Qube 3 to be the Web access, Web server and DHCP server
> for
>> a network that contains an Appleshare IP 5.0 server and about 12
> computers--
>> all Macs of various kinds (all PPC). All of the Macs are configured to
>> obtain their IPs from a DHCP server.
>>
>> The Cobalt runs fine and talks to the Web fine, and when everything is
>> running right, the Macs obtain the DHCP service and acquire an IP from the
>> Cobalt's block of IPs (e.g., 10.6.18.X).
>>
>> However, at various points in the day, they somehow "lose it" and begin
>> using their own Apple-supplied IPs (e.g. 169.254.220.X) for no discernable
>> reason.
>>
>> When this occurs, no machine on the network can talk to the Cobalt,
> although
>> a machine coming in from outside can talk to the Cobalt, access all of its
>> admin functions through the GUI, and everything appears to be running fine
>> on the Cobalt.
>>
>> Nonetheless, because the Macs can't see the Cobalt, we wind up rebooting
> the
>> Cobalt. At that point, it returns to normal--until the next episode.
>>
>> We have placed an order for the latest Appleshare IP 6.3.3, but do not
> know
>> whether this will make a difference.
>>
>> Any thoughts, anyone?
>>
>> Thanks
>>
>> --Dave Shugarts
>>
>> _______________________________________________
>> cobalt-users mailing list
>> cobalt-users@xxxxxxxxxxxxxxx
>> To Subscribe or Unsubscribe, please go to:
>> http://list.cobalt.com/mailman/listinfo/cobalt-users
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users