Re: [cobalt-users] Macintosh, AppleShare IP Users

["Gary Melendez" <gmelendez@xxxxxxxxxxxxxxxx>]

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
>

Dave,

I don't have any help to offer, but maybe I can add some information.

I also have a Qube 3. It's on a Windows NT network rather than what you have
set up, but I tend to see the same sort of behavior, albeit with somewhat
different symptoms. I am not using the DHCP server on the Qube 3 but I am
trying to use the Windows File Sharing (Samba) service. It will work for a
while and then it will just stop being available from the LAN. I get
something like 'Remote Computer could not be contacted,' or words to that
effect. I also have a Qube 2 and never had this problem, but ever since the
Qube 3 came in I've had trouble with both file sharing and with SMTP
service.

The SMTP service seems to take forever (up to 3 minutes) to allow a
connection for sending email. The Qube 2 never had this problem either.

I suspect these two problems are related, but I don't have enough data to
correlate them as yet.

As in your case, accessing the Qube 3 using it's real Internet host name
works just fine and there is no indication of a problem. I think what we are
seeing is an underlying problem with the Qube 3's ability to communicate,
either software or hardware, but I have no way to demonstrate or prove that.
I do know that, since I 'updgraded,' that solid reliability I felt with the
Qube 2 has started to evaporate.

Maybe others will chime in here and we can see if this a trend or not.

Thanks,
Gary