NET USE command problem

[luvtopost]

Hi all.
I have an issue. I've been using a DOS diskette that i configured to
boot from a particular Dell machine with appropriate dos drivers to the
network. It works fine as i have created a batch file with the NET USE
command to map to a current server(net use driveletter:
\\servername\share) for ghosting. My problem is mapping to another
server in DOS mode when bootup with disk which uses a fully qualifed
domain name(\\appserver.texas100.exxon.net). It keeps telling me the
syntax is incorrect eventhough i typed in the fully qualifed name
whenever i put it in the batch file or type it in at the dos bootup
prompt. However, if i go to a windows machine already logged into the
network, i can type in NET USE X:
\\appserver.texas100.exxon.net\backup$ at the dos prompt and it maps
ok. I've also tried putting the * instead of driveletter and still same
problem telling me Syntax incorrect. this server doesn't have WINS so i
have to use the fully qualified domain name according to the
administrator. It has something to do with the DOS bootup prompt vs.
the DOS prompt within windows maybe? Any thoughts? Thanks.

 

[luvtopost]

BTW, I tried using ip also. Didn't work from DOS bootup dis, but ok
within DOS prompt after logging into machine.

 

[Pegasus \(MVP\)]

Hi all.
I have an issue. I've been using a DOS diskette that i configured to
boot from a particular Dell machine with appropriate dos drivers to the
network. It works fine as i have created a batch file with the NET USE
command to map to a current server(net use driveletter:
\\servername\share) for ghosting. My problem is mapping to another
server in DOS mode when bootup with disk which uses a fully qualifed
domain name(\\appserver.texas100.exxon.net). It keeps telling me the
syntax is incorrect eventhough i typed in the fully qualifed name
whenever i put it in the batch file or type it in at the dos bootup
prompt. However, if i go to a windows machine already logged into the
network, i can type in NET USE X:
\\appserver.texas100.exxon.net\backup$ at the dos prompt and it maps
ok. I've also tried putting the * instead of driveletter and still same
problem telling me Syntax incorrect. this server doesn't have WINS so i
have to use the fully qualified domain name according to the
administrator. It has something to do with the DOS bootup prompt vs.
the DOS prompt within windows maybe? Any thoughts? Thanks.

It's probably related to your second server name either being
too long, or having three full stops in it, or both.

 

[Herb Martin]

It's probably related to your second server name either being
too long, or having three full stops in it, or both.

I believe that it is due to the DOS diskette (but perhaps it
depends on version) -- historically DOS did NOT understand
DNS names (i.e., with dots) in a UNC name.

DOS historically (and unless it has been significantly upgraded)
requires a NetBIOS name.

So using \\ServerName\Sharename\dirEtc would be required in
most cases. (Although I haven't tried it lately.)

NT4 introduced the acceptance of DNS server names into a UNC
name.

 

[luvtopost]

Herb,
Is there a workaround for this? Is there a way to break the fully
qualified name apart? The fully qualified name is
\\appserver.texas100.exxon.net and the share is \backup$.

I tried net use x: \\appserver.texas100.exxon.net\backup$ but no
success
I tried net use * \\appserver.texas100.exxon.net\backup$ with no
success
I tried net use x: \\appserver\texas100.exxon.net\backup$ with no
success either

I was told by someone working in another IT department that i might
have to use BartPE instead of the DOS diskette. I might end up doing
that. Thanks for input guys!

 

[Herb Martin]

Herb,
Is there a workaround for this? Is there a way to break the fully
qualified name apart? The fully qualified name is
\\appserver.texas100.exxon.net and the share is \backup$.

NetBIOS name would normally be JUST AppServer: \\AppServer

BTW, that is NOT a "FQDN" (or fully qualified domain name) but
just a DNS name -- an FQDN is a DNS name that is TERMINATED
with a "." (dot): appserver.texas100.exxon.net.

I tried net use x: \\appserver.texas100.exxon.net\backup$ but no
success
I tried net use * \\appserver.texas100.exxon.net\backup$ with no
success
I tried net use x: \\appserver\texas100.exxon.net\backup$ with no
success either

What's wrong with just using \\appserver\backup$

Normally the NetBIOS machine name is the same as the left-most
DNS tag so this should work just fine.

[You definitely cannot put the domain name into the share name as
in your third example.]

I was told by someone working in another IT department that i might
have to use BartPE instead of the DOS diskette. I might end up doing
that. Thanks for input guys!

Well, Bart PE and the Microsoft PE both use Windows (a
limited version) for the OS.

 

[luvtopost]

I get system 53 error when i try that. The network path was not found.
(\\appserver\backup$)

 

[Herb Martin]

I get system 53 error when i try that. The network path was not found.
(\\appserver\backup$)

If you have only one subnet, chance are you have disabled
NetBIOS on some or all of your machines (including servers);
you need NetBIOS.

Otherwise, chances are you have multiple subnets and therefore
a practical need for WINS server(s).

Then make sure you computer is a WINS client and that the
target server (e.g., AppServer) is ALSO a WINS client of
the same WINS server SET.