Mapping to a network share

Greetings.

My network boot diskette fails to map a drive from the original server to a
network share residing on a target server. The network share on the target
server is volume F which holds many files.

From the command prompt on the original server, I performed the following
commands.
1. Running ping 64.69.53.99 was successful.
2. Running tracert 64.69.53.99 was successful.
3. Mapping to the volume failed.
net use f: \\64.69.53.99\f$
Mapping produced the message, "network path not found."

From the command prompt on my workstation, I performed the following commands.
1. Running ping 64.69.53.99 was successful.
2. Running tracert 64.69.53.99 was successful.
3. Mapping to the volume was successful.
net use f: \\64.69.53.99\f$
The mapping prompted me for a username and password. Authentication worked
and I mapped to volume F.

The static IP address on the diskette resides within the same subnet of the
target server.
Network boot diskette
IP = 64.69.53.112
NETMASK = 255.255.255.240
GATEWAY = 64.69.53.97

Target server
IP = 64.69.53.99
NETMASK = 255.255.255.240
GATEWAY = 64.69.53.97

I do not know the origin of the problem. Is there something missing?

Thanks, Mark

If computers are connected to workgroup use identical usernames with
identical passwords on all computers to connect that share.


"Mark S" <(E-Mail Removed)> wrote in message
news:46E73B71-7B12-4BD6-9D1D-(E-Mail Removed)...
> Greetings.
>
> My network boot diskette fails to map a drive from the original server to
> a
> network share residing on a target server. The network share on the target
> server is volume F which holds many files.
>
> From the command prompt on the original server, I performed the following
> commands.
> 1. Running ping 64.69.53.99 was successful.
> 2. Running tracert 64.69.53.99 was successful.
> 3. Mapping to the volume failed.
> net use f: \\64.69.53.99\f$
> Mapping produced the message, "network path not found."
>
> From the command prompt on my workstation, I performed the following
> commands.
> 1. Running ping 64.69.53.99 was successful.
> 2. Running tracert 64.69.53.99 was successful.
> 3. Mapping to the volume was successful.
> net use f: \\64.69.53.99\f$
> The mapping prompted me for a username and password. Authentication worked
> and I mapped to volume F.
>
> The static IP address on the diskette resides within the same subnet of
> the
> target server.
> Network boot diskette
> IP = 64.69.53.112
> NETMASK = 255.255.255.240
> GATEWAY = 64.69.53.97
>
> Target server
> IP = 64.69.53.99
> NETMASK = 255.255.255.240
> GATEWAY = 64.69.53.97
>
> I do not know the origin of the problem. Is there something missing?
>
> Thanks, Mark

Hello, Simas.

Thank you again for the feedback. The original server and target server do
not reside in a workgroup.

My network boot disk holds an autoexec.bat file. Autoexec.bat has a line
which maps a network drive to the administrative share, volume F. The last
item in the line is the password to the administrative share.

net use f: \\64.69.53.99\f$ password

Should the original server and target server reside in the same workgroup?

Thank you, Mark

"Simas Kvilius" wrote:

> If computers are connected to workgroup use identical usernames with
> identical passwords on all computers to connect that share.
>
>
> "Mark S" <(E-Mail Removed)> wrote in message
> news:46E73B71-7B12-4BD6-9D1D-(E-Mail Removed)...
> > Greetings.
> >
> > My network boot diskette fails to map a drive from the original server to
> > a
> > network share residing on a target server. The network share on the target
> > server is volume F which holds many files.
> >
> > From the command prompt on the original server, I performed the following
> > commands.
> > 1. Running ping 64.69.53.99 was successful.
> > 2. Running tracert 64.69.53.99 was successful.
> > 3. Mapping to the volume failed.
> > net use f: \\64.69.53.99\f$
> > Mapping produced the message, "network path not found."
> >
> > From the command prompt on my workstation, I performed the following
> > commands.
> > 1. Running ping 64.69.53.99 was successful.
> > 2. Running tracert 64.69.53.99 was successful.
> > 3. Mapping to the volume was successful.
> > net use f: \\64.69.53.99\f$
> > The mapping prompted me for a username and password. Authentication worked
> > and I mapped to volume F.
> >
> > The static IP address on the diskette resides within the same subnet of
> > the
> > target server.
> > Network boot diskette
> > IP = 64.69.53.112
> > NETMASK = 255.255.255.240
> > GATEWAY = 64.69.53.97
> >
> > Target server
> > IP = 64.69.53.99
> > NETMASK = 255.255.255.240
> > GATEWAY = 64.69.53.97
> >
> > I do not know the origin of the problem. Is there something missing?
> >
> > Thanks, Mark
>
>
>

read more here: http://www.chicagotech.net/workgroupnet.htm

"Mark S" <(E-Mail Removed)> wrote in message
news:29DAA3EE-315E-41F2-91F8-(E-Mail Removed)...
> Hello, Simas.
>
> Thank you again for the feedback. The original server and target server do
> not reside in a workgroup.
>
> My network boot disk holds an autoexec.bat file. Autoexec.bat has a line
> which maps a network drive to the administrative share, volume F. The last
> item in the line is the password to the administrative share.
>
> net use f: \\64.69.53.99\f$ password
>
> Should the original server and target server reside in the same workgroup?
>
> Thank you, Mark
>
> "Simas Kvilius" wrote:
>
>> If computers are connected to workgroup use identical usernames with
>> identical passwords on all computers to connect that share.
>>
>>
>> "Mark S" <(E-Mail Removed)> wrote in message
>> news:46E73B71-7B12-4BD6-9D1D-(E-Mail Removed)...
>> > Greetings.
>> >
>> > My network boot diskette fails to map a drive from the original server
>> > to
>> > a
>> > network share residing on a target server. The network share on the
>> > target
>> > server is volume F which holds many files.
>> >
>> > From the command prompt on the original server, I performed the
>> > following
>> > commands.
>> > 1. Running ping 64.69.53.99 was successful.
>> > 2. Running tracert 64.69.53.99 was successful.
>> > 3. Mapping to the volume failed.
>> > net use f: \\64.69.53.99\f$
>> > Mapping produced the message, "network path not found."
>> >
>> > From the command prompt on my workstation, I performed the following
>> > commands.
>> > 1. Running ping 64.69.53.99 was successful.
>> > 2. Running tracert 64.69.53.99 was successful.
>> > 3. Mapping to the volume was successful.
>> > net use f: \\64.69.53.99\f$
>> > The mapping prompted me for a username and password. Authentication
>> > worked
>> > and I mapped to volume F.
>> >
>> > The static IP address on the diskette resides within the same subnet of
>> > the
>> > target server.
>> > Network boot diskette
>> > IP = 64.69.53.112
>> > NETMASK = 255.255.255.240
>> > GATEWAY = 64.69.53.97
>> >
>> > Target server
>> > IP = 64.69.53.99
>> > NETMASK = 255.255.255.240
>> > GATEWAY = 64.69.53.97
>> >
>> > I do not know the origin of the problem. Is there something missing?
>> >
>> > Thanks, Mark
>>
>>
>>