Don't worry about asking a stupid question; it's a stupid situation that I am finding myself in.

I've been using all of my own settings:

Airport Router: 10.0.1.1
Host Machine: 10.0.1.4
tap0: 10.0.1.8 (linked to en1 in IPNetRouter, configured on subnet 255.255.255.0)

And in OS9
IP Address: 10.0.1.12
Subnet Mask: 255.255.0.0
Router Address: 10.0.1.1

And I've tried DNS addresses of:

207.xxx.xx.132, 207.xxx.xx.1, 66.yyy.yyy.237 and zz.myinternetprovider.net

but none of those DNS options seem to work. As a side note, 10.0.1.8 and 10.0.1.12 were both unassigned IPs on my network.

I really do wonder if it's an Airport internet card problem (en1, computer side), or an Airport Express (router side) problem.

Unfortunately I don't have another router to test. It would be interesting to see if anyone using a Dlink or Linksys (or another non-Apple) wireless router can get this to work.

PS. Thanks for helping me troubleshoot Cat_7!

Well obviously you got the numbering scheme sorted.
Have you tried to run the following command in a new terminal window?:

Sudo tcpdump –ni en1

I sometimes needed that to get the network going. Don't ask me why...
Can you post some of the output?

Cat_7

Hi Cat_7, sorry for taking so long to respond. I've been trying to wrap up my Master's thesis these past couple of weeks.

Note that 10.0.1.12 is my OS9 IP address, and 10.0.1.4 is my host computer, and 10.0.1.1 is my router

Running the 'tcpdump' command doesn't allow me to connect. Here is some of the (notable) output that is being returned:


22:29:02.209016 IP 10.0.1.4.631 > 10.0.1.255.631: UDP, length 151

22:29:07.385991 ARP, Request who-has 10.0.1.1 (ff:ff:ff:ff:ff:ff) tell 10.0.1.12, length 28


It does look like my OS9 is trying to connect with my Airport Router... Any thoughts? Thanks.

Ah, no problem: gives me time to write my PhD research plan

Can you provide me with a screen dump of the ifconfig command when the tap device is active?

Cat_7

I'm having the same problem. Looks like I might be able to go downstairs and plug in the hardwire connection for a temporary fix, but it'd be nice to know how to do this over wireless.

Hi,

The wireless option seems flawed when using this Appletalk solution. Can you connect to websites by using their ip-address instead of DNS name?

I would be interested in knowing if you succeed in creating a connection when using the wired option.

Best,
Cat_7

Works great when connected by Ethernet cable. Didn't seem to have any impact on connectivity on OS X host, either. No luck with wireless, though. Putting IP addresses in doesn't help—still no connection.

My ultimate goal is to be able to mount OS 9 server drives or other OS 9 shared drives in my Sheepshaver.

Following the instructions at http://www.open.ou.nl/hsp/engels/Applet ... Shaver.htm,
I am trying to launch Sheepshaver with root privileges.

It does not work:

MacPro2:~ mine$ cd /Users/mine/Documents/Sheepshaver/SheepShaver.app/Contents/MacOS
MacPro2:MacOS mine$ sudo ./Sheepshaver
SheepShaver V2.3 by Christian Bauer and Mar"c" Hellwig
ERROR: Cannot open ROM file.
MacPro2:MacOS mine$

It launches fine when I double-click the .app from the finder.

Any ideas?

When you want to launch the SheepShaver executable directly, both from Terminal or in the Finder, all paths to the needed files (rom file, disk image files, keycodes file) need to be full paths.

The built-in preferences editor only provides relative paths. To enter full paths, it is easiest to edit your .sheepshaver_prefs file manually in a text editor. TextEdit can be used. Entering in Terminal:

will open the file in TextEdit.

Edit: Be carefull when you want to use the shared folder feature while running SheepShaver as root !

This guide:
http://www.emaculation.com/doku.php/app ... heepshaver
also provides hints about using a script to set things up so you don't have to perform the steps manually all the time.

Best,
Cat_7

Successfully mounted drive on OS 9 server with Sheepshaver. Astonishing.

Do I always have to run Sheepshaver as root for this to work? Why do I have to run as root?
What do I need to be careful of? Ronald warned about using the Unix drive as root. Can someone explain?

Thanks!
anne

I never tried it, but it could well be that files added to the Unix disk or changed on the Unix disk while SheepShaver is running with root privileges will appear to be owned by system on the MacOSX side.

Yes, you are right. the document I saved is owned by root, and I could open it, but not save changes.

It appears that I can't get the server to mount unless I am running Sheepshaver as root.
Is this the case?

Hi,

The actual reason why you have to run SheepShaver as root is that only then the tap device you need to get real appletalk running is created during SheepShaver's start. So the tap device is the bottleneck in the procedure. Until someone re-programs SheepShaver to start the device without explicit root privililedges.

Can you not access the server drives through tcp ip, by entering the ip-address of the server and then choosing a share? That would make the appletalk steps superfluous.

Cat_7

No, I can't seem to get the drive to mount unless I do the IPNetRouter tap0 Bridge procedure.

Is there somewhere you can point me for directions on this?

My Sheepshaver prefs file would have to be changed from tap0 back to slirp for this?

Good news! Using the tap0 and IPNetRouterX software, I have been able to mount shared drives on the desktop, and actually see printers in the chooser. Very exciting! Now I just need to write a utility to fix the user on files in the Unix drive, and things will be pretty smooth going.

Yay! Thanks everyone for the help.
anne

Hello, I think there may be a typo that has been propagated from the original link below.

most scripts I see start with
#!/ rather than
#/!

It seemed to work anyway, but I am searching for reasons why
I get the colorful beachball of delay when I launch the script...

Here is a quote of the web page I copied the script from:

--------------
Automating the procedure with a script

Based on: http://68kmla.net/forums/viewtopic.php?f=15&t=11685

You can use the script below (4 lines) to automate the procedure:

#/!bin/bash
--------------

-anne

Hi,

Doesn't the hash in front of the line indicate it won't be read when running the script? otherwise it wouldn't work.

Cat_7

In most cases, yes, but the correct first line for a bash script is in fact:

fixed in the tutorial.

Thanks,
Cat_7