DHCP + Architecture in a mixed environment

[datadan]

We have a sloppy network.

2 IP subnets in one building.
3 Domains
NT4, Linux7, Novell 5, and W95,98 technology.

Users use Novell for file server, Linux for email and DNS, and NT for applications.

We are currently static, but will be introducing new application software and ~50PCs and I believe it's time to make the move to DHCP.

I am fishing for expertise here on whether I should implement DHCP on a Linux, NT, or Novell basis.

Any advice appreciated.
Thanks,

 

[bcastner]

Is your future direction Novell or Windows for the file server?

Identify your upgrade path, and implement DHCP on that network service.

 

[manarth]

if Linux is the DNS, go with Linux for DHCP...You'll want the IPs bound to the DNS entries.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[bcastner]

I agree with manarth, but be careful as well with the Linux DNS service. If your future upgrade path is towards Windows most Linux DNS servers will fall short of what is expected from a Windows service.

 

[datadan]

We will stay with Novell as a file server.

My concern is the protocol priority. I have been told that that packets are prioritized by technology. For example if I have an NT machnine and a Linux machine. NT will be the first packets read v. the Linux machine.

My NT will hold the DOMAIN for the application server.
All pcs will point to the linux box for DNS info, yet people authenticate for File services and print services on Novell.

Aside from packet priority I am also concerned with ease of use. Is NT easier than Linux. (Although I can navigate through both, I am not a hardcore code guy).

Lastly, I want reliability. From this standpoint I feel Linux has NT beat hands down.

Other thoughts?

Thanks,

 

[bcastner]

Quote:

&quot;We have a sloppy network.

2 IP subnets in one building.
3 Domains
NT4, Linux7, Novell 5, and W95,98 technology.&quot;

All of this is completely outdated. You can update the Linux without cost. You can be certain your NT is up-to-date without cost. You can check to be certain your Novell setting is up-to-date without cost.

It is unclear from your original post whether you are updating application software only, and/or adding an additional 50 workstations.

I am puzzled by the immediate concern with what you describe as &quot;protocol priority.&quot; You could, and should, go completely to TCP/IP. Move your Win95 clients if possible to Win98 or better. You want to eliminate IPX as it is a not-needed component, and a huge bandwidth waster.

If I was on a limited budget I would focus on:

1. All the free updates to the various OS's as possible;
2. Move to TCP/IP
3. You might consider a good hardware router that could provide DHCP service as well as other advantages
4. You might rethink your Linux vs. Windows stability notions
5. Spend some money on the client/workstation side of the shop

 

[datadan]

You are right I do need to upgrade and we will.

We will be most TCP/IP. Clients will be TCP/IP. IPX will need to stay on the network however.

Why might you say Windows is more stable than Linux as a DHCP server? (My NT machines crash far more than my linux machines do.)

Client machines will do very little. They are only used for viewing a particular application. No Word/Excel/Mail/Access functions necessary.

 

[bcastner]

I will try to avoid a Linux vs. Windows argument.

My Win2k and XP clients are rarely every reset.

My Win2k and Windows 2003 servers the same.

My Linux boxes, are mixed, but reliable.

I no longer have Win85 clients, but they did have to be reset often. Win98 clients much less so. Win2k clients and Win XP clients rarely.

I just wanted you to have an open mind. Both Novell and Microsoft offer very strong server products. As does Linux, at least at the 8+ kernel level. I can see using Linux for Web server, but for application server I would use Win2k or Windows 2003, and for regular file/print I would use either Windows or Novell. There is no best solution, but fortunately there are several quite good solutions.

In your position I suspect the biggest bang you could achieve is by updating your clients, both hardware and OS software.

In the middle would be to upgrade Novell, as this is your choice of file/print server.

In between, I would spend some moneys on a decent physical plant, including the interim step with Novell as file/printer server of using good hardware routers.

Best.

 

[datadan]

Thanks for the input.

I will try an NT DHCP setup and test it out. I will now move my further inquires to the NT4.0 list and off this one.

...