System error 53 - computer name specified in the network path cannotbe found

B

BertieBigBollox

Got laptop which boots from windows 95 into DOS. Loads network
drivers
etc. IP address is 10.1.99.7 (255.255.255.192) and gateway is
10.1.99.10.
10.1.99.10 is windows 2000 server with shares on.

From laptop 10.1.99.7 (255.255.255.192) I can ping 10.1.99.10.


However, if I do :-
NET USE \\PXE-SERVER\SHARE1
or NET USE \\10.1.99.10\SHARE1


I get ERROR 53-Computer name specified in the network path cannot be
found.


How can this be? I've specified an IP address?
 

My Computer

D

Desk Rabbit

Re: System error 53 - computer name specified in the network pathcannot be found

On 15/01/2010 14:34, [email protected] wrote:

> Got laptop which boots from windows 95 into DOS.
That's a clever trick! How do you do that then?

> Loads network
> drivers
> etc. IP address is 10.1.99.7 (255.255.255.192) and gateway is
> 10.1.99.10.
> 10.1.99.10 is windows 2000 server with shares on.
>
> From laptop 10.1.99.7 (255.255.255.192) I can ping 10.1.99.10.
>
>
> However, if I do :-
> NET USE \\PXE-SERVER\SHARE1
> or NET USE \\10.1.99.10\SHARE1
>
>
> I get ERROR 53-Computer name specified in the network path cannot be
> found.
>
>
> How can this be? I've specified an IP address?
>
>

Try adding a username and password to the command.

net use /? will give you guidance.



Also telling us exactly what you are trying to do and why with these
antique operating systems might yield some different answers to your
problem.
 

My Computer

P

Pegasus [MVP]

Re: System error 53 - computer name specified in the network path cannot be found

"[email protected]" <[email protected]> said this in news
item
news:[email protected]

> Got laptop which boots from windows 95 into DOS. Loads network
> drivers
> etc. IP address is 10.1.99.7 (255.255.255.192) and gateway is
> 10.1.99.10.
> 10.1.99.10 is windows 2000 server with shares on.
>
> From laptop 10.1.99.7 (255.255.255.192) I can ping 10.1.99.10.
>
>
> However, if I do :-
> NET USE \\PXE-SERVER\SHARE1
> or NET USE \\10.1.99.10\SHARE1
>
>
> I get ERROR 53-Computer name specified in the network path cannot be
> found.
>
>
> How can this be? I've specified an IP address?

Have a look at your similar post in the Win2000 newsgroup. I gave you some
background about this phenomenon.
 

My Computer

B

BertieBigBollox

Re: System error 53 - computer name specified in the network pathcannot be found

On Jan 15, 3:15 pm, Desk Rabbit <[email protected]> wrote:

> On 15/01/2010 14:34, [email protected] wrote:> Got laptop which boots from windows 95 into DOS.
>
> That's a clever trick! How do you do that then?
>
>
>
>
>

> > Loads network
> > drivers
> > etc. IP address is 10.1.99.7 (255.255.255.192) and gateway is
> > 10.1.99.10.
> > 10.1.99.10 is windows 2000 server with shares on.
>

> >  From laptop 10.1.99.7 (255.255.255.192) I can ping 10.1.99.10.
>

> > However, if I do :-
> > NET USE \\PXE-SERVER\SHARE1
> > or NET USE \\10.1.99.10\SHARE1
>

> > I get ERROR 53-Computer name specified in the network path cannot be
> > found.
>

> > How can this be? I've specified an IP address?
>
> Try adding a username and password to the command.
>
> net use /? will give you guidance.
>
> Also telling us exactly what you are trying to do and why with these
> antique operating systems might yield some different answers to your
> problem.- Hide quoted text -
>
> - Show quoted text -

Sorry - to be more clear.

Booting a laptop from a floppy so that I can map a share on a windows
2000 server. Then I can run ghost and perform a ghost backup of laptop
in question. Server is a domain controller.

Unfortunately, laptop does not support network boot.

Its a legacy system so we have to use windows 2000 - dont ask !!! :-)

This used to work ok. We 'ported' to a new server hardware with
different ethernet cards and now it doesnt work. Dont know why because
server setup should be identical.
 

My Computer

P

Pegasus [MVP]

Re: System error 53 - computer name specified in the network path cannot be found

"[email protected]" <[email protected]> said this in news
item
news:[email protected]

> On Jan 15, 3:15 pm, Desk Rabbit <[email protected]> wrote:

>> On 15/01/2010 14:34, [email protected] wrote:> Got laptop which
>> boots from windows 95 into DOS.
>>
>> That's a clever trick! How do you do that then?
>>
>>
>>
>>
>>

>> > Loads network
>> > drivers
>> > etc. IP address is 10.1.99.7 (255.255.255.192) and gateway is
>> > 10.1.99.10.
>> > 10.1.99.10 is windows 2000 server with shares on.
>>

>> > From laptop 10.1.99.7 (255.255.255.192) I can ping 10.1.99.10.
>>

>> > However, if I do :-
>> > NET USE \\PXE-SERVER\SHARE1
>> > or NET USE \\10.1.99.10\SHARE1
>>

>> > I get ERROR 53-Computer name specified in the network path cannot be
>> > found.
>>

>> > How can this be? I've specified an IP address?
>>
>> Try adding a username and password to the command.
>>
>> net use /? will give you guidance.
>>
>> Also telling us exactly what you are trying to do and why with these
>> antique operating systems might yield some different answers to your
>> problem.- Hide quoted text -
>>
>> - Show quoted text -
>
> Sorry - to be more clear.
>
> Booting a laptop from a floppy so that I can map a share on a windows
> 2000 server. Then I can run ghost and perform a ghost backup of laptop
> in question. Server is a domain controller.
>
> Unfortunately, laptop does not support network boot.
>
> Its a legacy system so we have to use windows 2000 - dont ask !!! :-)
>
> This used to work ok. We 'ported' to a new server hardware with
> different ethernet cards and now it doesnt work. Dont know why because
> server setup should be identical.

Perhaps you're using the wrong tool for your ghosting operation, which makes
life difficult for you. Some imaging tools (e.,g. Acronis TrueImage) will
run while Windows is up and running, thus permitting you to store the image
file on a share that you can access with the standard Windows networking
tools. Note also that spending a lot of time on setting up a DOS boot
diskette might be a wasted effort: These days most if not all new machines
come with SATA disks. I am not aware of a DOS driver for a SATA disk, so
even if you succeed with your current IDE disks, you will have to start all
over again within a few months.
 

My Computer

B

BertieBigBollox

Re: System error 53 - computer name specified in the network pathcannot be found

Had Netbios over TCP/IP enabled before.

However, just installed Netbeui on server and set client to run
netbeui and it now works?

Weird. Is it possible the new server ethernet card just doesnt like
netbios over tcpip?
 

My Computer

J

John Holmes

Re: System error 53 - computer name specified in the network pathcannot be found

Desk Rabbit "contributed" in 24hoursupport.helpdesk:

>> Got laptop which boots from windows 95 into DOS.
> That's a clever trick! How do you do that then?
>

By editing the msdos.sys file and add:

bootgui=0

--
<snip>
 

My Computer

B

BertieBigBollox

Re: System error 53 - computer name specified in the network pathcannot be found

On Jan 15, 4:30 pm, "Pegasus [MVP]" <[email protected]> wrote:

> "[email protected]" <[email protected]> said this in news
> itemnews:[email protected]
>
>
>
>
>

> > On Jan 15, 3:15 pm, Desk Rabbit <[email protected]> wrote:

> >> On 15/01/2010 14:34, [email protected] wrote:> Got laptop which
> >> boots from windows 95 into DOS.
>

> >> That's a clever trick! How do you do that then?
>

> >> > Loads network
> >> > drivers
> >> > etc. IP address is 10.1.99.7 (255.255.255.192) and gateway is
> >> > 10.1.99.10.
> >> > 10.1.99.10 is windows 2000 server with shares on.
>

> >> >  From laptop 10.1.99.7 (255.255.255.192) I can ping 10.1.99.10.
>

> >> > However, if I do :-
> >> > NET USE \\PXE-SERVER\SHARE1
> >> > or NET USE \\10.1.99.10\SHARE1
>

> >> > I get ERROR 53-Computer name specified in the network path cannot be
> >> > found.
>

> >> > How can this be? I've specified an IP address?
>

> >> Try adding a username and password to the command.
>

> >> net use /? will give you guidance.
>

> >> Also telling us exactly what you are trying to do and why with these
> >> antique operating systems might yield some different answers to your
> >> problem.- Hide quoted text -
>

> >> - Show quoted text -
>

> > Sorry - to be more clear.
>

> > Booting a laptop from a floppy so that I can map a share on a windows
> > 2000 server. Then I can run ghost and perform a ghost backup of laptop
> > in question. Server is a domain controller.
>

> > Unfortunately, laptop does not support network boot.
>

> > Its a legacy system so we have to use windows 2000 - dont ask !!! :-)
>

> > This used to work ok. We 'ported' to a new server hardware with
> > different ethernet cards and now it doesnt work. Dont know why because
> > server setup should be identical.
>
> Perhaps you're using the wrong tool for your ghosting operation, which makes
> life difficult for you.  Some imaging tools (e.,g. Acronis TrueImage) will
> run while Windows is up and running, thus permitting you to store the image
> file on a share that you can access with the standard Windows networking
> tools. Note also that spending a lot of time on setting up a DOS boot
> diskette might be a wasted effort: These days most if not all new machines
> come with SATA disks. I am not aware of a DOS driver for a SATA disk, so
> even if you succeed with your current IDE disks, you will have to start all
> over again within a few months.- Hide quoted text -
>
> - Show quoted text -

Like I said its a Legacy system. Uses a bank of single card PCs in a
chassis which is then deployed in a mobile setting. They;ve all got
onboard IDE.
 

My Computer

Top