Print

[bmwcyclist]

Hello!

Why do the simple things seem so hard sometimes?

I have a good WORKING OS 7.5.5 that works just fine with TCP/IP but of course 7.5.5 is a memory hog

I made an OS 7.1 profile image, configured it the same, and it won't work.

I checked with the BlueSCSI docs, and I don't seem to be missing anything.

What I assume are the relevant settings:

MacTCP same settings (IP, subnetmask, DNS)
Wifi control panel: finds the wireless SSID on both 7.1 and 7.5 so I think they are both able to communicate with BlueSCSI
DynaPort driver installed.

The BlueSCSI documentation seems to indicate that the DynaPort will work with 7.1 even though it does not have OpenTransport.

TESTS:

System 7.5
Ping from external host (after launching browser, or MacTCP Ping which is interesting)
Pings out
Browser works


System 7.1
No ping out to internet or local host
No ping from local host

Any suggestions?

the fact 7.5 does not respond to pings until a TCP app is launched makes me wonder if it is a driver issue?

[D.Finni]

You need to do more than pings to test MacTCP. What TCP applications have you run on System 7.1?

[bmwcyclist]

You need to do more than pings to test MacTCP. What TCP applications have you run on System 7.1?

Thanks for the reply!

MacWeb 2.0

I am curious why you would need more than Ping?

Unless blocked by a firewall process, a ping should always receive a response from a TCP/IP host. As long as you ping an IP address and not a name, you don't have to worry about other services, such as DNS or specific ports. Even if the MacPing app is defective, a ping from another local host should get a response.

What other app(s) would be better?