I never used IPNR. Running Airport 1.3. Like Steve, I have the "Airport IP"
extension; there are three extensions grouped with Airport by Conflict
Catcher. My copy, also, says "portions copyright by Sustainable Networks."
Looks like Apple licensed the software base station part from them.
If you are working without it, I wouldn't mess too much with anything.
However, you might want to scout around to see if there are any pieces from
the IPNR installation still left on your system. Maybe that "standard"
extension is conflicting with something from your previous software base
station system.
On or near 3/13/01 7:50 AM, Laurie A Duncan at [EMAIL PROTECTED] observed:
> Now Steve, don't go making me all sad again. I just checked IPNR installer
> log (I do save those every now and then), and that extension is listed. It
> may be installed with the Airport software as well, but in Conflict Catcher
> it does say "sustainable networks" as the author, and not Apple all the
> other Airport extensions say Apple. And the icon is defiantely an IPNR icon.
>
> I just enabled that extension again and Entourage crashed. I disabled it and
> everything works.
>
> At this stage, whether Airport installed that extension or IPNR installed
> that extension, I am keeping it off since everything works without it!
>
> Also, remember I am using only a software basestation, with no apple
> stand-along basestation unit. I've a feeling things would be different if I
> were using a separate basestation.
>
> BTW -- be sure you are not confusing Airport AP with Airport AP Support,
> which is another module/extension that is clearly installed with Airport 1.3
>
> There's actually a brief reference to these 2 files here:
>
> http://www.macfixit.com/ultimate/Forum24/HTML/000002.html
>
> Thanks for your help though.
>
> -Laurie
>
>
> On 3/13/01 10:32 AM, "Steve Sell" <[EMAIL PROTECTED]>, added a note to the
> human symphony when this was said:
>
>> Laurie,
>>
>> I wouldn't be so sure -- I just got a PB G4 with Airport Installed and that
>> extension was installed right from the factory. Look at the description in
>> conflict Catcher -- the description comes from the extension itself and it
>> clearly says it's for the AirPort 1.3. I would assume that Apple licensed
>> some code from the IPNR folks. But it most definitley _is_ installed by the
>> AirPort 1.3 package. I even confirmed this by installing AirPort 1.3 on
>> another powerbook we have - neither of my machines had ever had IPNR
>> installed.
>>
>> -Steve
>>
>>
>> On 3/13/01 8:11 AM, "Laurie A. Duncan" <[EMAIL PROTECTED]> wrote:
>>
>>> Please forgive me for being such a dope. I just realized that in Conflict
>>> Catcher, when I list files by package, it includes an extension called
>>> Airport AP in the package. Well silly me, I natuarally assumed that Airport
>>> installed that and that it was a required extension. Then I looked closely
>>> at the icon...and the icon looks different. The icon clearly has an "IP"
>>> stamped on on it and has the IPNR colors. DUH! That's not an Apple Airport
>>> extension, that's an IPNetRouter extension! What threw me was that it is
>>> also v. 1.3 so i didn't give it a second thought when I was enabling all my
>>> airport extensions last night after installing the card. I mean it was
>>> listed in the Airport Pakcage!
>>>
>>> Sure enough, by disabling just that extensio and leaving the other 3 APPLE
>>> Airport extensions, Entourage works fine now :)
>>>
>>> Sorry for not catching that sooner and for not sparing the list from my
>>> "unsolvable problem" despair.
>>>
>>> Please don't kick me out of the Entourage:mac club :)
>>>
>>> But while I am on the subject...any known problems enabling PROGRAM LINKING
>>> over airport so I can run the Cube's Entourage app remotely from my iBook?
>>> I've never had reason to use Program linking before, but it seems it may be
>>> handy now that I am so mobile around the house :)
>>>
>>> Thanks for everyone's attempt to help me solve a problem I brought on myself
>>> :)
>>>
>>> -Laurie
>>>
>>>> On 3/13/01 3:34 AM, [EMAIL PROTECTED] showcased their stellar typing and
>>>> language skills in this message:
>>>>
>>>>> If I understand you correctly. You have your DSL Modem connected to the
>>>>> ethernet port of your Cube forming a WAN, and your iBook and and Cube are
>>>>> using an Airport link to form a LAN. And you are using Airport 1.3 as a
>>>>> software router between the two networks. Do you have anything else
>>>>> connected to either network?
>>>>
>>>> DSL modem connected to ethernet hub, ethernet cables running from hub to
>>>> Cube
>>>> and iBook (this set up since I previously had a wired sharing system
>>>> running
>>>> with IPNetRouter on the Cube, Everthing worked beautifully with iBook able
>>>> to
>>>> filshare and share DSL connection. Only thing I had to change to use Cube
>>>> as
>>>> base station, was disable IPNetRouter and configure Software Basestation,
>>>> the
>>>> 2 together are redundant (Airport software is actually based on IPNR)
>>>>
>>>>> Are you using Airports NAT capability, or do you have two IP Addresses
>>>>> from
>>>>> your ISP. If your using Airports built-in NAT, you will need to configure
>>>>> *both* the iBook and Cube to use the Airports router address. Your Airport
>>>>> software will translate the router address to the actual IP Address issued
>>>>> you by your ISP.
>>>>>
>>>>> You will also have to make sure that the TCP/IP Control Panel on your Cube
>>>>> is configured to use the Airport software as its gateway. Not the Airport
>>>>> card. The software is your Cubes route to the WAN gateway, not the Airport
>>>>> card. -- Your iBook should continue to be configure to using its Airport
>>>>> card, as this is its path to the gateway.
>>>>
>>>>
>>>> I have one static IP. Cube is configured properly to route everything and
>>>> both
>>>> machines access the internet over DSL perfectly when Airport is enabled.
>>>> TCP/IP CP is configured to use my normal IP addresses for settings since it
>>>> is
>>>> acting as the base station. It doesn't work if I switch it to Airport. Per
>>>> the
>>>> Airport manual (and the Airport software alert I got when I was configuring
>>>> it, the "host computer" when it is the basestation, uses it's normal DSL
>>>> settings. If that is incorrect, please advise (both me and Apple!)
>>>>
>>>>> As far as File Sharing and Airport. I'm using Airport software 1.2, but
>>>>> had
>>>>> no trouble using either with SurfDoubler (a software router) and my iMac.
>>>>> (I
>>>>> am now using a hardware router.) I just had to be clear on on my AppleTalk
>>>>> and TCP/IP control panel settings. AppleTalk had to be pointed to the LAN
>>>>> and TCP/IP had to be pointed to the software router.
>>>>
>>>> Filesharing alone doesn't effect anything. I have filesharing enabled now,
>>>> with Airport disabled and everything is smooth.
>>>>
>>>>> A question, is your web browser working on your Cube. My guess is that it
>>>>> isn't.
>>>>
>>>> My browser (IE 5) works fine under Airport - on both computers. It is only
>>>> Entourage that is afected. No signs of trouble elswhere. Even filsharing
>>>> works
>>>> fine over TCP/IP with Airport enabled. But I cannot use Entourage. The
>>>> moment
>>>> it starts to check for mail it freezer forcing a force quit.
>>>>
>>>>
>>>>> Sorry I can't help you if your using PPPoe.
>>>>
>>>> I am not using Ppoe. I have a static IP and 24/7 on connection.
>>>>
>>>>> Russell Carr
>>>>
>>>>
>>>> Thanks for trying! If I have a step misconfigured above, I'd love to know
>>>> how
>>>> to fix it!
>>>>
>>>>> on 3/12/01 8:05 PM, Laurie A. Duncan at [EMAIL PROTECTED] wrote:
>>>>>
>>>>>> Just when I thought i had it all figured out...
>>>>>>
>>>>>> Installed Airport cards tonite in my Cube and iBook, using the Cube as a
>>>>>> software base station to share my DSL connection and files (over TCP/IP).
>>>>>>
>>>>>> Everything appeared to be working swimingly. Ibook is able to access DSL
>>>>>> connection and file share with the Cube.
>>>>>>
>>>>>> My Cube is now behaving strangely. Now I can't launch Entourage without a
>>>>>> freeze. I reinstalled, I copied the MS Insternet Library file over to my
>>>>>> Office folder again, I trashed the Finder prefs, I even ran DiskWarrioir
>>>>>> and
>>>>>> replaced the directory, etc...but it still is not happy. Disabling the
>>>>>> Airport set of extensions and switching my Location Mgr back to standard
>>>>>> ethernet settings makes Entourage happy again. But it defeats the purpose
>>>>>> of
>>>>>> the Airport card :)
>>>>>>
>>>>>> Only thing, besides the Airport extensions, that I am doing differently
>>>>>> is
>>>>>> that I now have file sharing opening upon start-up.
>>>>>>
>>>>>> Is it the combination of FileSharing PLUS the Airport extensions (using
>>>>>> the
>>>>>> latest Airport 1.3 btw...) or just Airport itself OR just FileSharing
>>>>>> itself
>>>>>> causing the problem? What happens is that as soon as Entourage goes to
>>>>>> check mail, it just locks up and I have to force quit, which then renders
>>>>>> my
>>>>>> system pretty unstable so I have to reboot and start all over again.
>>>>>>
>>>>>> Anyone have a clue before I go insane with my 25th restart in an hour? I
>>>>>> can't take it anymore and I think I've tried every combo of FileSharing
>>>>>> on/of, airport on/off etc.. But i am losing track :( Currently I have
>>>>>> Location Manager set to use my plain old wired ethernet connection (which
>>>>>> it
>>>>>> does even using Airport as it's serving as the BaseStation), and I have
>>>>>> FileShare ENABLED. The Airport extensions are disabled.
>>>>>>
>>>>>> Thanks in advance,
>>>>>>
>>>>>> Laurie
>>>>>>
>>>>>
>>>
>>
>
--
Peace,
Allen Watson <[EMAIL PROTECTED]> XNS name: =Allen Watson
A Mac family since 1984 <http://home.earthlink.net/~allenwatson/>
Applescripts for Outlook Express and Entourage:
<http://homepage.mac.com/allenwatson/>
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
