Deployment Solution

Hello,

I have installed a new Testenvironment for DS 6.9 SP1.

If I now boot a client from network I get always the message "Unable to map Drive F: the Server could not be found".
The network-boot process works fine until the point where the client try to map drive F

My Test-DC and Test DS works fine. Ping and so on works also fine. DHCP is also ok. During the networkboot the client gets a IP.

Any Idea what the problem could be? Or how I can trace the problem?

Thanks in advance and best regards, Bernd

Sounds like the credentials that you're using to map F: aren't correct. Make sure the user that you specified in your boot disk actually has rights to the eXpress share.

Anthony,

the credentials are ok. If I interrupt the DOS-Bootprocess, I can start and stop the Networtk (net stop, net start)

So, from this side all is ok. Also, I can map the share from another Win-PC with this credentials.

One more Idea?

Regards, Bernd

One possiblity is, that if you are on multiple networks (our servers serve about 50 networks, but are all on one), make sure you have clicked the box to make an lmhosts entry when making the PXE file or boot disk.

Something simple that's easy to miss: if your boot environment is WinPE, it may be picking up removable media readers as additional drive letters, meaning one of the slots in the media reader is drive F:.

Also,
If you have 4 devices (2 hard drives and 2 cd-roms), your F: drive will be unavailable. I always change the drive letter to L: or something lower to leave room for drives, etc.

HTH

Hi all,

thanks a lot for your answers. The problem was the networkconfiguration from the testenvironment. After fixing that all works fine.

For troubleshooting it's much better to boot WinPE on the client than DOS. With WinPE you have much more diag-tools and configuration errors could be found much faster.

Thanks again and regards, Bernd