Well, it turns out that the MSCLIENT stack *can* do DNS resolution; you just have to load the "dnr.exe" tool first. And possibly configure it.
I have put a copy of dnr.exe in <http://unattended.sourceforge.net/testing/>. To try it: 1) Add it to your boot disk 2) Edit \net\tcputils.ini to add a section like this: [DNR] drivername=DNR$ bindings=TCPIP_XIF 3) Invoke it from autoexec.bat (just after "tinyrfc.exe") Then maybe (big maybe) you will be able to map shares by DNS name. Or maybe you will have to add some DNS servers by hand... I honestly do not know. But it is worth a shot :-). - Pat Justin Beckley <[EMAIL PROTECTED]> writes: > I can ping the server if I fill out the whole IP name, > ie. myDC.ece.utk.edu will ping successfully, but myDC would fail. The > "net use" command is old enough that myDC.ece.utk.edu will not work > with it, but if you use the "Map Network Drive" feature, you can use > the whole IP name. I think that if I can add the proper entries to the > lmhosts file, it should work with just the name. Maybe I am wrong > about this? Anyone got any suggestions? > > Justin Beckley ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
