Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A bug with classic while this is turned on' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A bug with classic while this is turned on
Authored by: usermilk on Dec 25, '01 10:35:32AM

It seems Classic applications cannot access the internet while your DNS is set to 127.0.0.1, when I removed the DNS entry I restarted Classic and everything was fine.



[ Reply to This | # ]
Info on and fix for the Classic Bug
Authored by: dlandrith on Dec 29, '01 03:33:13PM

It's taken me a while to get around to this since I don't run Classic, and I had to install it in order to test.

This is an interesting problem, that does not seem related to OpenTransport's screwy implementation of loopback addresses. Even if you put your IP address into the DNS list instead of 127.0.0.1 (which works in OS X), Classic will not resolve names. Moreover, endless fiddling the the IP Secondary Addresses and Hosts file do not solve the problem, though I'm not even sure that these are used in Classic mode. Any info that you can provide on this would be useful.

At any rate, the following solution does work:

Place your normal name server as the second name server in your list, and Classic will use this name server. I haven't noticed any delay caused by this.



[ Reply to This | # ]