Once a Mac (running MacTCP, or Open Transport versions older than the one
that came with MacOS 7.5.5 or so) has had problems looking up any name, it
seems to develop what I've called Macintosh DNS Insanity.
This is the malady cured by quitting all TCP/IP clients, tossing out
"MacTCP DNR" from the System folder, and rebooting.
However, I can't explain the connection refused by the server messages when
an IP address is given to Navigator. [Although quitting and relaunching
Navigator/Communicator sometimes helps it.]
--John (who has no desire to run anything older than MacOS 8.6)
PS: I run my machine configured to use only our primary DNS...it gives me a
nice alert when that goes away, which I could miss if I configured
"correctly".
"Matt Hadlock" <mhadlock@bainbridge.net> wrote
>Thanks for the info but I don't think that this is the answer to my problem.
>Why don't you see if you could reach my DNS servers, they are 207.138.224.12
>(primary) 207.138.224.11 (secondary)I have no problem using either. Also, if
>the user inputs an IP address they get the same error message from Netscape.
>
>The error message is:
>Netscape was unable to connect to "...", The connection was refused by the
>server, please try again later.
>
>For some strange reason, It seems that the Macs are unable to route beyond
>our local subnet.
>
>:----------------------~~~~~~=~~~~~~---------------------------:
>: Matt Hadlock -=- Systems Administrator :
>: admin@bainbridge.net -=- mhadlock@bainbridge.net :
>:Northwest Network Services -=- BainbridgeNet Internet Services:
>:..............................................................:
>
>-----Original Message-----
>From: owner-portmaster-users@livingston.com
>[mailto:owner-portmaster-users@livingston.com]On Behalf Of Tim Seibert
>Sent: Wednesday, May 26, 1999 1:49 PM
>To: Matt Hadlock; portmaster-users@livingston.com
>Subject: Re: (PM) Mac OS 7.5
>
>
>Your secondary DNS server is down or unreachable, and the clients have
>MacTCP misconfigured. MacTCP has a pretty strange configuration. Often,
>I've seen it configured as this:
>
>mydomain.com 123.45.67.89
>. 98.76.54.32
>
>When it's set up this way, anytime they try to access a site on the
>mydomain.com domain, it will use the 123.45.67.89 DNS server. Everything
>else it uses the 98.76.54.32 one. If this secondary server goes down, they
>won't be able to look up any URL's outside of mydomain.com. You need to
>set them up like this:
>
>mydomain.com 123.45.67.89
>. 123.45.67.89
>. 98.76.54.32
>
>
>Tim
>
>At 04:32 PM 5/26/99 , Matt Hadlock wrote:
>>Hello all, I have a very bizarre problem.
>>
>>Up until about 5 days ago all of my customers with Mac OS 7.5 using MacTCP
>>have been working flawlessly. Now they can dial in just fine but they
>cannot
>>browse to anything beyond our local subnet. ALL other platforms are working
>>perfectly including Macs using Open Transport. I have not changed any
>>configuration for the last 2 months the problem is the same for both my
>>PM25r and my PM3 RAS servers. Has anyone ever seen anything like this?
>
>-
>To unsubscribe, email 'majordomo@livingston.com' with
>'unsubscribe portmaster-users' in the body of the message.
>Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
>
>-
>To unsubscribe, email 'majordomo@livingston.com' with
>'unsubscribe portmaster-users' in the body of the message.
>Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>