NT RemoteBoot Client

I have diskles workstation (no hard drive, nor floppy disk ) I only got a BootRom on my NIC card. I want my workstation can have a MS DOS ( just exactly like Netware do with his remote boot program)from NT server. But I can't find it NT REmote Boot Manager only supoort win95, not support bootrom from zerro! How I can configure my NT server, so that My diskless workstation can have a MS-Dos ??
LVL 1
blankzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TooKoolKrisCommented:
I'm having a hard time understanding your question. Are you wanting your NT workstations to be able to be remotly rebooted and start up in DOS?
0
blankzAuthor Commented:
Adjusted points to 500
0
blankzAuthor Commented:
oh. sorry, I mean I have a PC, (not NT Workstation and totaly diskless), and I want it to be booted remotely to MS Dos. And I want to set up My NT server to be Remote Boot Server.

I have installed Remoteboot service on Nt server, DLC and NetBios installed on my NT server. But I cant boot my PC to MS dos. How I can boot my Diskless PC to MS Dos ?  ( with NT server as remoteboot server of course )
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

hiandrasCommented:
How to Configure DOS for Remoteboot In Windows NT 4.0
PSS ID Number: Q158277
 
SUMMARY
=======
 
This article covers the steps required to install and configure Microsoft DOS on
a Windows NT 4.0 Remoteboot server. This article assumes you are using MS-DOS
version 6.22 in all examples.
 
MORE INFORMATION
================
 
Installing DOS
--------------
 
1. Verify that the Winnt\Rpl\Rplfiles directory is being shared on the
   remoteboot server with a share name of Rplfiles. If your system does not have
   this share, then you either have not installed remoteboot properly or have
   stopped sharing this directory. To resolve this problem, stop and restart the
   Remoteboot Server service. After the service has restarted, the Rplfiles
   share should be recreated. If the share fails to create, your remoteboot
   service is not operating properly, and you must remove and reinstall the
   Remoteboot service.
 
2. From an MS-DOS client (running the version of MS-DOS you want to support on
   the Remoteboot server), log on to the network as Administrator and connect to
   the Remoteboot server's Rplfiles share by typing:
 
   net use M: \\NTSERVER\RPLFILES
 
   where NTSERVER is the name of the Remoteboot server.
 
3. Copy all the MS-DOS files to the M:\Binfiles\Dosxxx directory by typing the
   following commands. You will need to replace the xxx with the appropriate DOS
   version (eg. DOS622 for DOS version 6.22).
 
   COPY C:\DOS\*.* M:\BINFILES\DOS622
   ATTRIB -S -H C:\IO.SYS
   COPY C:\IO.SYS M:\BINFILES\DOS622
   ATTRIB +S +H C:\IO.SYS
   ATTRIB -S - H C:\MSDOS.SYS
   COPY C:\MSDOS.SYS M:\BINFILES\DOS622
   ATTRIB +S +H C:\MSDOS.SYS
 
   The files Msdos.sys and Io.sys must have the hidden and system attributes
   removed prior to copying them to the server. Once the copy has been
   completed, remember to reset the hidden and system attributes on the client
   computer (not on the Remoteboot server) for the DOS system to boot properly.
 
   NOTE: The hidden and system attributes should not be set on the Remoteboot
   server. If these attributes are set, then the DOS Remoteboot client will not
   boot properly and will display an error:
 
   Non-System Disk error or disk error
 
4. If you copied DOS files other than MS-DOS, you must rename the input/output
   system file to Io.sys and the Disk Operating System to Msdos.sys. The
   following example is based on IBM's PC-DOS.
 
   Rename Ibmdos.com Msdos.sys
   Rename Ibmbio.com Io.sys
 
Please note that the remoteboot service is designed to support Microsoft DOS.
 
Activating the DOS Version
--------------------------
 
1. From the Windows NT remoteboot server, start the Remoteboot Manager.
 
2. Select Configure from the menu bar, and then click Check Configurations. This
   will check the remoteboot system for all available operating systems and make
   them available for the clients.
 
Creating a Remoteboot DOS Client Profile
----------------------------------------
 
1. From the Windows NT Remoteboot server, start Remoteboot Manager.
 
2. Select Remoteboot from the menu bar, and then click New Profile.
 
3. When the New Profile dialog box appears:
 
   Type a Profile Name: MSDOS622
 
   Select the Configuration: DOS 6.22 3Com Etherlink II
 
   For the Description: Type any descriptive comments
 
   NOTE: Any comments typed prior to selecting a configuration or changing a
   configuration will be over-written with default comments.
 
4. Click OK to save the new profile.
 
Assigning a Profile to a Remoteboot Client
------------------------------------------
 
1. Connect the Remoteboot client to the network, and power the system on. The
   client should start searching for the Remoteboot server. The retries counter
   should increase at a steady pace.
 
2. From the Windows NT Remoteboot server, start Remoteboot Manager.
 
3. Select the workstation name corresponding to the client's media access
   control address. The client will have registered its address automatically
   with the server.
 
   The media access controll address is a unique 12-digit hexadecimal number
   supplied by network adapter firmware. This ID identifies the adapter type and
   manufacturer using the first six digits. If this number is not displayed in
   Remoteboot Manager, press the F5 key. If you still do not see this number, it
   is possible that you have not installed Remoteboot Manager properly, that the
   DLC protocol is not installed, or that your client and server are separated
   by a router that is not forwarding DLC packets.
 
4. Select Remoteboot from the menu bar, and then click Convert Adapters.
 
5. When the Convert Adapters dialog box appears:
 
    - Type a workstation name for the client.
 
    - Type a detail description for the client computer.
 
    - Type a password if desired. A blank or Null password allows the Remoteboot
      client to connect to the RPL server without any operator intervention
      after the power is turned on.
 
    - Select the Configuration type:
 
   Shared: the client can share its profile with other clients
   Personal: the must have it own unique profile
 
    - Select the desired Workstation Profile
 
    - Select TCP/IP DHCP / TCP/IP SETTINGS. If you select TCP/IP settings,
      consult your network administrator for proper configuration.
 
      NOTE: If you are not using TCP/IP, then select the TCP/IP DHCP option.
 
6. Click ADD. The Remoteboot system will then create a user account for the
   computer, and the Remoteboot client will continue the startup process using
   the assigned profile.
 
This completes the installation of MS-DOS on a Remoteboot client.
 
For more information on Remoteboot, see the Windows NT 4.0 Resource Kit.
Specifically, refer to the Server Networking Guide Help File.

#######################################
 
How to Install Remoteboot on Windows NT 4.0
PSS ID Number: Q158454

SUMMARY
=======
 
This article describes the steps required to install the Remoteboot service on a
Windows NT 4.0 Server.
 
MORE INFORMATION
================
 
Requirements: Access to a Windows NT 4.0 Server compact disc.
 
Installing The Remoteboot Service
---------------------------------
 
1. Install the NetBEUI and DLC protocols on the server. These protocols are
   required to run the Remoteboot service.

2. From the Start menu select Settings and then Control Panel.
 
3. Once the Control Panel appears, click the Network icon.
 
4. In the Network Setting dialog box, choose the Services tab and then select
   the Add button.
 
5. In the Select Network Service dialog box, choose the Remoteboot Service.
 
6. In the Remoteboot Setup dialog box, enter the complete path and directory
   name where the remoteboot directory is to be installed. By default this
   directory is <Systemroot>\RPL.
 
7. Click OK.
 
8. Complete the dialog boxes that appear.
 
9. Once you have completed the install of the Remoteboot service, you will need
   to start Remoteboot Manager.
 
10. From the Menu bar, choose Configure and then Fix Security. The Fix Security
   process will create the RPLUSER local group and also assign the proper
   permissions throughout the RPL directory.

I hope these ones helped, tell me if you have any further question.
0
blankzAuthor Commented:
6. Click ADD. The Remoteboot system will then create a user account for the
   computer, and the Remoteboot client will continue the startup process using
   the assigned profile.
-------------------------------------

I use Intel Exther Express Pro 10, I use profile :   DOS 6.22 Intel ExtherExpress PRO, but when I click add an error message stating : "You have specified a profile which is not compatible with adapter for this workstation", then I try using all profiles type, but still got the same error...

I have double check everything else..  like rplprofiles, share name, setting, etc... not help!

Needs further assistance..
0
blankzAuthor Commented:
and Even I use New Workstation, it appear message : "Choosen Profile is not compatible with this workstation" what the hell is this mean ?? is NT is GOD that know a workstation form its MAC address ????
0
blankzAuthor Commented:
Adjusted points to 1000
0
blankzAuthor Commented:
Sorry I have to reject the answer so that another person can answer it if they can.... I need answer badly.. I give all this point to whomaever can solve this...
0
blankzAuthor Commented:
an another information.. I use Sevice Pack 6 alpha (lattest one).
0
linuzCommented:
Does your network card support PXE? If so, you can try installing a PXE service for NT server. Then you can boot MS-DOS by creating a bootable floppy image. Let me know if you need additional details.
0
blankzAuthor Commented:
What is PXE ? My PC bootprom has already NDIS and ODI installed. I just choose NDIS for remote boot. I have try to connect to Netware with ODI and it successfully login to Netware without any problem. So I think the problem is the remoteboot service on NT. Well I'll try PXE, ffrom where I got this software ?
0
linuzCommented:
You can get it from Intel: http://developer.intel.com/ial/wfm/tools/pxepdk20/index.htm Make sure your card supports it though, otherwise it won't work.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bbaoIT ConsultantCommented:
Problem solved?
0
blankzAuthor Commented:
not yet.. in progress of trying... coz the pxe source from intel is for FastEthernet. Still looking for 10Mbps Intel EtherExpress Pro.
0
hiandrasCommented:
Can you try it with another card?
An old NE2000 compatible for start?
0
linuzCommented:
Ignore the fact that PXE has sample ROM for FatsEthernet. As long as YOUR card supports PXE, you should be able to get it to work by installing PXE service from the PDK.
0
kloverCommented:
Forget the Boot from ROM...
You should be able to create a boot floppy with all of the DOS drivers necessary to get your workstations connected to the network.  NT will even make the disk for you.  Use the Network Client Administrator under Start > Program Files > Admin Tools.  I think it even supports your LAN card.  If not you can fake it by creating a disk from a similar card and editing the files and copying the appropriate NDIS DOS drivers to the diskette.  

This is normally used to get a blank workstation up on the network long enough to install an operating system to the workstation, but works just as well for hard-diskless access to LAN.  
0
kloverCommented:
Sorry, just reread your question and noticed that you have no floppy.  A thousand apologies...
0
blankzAuthor Commented:
So the conclution is if My NIC is not surpport PXE, It won't boot to NTRemoteBoot server right ? :)
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.