Help with Mac Plus networking??

[WakelessFoil]

I have been trying for months to get my rare Asante EN/SC to work with my Macintosh plus to no avail. I have the adapter hooked up to a 10BaseT hub and I can even receive packets in the troubleshooter. But when I bring up Macweb it acts as though there is no connection; error 500.

Any help is greatly appreciated!

-Justin

 

[RogerWilco6502]

Is that an HTTP error 500? Because that would be an internal server error, so nothing on your end.

I don't know much about this specific configuration, but I have done a lot of troubleshooting network connections so I might be of use.

 

[defjam]

Can you provide additional information regarding the configuration? What version of MacOS are you running? Do you have the Asante drivers installed? Are you attempting a TCP based connection?

 

[WakelessFoil]

I’m running system 7.0.1 with Asante drivers 5.1.2. I am trying to set up a tcp based connection through macTCP 2.0.6. Below is a diagram of my hardware configuration and the Asante troubleshooter that says it’s receiving packets. But Mac web acts as if I have no network connection what so ever.

 

[RogerWilco6502]

Can you send a picture of the error?

 

[WakelessFoil]

It pretty much does this with any URL that I enter.
[automerge]1583601752[/automerge]

Can you send a picture of the error?

It pretty much does this with any URL that I enter.

 

[RogerWilco6502]

Ok, looks like you might have a DNS config issue. If I'm remembering correctly, when it can't find the host it means that the DNS isn't configured properly.

 

[WakelessFoil]

Ok, looks like you might have a DNS config issue. If I'm remembering correctly, when it can't find the host it means that the DNS isn't configured properly.

I set my dns to my router address and entered 1.1.1.1 as an alternate. I do this with all systems on my LAN.

So I finally connected, but there are still two issues with the set up. One, I can’t connect with actual URLs because of some http issue with macweb. But I’ve seen others use macweb with URLs in the search bar so I’m lost on this issue. I have to connect via public ip addresses. And two, I’m concerned for the health of the Asante EN/SC. It works fine and is in good condition but being so rare it makes me uncomfortable keeping it on 24/7. Should I unplug it when not in use or leave it on? It doesn’t have a power switch so I assume it’s supposed to stay on like a router or cable modem.

Anyways just for some enjoyment and satisfaction here’s the 33 year old Mac running on a 5 mbps connection to the web. Surprisingly usable despite all the Java and css problems. Loads a full google search in about 20 seconds.

 

[RogerWilco6502]

The DNS should also solve the issue with needing to use public IP addresses, but networking is something I don't know a whole lot about in comparison to some people.

I'm not sure about your second question, sorry.

 

[defjam]

I set my dns to my router address and entered 1.1.1.1 as an alternate. I do this with all systems on my LAN.

So I finally connected, but there are still two issues with the set up. One, I can’t connect with actual URLs because of some http issue with macweb. But I’ve seen others use macweb with URLs in the search bar so I’m lost on this issue. I have to connect via public ip addresses. And two, I’m concerned for the health of the Asante EN/SC. It works fine and is in good condition but being so rare it makes me uncomfortable keeping it on 24/7. Should I unplug it when not in use or leave it on? It doesn’t have a power switch so I assume it’s supposed to stay on like a router or cable modem.

Anyways just for some enjoyment and satisfaction here’s the 33 year old Mac running on a 5 mbps connection to the web. Surprisingly usable despite all the Java and css problems. Loads a full google search in about 20 seconds.

I meant to pick up one of these up yesterday and forgot all about it.

Do you have any network tools (ping, nslookup, telnet, etc.) available which would allow you to test? It appears you've got it partially working and that RogerWilco's suggestion of a DNS issue as a possible issue is reasonable. You also need to keep in mind many sites are rejecting HTTP connections and forcing HTTPs connections. The HTTPs connections will fail on older browsers due to SSL certificate issues. Perhaps this may be what you're experiencing?

As for leaving it on constantly if I recall that's a pretty solid box. The only concern I would have leaving it on 24/7 is a possible electrical surge.

 

[MacTech68]

Here is a vanilla http server you can test with to rule out the ssl/tls/certificate problems you WILL encounter on the majority of websites.

HTTP vs HTTPS Test

Encrypted websites protect our privacy and are significantly faster. Run this test and prepare to be amazed. #HttpsEverywhere

www.httpvshttps.com

If it fails to load, check your DNS with this old tool (not sure it works with 7.0 or 7.1)

https://archive.info-mac.org/_Internet/dns-lookup-092.hqx

Enter your ISP's DNS server when prompted. From the File menu select 'New Lookup', and enter a web name to lookup (like www.google.com)

Let us know the result.

 

[Anonymous Freak]

One problem with really old web browsers is that they don't support *ANY* of the modern web standards. Virtual servers are extraordinarily common, but old browsers don't support it. (I'm not talking "a server running in ESX," I'm talking where "one host acts as multiple domain names"

You can get around it by setting up a web proxy that "translates" new websites in to something readable to an old web browser. This would require running the proxy on a machine in your local network, and you would point your Mac Plus at *THAT* machine, which would present an interface to let you choose which website you want to go to.

Web Rendering Proxy is probably the best of them, but it renders the pages as a picture to the old system - there are other ones that "translate" new style web requests to old, with various successfulness.

GitHub - tenox7/wrp: Web Rendering Proxy: Use vintage, historical, legacy browsers on modern web

Web Rendering Proxy: Use vintage, historical, legacy browsers on modern web - tenox7/wrp

github.com

 

[reukiodo]

It's definitely a DNS issue. Is 1.1.1.1 a valid DNS-serving IP? You can use Google's 8.8.4.4 and 8.8.8.8 or OpenDNS instead.

Also, check out iCab as a more updated browser.