MacNN Forums (
-   Classic Macs and Mac OS (
-   -   MacTCP DNR (

wlonh Jun 20, 2000 01:42 PM
why is this file still needed? i have trashed it and it did not regenerate after restart (i'm experimenting, i know i can get a copy of it from my MacOS CD if needed) and i am using all my usual internet app's with no prob's

so what is up with MacTCP DNR? what, if anything, uses it these days?
slboett Jun 20, 2000 04:34 PM

After deleting it on my 9.0.4 Macs, it never has returned. So maybe it's just a useless leftover from earlier OSes?

wlonh Jun 21, 2000 07:39 AM
yeah that is what i figured, it is vestigial

but i still wonder why Apple leaves it in there... harrrumpf

[This message has been edited by wlonh (edited 06-21-2000).]
GORDYmac Jun 21, 2000 10:25 AM
DNR - Do not remove.
wlonh Jun 21, 2000 10:28 AM
yaaaa okey dokey yup uh huh u bet and how, pardner
slboett Jun 21, 2000 02:29 PM
And that from a senior member...

oscar Jun 21, 2000 02:57 PM
I believe the DNR stands for Domian name resolver

-See Yea!
wlonh Jun 21, 2000 03:04 PM
yes, either that or Domain Name Resolution, knew that... forget which it is exactly but that was never an issue for me here
slboett Jun 21, 2000 04:32 PM
Paul Crawford Jun 23, 2000 01:48 AM
Hi all,

I'm running under Mac OS 9.0.4 on a beige PM G3/266, and I too manually deleted the 'MacTCP DNR' file about a week ago. Like wlonh and Scott, I also have found that it has not re-appeared so far after rebooting, Internet access, etc. I guess Apple has finally dropped backward support for MacTCP and its older DNR mechanism, in favor of Open Transport/TCP and its modern DNR mechanism (available since System 7.5.2, I believe)?

My guess is that it's safe to delete the 'MacTCP DNR' file if you're not using any old MacTCP-dependent apps. I got the impression that the Mac OS 9.0.4 Updater automatically removes this file on some people's machines; why it didn't do so on ours, I'm not sure.


reader50 Jun 23, 2000 12:53 PM
I poked around in the TIL. MacTCP DNR apparently is present to support System 6 TCP applications.

We had all better leave this file alone. Who knows when we will boot up a System 6 app for cruising the internet?
GORDYmac Jun 23, 2000 03:03 PM
I stand corrected, I guess I'll trash mine too.
wlonh Jun 26, 2000 09:38 AM
slboett Jun 26, 2000 12:19 PM
wlonh Jun 27, 2000 11:57 AM
ah hahahhaha from MacFixit (today's issue) comes this:

"MacTCP DNR: gone or not? Despite Apple's statement that "with the release of Mac OS 9.0.4, the MacTCP DNR file was eliminated" (see yesterday's item), several readers dispute this claim:

"I just bought a new PowerBook (400 MHz) that came pre-installed with OS 9.0.4 and the MacTCP DNR file came right along with it." [Olaf Bininda-Emonds]

"Upgraded from OS 8.6 via disk directly to OS 9.0.4. I still have MacTCP DNR labeled as OS 9.0. I also checked the log file. It says MacTCP DNR was installed by OS 9.0.4 disk. Apple is in error." [Pat Styer]

Regardless, several readers note that if you delete the file, it does not return and all continues to work just fine."


sez me:
why, of course 9.04 installs it as a legacy concern, who knows what some Mac user is running that may require it? it is douibtful it would be needed! but there it is, MacTCP DNR, just waiting to be deleted...


[This message has been edited by wlonh (edited 06-27-2000).]
slboett Jun 27, 2000 01:31 PM
It's easy to tell whether you need it. If you delete it, it will re-create a new file on startup - not unlike many other preference files. If not, it's not needed.
I used to delete this in the OS 6 and 7 days as part of my routine maintenance. Doing so in OS 9 seems to rid the System Folder of the file permanently...
As Lon said: delete away!

wlonh Jun 28, 2000 11:29 AM
from you guessed it, macfixit, TODAY:

"We recently covered the issue of the MacTCP DNR file being officially dropped (or not) from Mac OS 9.0.4. Several readers, who deleted the file from their Mac OS 9.0.4 System Folders after reading this, had a mysterious result: After a restart, the file returned again but with a different name. The exact name varied from user to user.

R. Lynn Rardin writes: "A file appeared with the same icon but named "Command-V" (actually the character generated by typing Command-V)."

Jerry Kindall found a file that was empty but had the same type and creator as MacTCP DNR (cdev/mtcp). He adds that the file was named "^B^@ (an ASCII 2 followed by an ASCII 0). The name doesn't show up in the Finder, of course; I had to paste it into BBEdit, turn on Show Invisibles, and use the Show button in the ASCII Table window to figure out what the characters were. If I delete the file I get a new one, usually with a different weird name."

Craig Cobban's file had such an unusual set of characters in its name that we won't even try reproduce it here. If he deleted the file, it returned with the same odd name.

C.K. Sample similarly adds: "If I throw away the MacTCP DNR file, it does return, but corrupted under a mangled file name."

So far, Nick Chapman is the only reader to report any connection problems associated with this odd renamed file. He writes: "In the past, prior OS 9, occasionally I would find myself unable to connect to anything; looking in the System Folder, I would find that the DNR file, or at least the file with that icon, had its name changed to a line of gooblydegook. Deleting this file and restarting the computer used to create a new, okay DNR file. However, a few weeks ago, the DNR file began regularly changing its name to "gJ)"

sez me:
huh? what the heck? sure is amusing in a way

[This message has been edited by wlonh (edited 06-28-2000).]
wlonh Jun 29, 2000 02:00 PM
the controversy rages:

{from macfixit today 06/9/00}
"First a bit of background: This file has technically no longer been needed since the advent of Open Transport. It was used for DNS lookup back in the days of MacTCP. However, Apple has let it hang around primarily because some older software still looks for this file and may fail to work if it does not find it present (even though it doesn't need the file anymore).

As to why the file may reappear with an odd name after deleting it and what you can do to prevent it (beyond what was covered yesterday):

Mike Griswold simply disabled the file via Extensions Manager. This eliminated the problem.

Bill Giles replies: "My solution was to remove all Open Transport software and preferences. Install a fresh copy from the Mac OS CD. Then lock the TCP/IP control panel."

Quinn MacDonald suggests: "I have never noticed a common cause, except it only seems to happen after installing a Microsoft application that installs shared library files (which is just about all of them these days)."

Tim Mityok writes: "As for files matching the icon of MacTCP DNR but with random file names, this is most likely the result of programs attempting to locate the file and inadvertently or purposely creating one in its place when it is not found. If you have the "MacTCP DNR" file its probably best to leave it there."

Again, while most people experience no problems whether or not the MacTCP DNR file is present or not, named correctly or not, a few do continue to report problems with its absence or wrong name (most likely due to the potential problem with older software described above):

Bill Giles writes: "I've found that when the MacTCP DNR file has the strange name, I experience TCP/IP dropouts and an inability to connect at all."

Isaac Balbin replies: "I removed the file, and found that some applications simply broke. For example. Transmit failed to connect to any site, and Reflections (an HP terminal emulator) failed complaining that it needed MacTCP drivers."

debbieci Jul 4, 2000 01:44 PM
I started having internet problems, freezing/crashing every sesions, did everything possible to correct the problem, after three days read about this MacTCP DNR file and trashed the file and all is well. Havent had a problem since....
P Jul 24, 2000 10:16 AM
If it ain't broke, don't fix it. If you're having problems, maybe it's worth trashing it. If not, well leave it be, it's not exactly large.
wlonh Jul 24, 2000 10:30 AM
TRASH IT, with extreme prejudice

MacTCP DNR has always been troublesome, you just may not have been aware of it... nothing, i repeat, nothing will go wrong if you delete it (unless you are in the stone age, running some legacy app that wants it, in which case you can retrieve this misbegotten POS file from your MacOS CD and drop into System Folder) and things can most certainly go wrong as a result of having it on your Mac... word to your mother!

so trash the damn thing... period.

UPDATE: 07/27/00

"MacTCP DNR and FreePPP--- discusses an issue where you be unable to access Web sites via FreePPP, due to a corrupt MacTCP DNR file. Deleting the file is the solution."

sez me: no! really?? you must be joking!!! why, i never!!!!

[This message has been edited by wlonh (edited 07-27-2000).]
All times are GMT -4. The time now is 12:50 AM.

Copyright © 2005-2007 MacNN. All rights reserved.
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2017, vBulletin Solutions, Inc.

Content Relevant URLs by vBSEO 3.3.2