Networking Forums

Networking Forums > Computer Networking > Windows Networking > How to setup DOS Client to login to Windows 2000 Domain?

Reply
Thread Tools Display Modes

How to setup DOS Client to login to Windows 2000 Domain?

 
 
Mitesh Patel
Guest
Posts: n/a

 
      12-29-2005, 06:20 PM
Hi,
I have some DOS PCs and right now they are login to Novell. I am planing to
migrate my Novell server to Window 2000 server. So how do I setup DOS PCs so
that they can login to Domain and map all network drives autometically.
Thanks

Mitesh
 
Reply With Quote
 
 
 
 
Ace Fekay [MVP]
Guest
Posts: n/a

 
      12-30-2005, 01:50 AM
In news:05E40705-8F81-41F7-B178-(E-Mail Removed),
Mitesh Patel <(E-Mail Removed)> stated, which I
commented on below:
> Hi,
> I have some DOS PCs and right now they are login to Novell. I am
> planing to migrate my Novell server to Window 2000 server. So how do
> I setup DOS PCs so that they can login to Domain and map all network
> drives autometically. Thanks
>
> Mitesh


Are you familiar with how to make a DOS network bootable diskette? This is a
huge subject by itself and _*numerous*_ books were written on it years ago.
To simplify it, if you still have an NT4 server, you can make a network
bootable diskette. Some links are provided below to show you how. In the
process you would select the NIC type. If it doesn't show up, you can go to
the NIC's manufacturer's site and download the drivers.

You will need to make the DOS PC network bootable. This all depends on what
NIC you have. Once the network software is installed, in the system.ini file
you would specify the domain name. But there's more than that.

If you don't have an NT4 server anymore, the documentation with the NIC
drivers will show you exactly how to make a network bootable diskette,
including what must be in the protocol.ini and system.ini files for their
specific drivers and where to put the drivers and necessary files. Then you
can transfer the files to the DOC PC and merge the autoexec.bat and
config.sys files with the existing ones. That's the way I do it since I had
created my original startup disks with NT4 because now the NICs are
different and EACH manufacturer has their own requirements.

How To Create an MS-DOS Network Startup Disk in Windows 2000 (use NT4 client
creator):
http://support.microsoft.com/?kbid=252448

How to Create a Network Installation Boot Disk (use NT4 client creator):
http://support.microsoft.com/?kbid=142857

Here are more articles with step by steps:

Installing Your Network Clients
http://www.windowsitlibrary.com/Content/315/02/toc.html

DOS Network Boot Floppy:
http://www.windowsnetworking.com/art.../dosclflp.html


And MY FAVORITE! I used Bart's method to create a multi-NIC boot CDROM that
will boot over 43 different network card brands and versions. It's great for
tech support, and many other things. Once you've created the diskette, you
can make a bootable CD out of it. To make a DOS PC bootable, just copy the
files over the machine.
Bart's Boot disks
http://www.nu2.nu/bootdisk/


To map a drive, you would need to add lines to your autoexec.bat. Here's an
example to map the drive letter X: to a share:
net use x: \\servername\sharename

Good luck!

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, if I may suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx, you can easily find your post, track
threads, cross-post, and sort by date, poster's name, watched threads or
subject.

Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================


 
Reply With Quote
 
Mitesh Patel
Guest
Posts: n/a

 
      12-30-2005, 03:50 PM
Thanks Ace,
I did all this, but if my network card driver is not built in with MS Client
(created through NT 4.0) How do I add new drivers to it.

Thanks



"Ace Fekay [MVP]" wrote:

> In news:05E40705-8F81-41F7-B178-(E-Mail Removed),
> Mitesh Patel <(E-Mail Removed)> stated, which I
> commented on below:
> > Hi,
> > I have some DOS PCs and right now they are login to Novell. I am
> > planing to migrate my Novell server to Window 2000 server. So how do
> > I setup DOS PCs so that they can login to Domain and map all network
> > drives autometically. Thanks
> >
> > Mitesh

>
> Are you familiar with how to make a DOS network bootable diskette? This is a
> huge subject by itself and _*numerous*_ books were written on it years ago.
> To simplify it, if you still have an NT4 server, you can make a network
> bootable diskette. Some links are provided below to show you how. In the
> process you would select the NIC type. If it doesn't show up, you can go to
> the NIC's manufacturer's site and download the drivers.
>
> You will need to make the DOS PC network bootable. This all depends on what
> NIC you have. Once the network software is installed, in the system.ini file
> you would specify the domain name. But there's more than that.
>
> If you don't have an NT4 server anymore, the documentation with the NIC
> drivers will show you exactly how to make a network bootable diskette,
> including what must be in the protocol.ini and system.ini files for their
> specific drivers and where to put the drivers and necessary files. Then you
> can transfer the files to the DOC PC and merge the autoexec.bat and
> config.sys files with the existing ones. That's the way I do it since I had
> created my original startup disks with NT4 because now the NICs are
> different and EACH manufacturer has their own requirements.
>
> How To Create an MS-DOS Network Startup Disk in Windows 2000 (use NT4 client
> creator):
> http://support.microsoft.com/?kbid=252448
>
> How to Create a Network Installation Boot Disk (use NT4 client creator):
> http://support.microsoft.com/?kbid=142857
>
> Here are more articles with step by steps:
>
> Installing Your Network Clients
> http://www.windowsitlibrary.com/Content/315/02/toc.html
>
> DOS Network Boot Floppy:
> http://www.windowsnetworking.com/art.../dosclflp.html
>
>
> And MY FAVORITE! I used Bart's method to create a multi-NIC boot CDROM that
> will boot over 43 different network card brands and versions. It's great for
> tech support, and many other things. Once you've created the diskette, you
> can make a bootable CD out of it. To make a DOS PC bootable, just copy the
> files over the machine.
> Bart's Boot disks
> http://www.nu2.nu/bootdisk/
>
>
> To map a drive, you would need to add lines to your autoexec.bat. Here's an
> example to map the drive letter X: to a share:
> net use x: \\servername\sharename
>
> Good luck!
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> If you are having difficulty in reading or finding responses to your post,
> instead of the website you are using, if I may suggest to use OEx (Outlook
> Express or any other newsreader of your choosing), and configure a newsgroup
> account, pointing to news.microsoft.com. This is a direct link into the
> Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
> account with your ISP. With OEx, you can easily find your post, track
> threads, cross-post, and sort by date, poster's name, watched threads or
> subject.
>
> Not sure how? It's easy:
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Assimilation Imminent. Resistance is Futile.
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>

 
Reply With Quote
 
Phillip Windell
Guest
Posts: n/a

 
      12-30-2005, 04:37 PM
The drivers for the Nic should be on the disk(s) that came with it. they
might be listed under a folder called "Novel" or "DOS" or "IPX" most
commonly but could be something else,...you just have to hunt for them.

There are two different kinds of "DOS" drivers for Nic. There is the NDIS
Driver and the Pkt (Packet) Driver. NDIS driver files ended with "*.dos",
Pkt Driver files ended with "*.com". The folders on the disk they are in
might even be NDIS and Pkt respectively.

You can't use both at the same time, they are configured differently and
work differently,...choose one or the other.

Sometimes you can get lucky and a driver will work for more than one card if
the chipset of the Nics are from the same manufacture (like many Netgear are
really Realtech, or was it Realtek?). Since you are only dealing with
minimal functionality the same driver may work for multiple Nics.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Mitesh Patel" <(E-Mail Removed)> wrote in message
news:69D38998-E11D-4B84-9570-(E-Mail Removed)...
> Thanks Ace,
> I did all this, but if my network card driver is not built in with MS

Client
> (created through NT 4.0) How do I add new drivers to it.
>
> Thanks
>
>
>
> "Ace Fekay [MVP]" wrote:
>
> > In news:05E40705-8F81-41F7-B178-(E-Mail Removed),
> > Mitesh Patel <(E-Mail Removed)> stated, which I
> > commented on below:
> > > Hi,
> > > I have some DOS PCs and right now they are login to Novell. I am
> > > planing to migrate my Novell server to Window 2000 server. So how do
> > > I setup DOS PCs so that they can login to Domain and map all network
> > > drives autometically. Thanks
> > >
> > > Mitesh

> >
> > Are you familiar with how to make a DOS network bootable diskette? This

is a
> > huge subject by itself and _*numerous*_ books were written on it years

ago.
> > To simplify it, if you still have an NT4 server, you can make a network
> > bootable diskette. Some links are provided below to show you how. In the
> > process you would select the NIC type. If it doesn't show up, you can go

to
> > the NIC's manufacturer's site and download the drivers.
> >
> > You will need to make the DOS PC network bootable. This all depends on

what
> > NIC you have. Once the network software is installed, in the system.ini

file
> > you would specify the domain name. But there's more than that.
> >
> > If you don't have an NT4 server anymore, the documentation with the NIC
> > drivers will show you exactly how to make a network bootable diskette,
> > including what must be in the protocol.ini and system.ini files for

their
> > specific drivers and where to put the drivers and necessary files. Then

you
> > can transfer the files to the DOC PC and merge the autoexec.bat and
> > config.sys files with the existing ones. That's the way I do it since I

had
> > created my original startup disks with NT4 because now the NICs are
> > different and EACH manufacturer has their own requirements.
> >
> > How To Create an MS-DOS Network Startup Disk in Windows 2000 (use NT4

client
> > creator):
> > http://support.microsoft.com/?kbid=252448
> >
> > How to Create a Network Installation Boot Disk (use NT4 client creator):
> > http://support.microsoft.com/?kbid=142857
> >
> > Here are more articles with step by steps:
> >
> > Installing Your Network Clients
> > http://www.windowsitlibrary.com/Content/315/02/toc.html
> >
> > DOS Network Boot Floppy:
> > http://www.windowsnetworking.com/art.../dosclflp.html
> >
> >
> > And MY FAVORITE! I used Bart's method to create a multi-NIC boot CDROM

that
> > will boot over 43 different network card brands and versions. It's great

for
> > tech support, and many other things. Once you've created the diskette,

you
> > can make a bootable CD out of it. To make a DOS PC bootable, just copy

the
> > files over the machine.
> > Bart's Boot disks
> > http://www.nu2.nu/bootdisk/
> >
> >
> > To map a drive, you would need to add lines to your autoexec.bat. Here's

an
> > example to map the drive letter X: to a share:
> > net use x: \\servername\sharename
> >
> > Good luck!
> >
> > --
> > Ace
> >
> > This posting is provided "AS-IS" with no warranties or guarantees and
> > confers no rights.
> >
> > If you are having difficulty in reading or finding responses to your

post,
> > instead of the website you are using, if I may suggest to use OEx

(Outlook
> > Express or any other newsreader of your choosing), and configure a

newsgroup
> > account, pointing to news.microsoft.com. This is a direct link into the
> > Microsoft Public Newsgroups, and it is FREE and DOES NOT require a

Usenet
> > account with your ISP. With OEx, you can easily find your post, track
> > threads, cross-post, and sort by date, poster's name, watched threads or
> > subject.
> >
> > Not sure how? It's easy:
> > How to Configure OEx for Internet News
> > http://support.microsoft.com/?id=171164
> >
> > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> > Microsoft MVP - Windows Server Directory Services
> > Microsoft Certified Trainer
> > Assimilation Imminent. Resistance is Futile.
> > Infinite Diversities in Infinite Combinations.
> > =================================
> >
> >
> >



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Windows xp takes 7 tries to login to server 2000 Mehbs Windows Networking 3 06-06-2007 09:26 PM
Windows 98 client cannot login to active directory domain Theresa Pallo Windows Networking 1 06-23-2004 12:35 AM
Cannot Join Windows 2000 Client to Windows Server 2003 Domain Nicholas White Windows Networking 1 05-03-2004 01:23 PM
Win 98 client disconnected after login to domain on Windows Server 2003 Janet Windows Networking 0 12-31-2003 02:33 PM
Windows 98 clients not able to login to Windows 2000 domain S Aravind Windows Networking 2 10-04-2003 11:11 AM



1 2 3 4 5 6 7 8 9 10 11