DHCP assigned addresses for Print Servers

[jodders]

HI all

We have a rather young engineer working for us who has setup around
10-20 printers on a 200-300 node network. Problem is that most of
these are older PC's logging into Netware.

He has decided in his young wisdom to set all the printers to DHCP.
Not a problem I hear you cry. Until you realise that around 150 of
these pcs are still win 95 and do not have any DNS lookup for the
printer.

Is it me or is he an arse

Your

Cisco Engineer

 

[Lanwench [MVP - Exchange]]

In

HI all

We have a rather young engineer working for us who has setup around
10-20 printers on a 200-300 node network. Problem is that most of
these are older PC's logging into Netware.

He has decided in his young wisdom to set all the printers to DHCP.
Not a problem I hear you cry. Until you realise that around 150 of
these pcs are still win 95 and do not have any DNS lookup for the
printer.

Is it me or is he an arse

Your

Cisco Engineer

He might be an arse, but in general there shouldn't be a problem in that DNS
and DHCP aren't the same thing. That said: this could be a problem depending
on how your network is set up to print....are you using a single print
server with shares? Are users having problems printing? Can they ping the
printers by IP? The name doesn't really matter -

I personally use DHCP reservations for printers - heck, for anything other
than servers & network equipment (switches, routers, etc).

Win95 can use WINS, and can also use DNS - so set up DNS to lookup to WINS
on the server. Are you using AD?

OT, but you really need to get those old PCs off your network. Win95 is old
old old old old...it's 2005 now. Also, Win9x has no security whatsoever and
does not belong on a corporate network IMHO. I won't say "ditch NetWare"
because frankly, there's nothing wrong with NetWare - unless you're using,
say, 3.x or somesuch....