want NT client to see server share

I want a machine running NT client under DOS to be able to connect to shares
on a Windows server 2003 machine. I've created a share and given "Everyone"
read access. I can connect to this share from windows 98 machines that are
NOT logged on using the server (they're just logged on locally as "guest" to
the workgroup WORKGROUP). however, when i try to do the same thing with the
NT client machine (connect as guest, with no password) and then do a:

net use * \\<server name>\<server share name>

i get an error:

error 53: the computer name specified in the network path cannot be located.

this same command works fine if i substitute a windows 98 machine name and
share for that 2003 name and share (ie. connect to a 98 share), which tells
me the networking is working. i'm using netbeui on all machines and tcp/ip
on the 2003 and 98 machines. also, for some reason, when i take tcp/ip off
one of the 98 machines and attempt a "net" operation with only netbeui, it
tells me i'm not logged on. this works fine with tcp/ip installed.

any help is greatly appreciated,

gary

--
Gary Roach
ADB Services

Hi Gary,

it looks to me that you have a problem with DNS or WINS.

what happens if you try with e.g.

net use x: \\<server fqdn>\<server share name>

Replace <share fqdn> with fully qualified name of your server (e.g.
server1.mydomain.com)

or

net use x: \\<server ip address>\<server share name>

Replace x: with free drive letter
Replace <server ip address> with IP address of server that you are trying to
connect to.

Again check DNS and WINS settings on Windows 98 PCs (see if you can resolve
host names on Windows 98)...


Mike

"Gary Roach" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>I want a machine running NT client under DOS to be able to connect to
>shares
> on a Windows server 2003 machine. I've created a share and given
> "Everyone"
> read access. I can connect to this share from windows 98 machines that are
> NOT logged on using the server (they're just logged on locally as "guest"
> to
> the workgroup WORKGROUP). however, when i try to do the same thing with
> the
> NT client machine (connect as guest, with no password) and then do a:
>
> net use * \\<server name>\<server share name>
>
> i get an error:
>
> error 53: the computer name specified in the network path cannot be
> located.
>
> this same command works fine if i substitute a windows 98 machine name and
> share for that 2003 name and share (ie. connect to a 98 share), which
> tells
> me the networking is working. i'm using netbeui on all machines and tcp/ip
> on the 2003 and 98 machines. also, for some reason, when i take tcp/ip off
> one of the 98 machines and attempt a "net" operation with only netbeui, it
> tells me i'm not logged on. this works fine with tcp/ip installed.
>
> any help is greatly appreciated,
>
> gary
>
> --
> Gary Roach
> ADB Services
>
>

DNS and WINS aren't relevant here since i'm using netbeui - i wish i could
use tcp/ip just to take netbeui out of the equation of unknowns but i don't
have tcp/ip ndis drivers for the cards in question. that may have to be the
next step - trying to get the tcp/ip drivers. thanks for the help

"Miha Pihler" <mihap-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Gary,
>
> it looks to me that you have a problem with DNS or WINS.
>
> what happens if you try with e.g.
>
> net use x: \\<server fqdn>\<server share name>
>
> Replace <share fqdn> with fully qualified name of your server (e.g.
> server1.mydomain.com)
>
> or
>
> net use x: \\<server ip address>\<server share name>
>
> Replace x: with free drive letter
> Replace <server ip address> with IP address of server that you are trying
to
> connect to.
>
> Again check DNS and WINS settings on Windows 98 PCs (see if you can
resolve
> host names on Windows 98)...
>
>
> Mike
>
> "Gary Roach" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> >I want a machine running NT client under DOS to be able to connect to
> >shares
> > on a Windows server 2003 machine. I've created a share and given
> > "Everyone"
> > read access. I can connect to this share from windows 98 machines that
are
> > NOT logged on using the server (they're just logged on locally as
"guest"
> > to
> > the workgroup WORKGROUP). however, when i try to do the same thing with
> > the
> > NT client machine (connect as guest, with no password) and then do a:
> >
> > net use * \\<server name>\<server share name>
> >
> > i get an error:
> >
> > error 53: the computer name specified in the network path cannot be
> > located.
> >
> > this same command works fine if i substitute a windows 98 machine name
and
> > share for that 2003 name and share (ie. connect to a 98 share), which
> > tells
> > me the networking is working. i'm using netbeui on all machines and
tcp/ip
> > on the 2003 and 98 machines. also, for some reason, when i take tcp/ip
off
> > one of the 98 machines and attempt a "net" operation with only netbeui,
it
> > tells me i'm not logged on. this works fine with tcp/ip installed.
> >
> > any help is greatly appreciated,
> >
> > gary
> >
> > --
> > Gary Roach
> > ADB Services
> >
> >
>
>

IIUC, NT runs NetBEUI only and all other hosts run both NetBEUI and TCP/IP?
NetBEUI is useless having W2k3 as you've already revealed, and all
communications use TCP/IP anyway.

Microsoft removed NetBEUI from W2k3, where did you get its distro?

you can just add netbeui from the "add protocol" list on server 2003. on xp
you have to get it from the "tools" dir on the CD. i can't use tcp/ip on the
nt client because i don't have an ndis driver for the card i'm using that
supports tcp/ip.

"Jetro" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> IIUC, NT runs NetBEUI only and all other hosts run both NetBEUI and
TCP/IP?
> NetBEUI is useless having W2k3 as you've already revealed, and all
> communications use TCP/IP anyway.
>
> Microsoft removed NetBEUI from W2k3, where did you get its distro?
>
>

Microsoft doesn't ship Windows 2003 with NetBEUI and doesn't support the
protocol in the OS. You can add it using XP disk, but...
Install IPX/SPX at least instead of NetBEUI.

I tried installing NetBEUI from the XP CD on an XP machine and on a server
2003 machine and then changing the server 2003 TCP/IP address to another
subnet so I couldn't communicate with it using TCP/IP. the two machines
couldn't see each other. i tried network neighbourhood as well as "net use"
and "net view" commands. I also loaded NWLink IPX/SPX compatible protocol on
both machines and they still can't talk. as far as i can tell, these
protocols are useless. the only application in which i've ever used NWLink
IPX/SPX successfully is over a direct cable connection between two XP
machines.

"Jetro" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Microsoft doesn't ship Windows 2003 with NetBEUI and doesn't support the
> protocol in the OS. You can add it using XP disk, but...
> Install IPX/SPX at least instead of NetBEUI.
>
>

When I used to work in the Novell environment my friends-unixoids and I
haven't discussed the networks - they couldn't get IPX/SPX at all )