Printers: DHCP vs Static IP 4

[TopRung]

Hello,

not sure if this is the correct Forum for this question, but here it is:

WIndows Server 2000 domain environment runing DHCP and DNS(XP pro clients)>

What is the best practice for setting up network printers?

I ask becausse we recently had a power failure, and all clients were not able to print afterwards. The clients were using a printer NAME rather than the printer IP. I went to each client and used the IP, and that fixed it.

- I am a bit confused.

 

[NetIntruder]

As long as you have DHCP set to always update DNS, you shouldn't have too many issues. Printing to IP addresses can get cumbersome - for network services and applications, it is always preferred to use DNS over IP Address.

Are your printers using DHCP now or are they set to static addresses?

~Intruder~

"The Less You Do, The Less Can Go Wrong"

 

[dennisbbb]

Dedicate a batch of ips for printers. Set them static so they will not change in case of power failure or DNS server has problems.
If you want to track, dedicate a server and install all the printers in the building. Share these printers to users. Track what they print from the event logging.

 

[TopRung]

Well it was using DHCP, but once we had this power failure and no one could print, I went to each client and used the IP.

After the power was back up and all servers/printers were online, i printed the config for the printer. The only difference betweeen this config and the previous config (prior to power failure) was that the host name changed. I wasnt sure what to do at that point, or why it changed, so i used the IP to make sure all clients were printing again.

It just made it seem like using DHCP can be volatile (losing names/pointers).

 

[TopRung]

well, maybe my lack of knowledge on this is giving the wrong impressions.

All I did to get the printers printing again is to go to each printer and "configure port" for the specific printer. Each client had a name for the printer [npf123.domain.int]. I changed that to the IP for the printer.

So, technically, I didnt do anything in DHCP or DNS servers.

maybe someoen can clarify what is going on here. They printed before using the name, but no longer. The only difference i notice when comparing printer config files is the HOSTNAME change - which must have occured when the servers/printers rebooted hours later.

 

[NetIntruder]

You could argue both ways on static vs. dynamic on IP addressing for printers. Smaller companies are fine to use static addressing, but DHCP will be the system of choice for most companies.

Am i assuming correctly by reading the above that you print directly to the printers? (IE you don't spool through a server)?..

~Intruder~

"The Less You Do, The Less Can Go Wrong"

 

[TopRung]

To make sure i didnt answer the question in appropriately, i turned off the "Print Spooler" on the server - It still printed. So, i assume it is not spooling through the server. Spooling is controlled locally (client side) it appears.

 

[NetIntruder]

This is part of your issue then. Try setting up a print queue on your server that points to the printer's hostname. I would still recommend using DHCP to aquire addressing (and to enable DNS Updates on DHCP for all clients) as this will update DNS frequently.

If you need further assistance with "Best Practice" Printer setup, i'm sure we could point you at some good documents on the net as well.

~Intruder~

"The Less You Do, The Less Can Go Wrong"

 

[TopRung]

NetIntruder: the more i look at this, and try to understand, I get a bit more confused.

Wouldn't you assume I am using DHCP? Under the DHCP management (address leases), I see the printer in question. the name it has is 5.domain.int.

I thought i should be able to configure the clients port to use that name, but when i try, it says invalid name.

what am i missing here?

<I ask this to better understand DHCP in order to decide for myself if it is better to use this method>

 

[TopRung]

Okay, think I have determined the cause... DHCP renamed the printer to 5.domain.int.

well the client side printer port dialog doesn't accept that name. It requires a letter first. such as H5.domain.int. Kinda squirrelly. I guess if DHCP had named it properly, all would have been okay.

So, this poses another question. How does DHCP generate these names? They appear to be 9 alpha numeric characters.

 

[ricpinto]

I need info, how's the printer/s connected, directly thru a PC/server or printserver box (HP jetdirect, Intel netport, etc)?

Correct me if I'm wrong but DHCP dish out ip only, hosts name changes was done by you and DNS just records it thru the request of the DHCP client(PC) for dynamic update.

http://support.microsoft.com/default.aspx?scid=kb;en-us;317590#21

 

[ricpinto]

Let me change my statement above to avoid contradictory because I notice itGenerally DHCP dish out ip only (ie NT DHCP), but (win2k) it can also update the DNS on behalf of the request from its client(PC). For static IP the PC just request the update to DNS server. Ok that's better.

 

[NetIntruder]

The DHCP server will update DNS for clients that do not support DNS Updates (IE, printers, etc). Whatever hostname is presented to DHCP at the time of obtaining a lease is what will get propogated into DNS. Once the hostname changes and you power cycle the printer to make the change, this should be reflected in DNS as the printer will check on boot-up to assure that it's IP is still good.

Where does the problem lie here - If you give a printer a hostname of "MyPrinter", what shows up in DHCP for the name and DNS for the name?

~Intruder~

"The Less You Do, The Less Can Go Wrong"

 

[TopRung]

I changed the hostname on the printer, and the DHCP accurately matched. DNS does not match.

There are 3 entries for that IP and each has a different name.

5.domain.int
npica0f1b.doamin.int
npia13a3f.domain.int (this was the name prior to power outage)

 

[NetIntruder]

hmm... you may want to look at your DNS setup. Check first off to see if you have record scavenging turned on. You may want to set this up to filter out the old junk on a regular basis (life of DHCP ticket, etc).

Do you have any oddities in your DNS event logs?

~Intruder~

"The Less You Do, The Less Can Go Wrong"

 

[TopRung]

First off, thank you for passing along your knowledge!

scavenging is not on! I looked at the log file, and there is nothing being logged - All are unchecked. Apparently, those that set this up initially cared less about the right way to do things.

I know nothing about the intricacies, so if you have insight (literature, how-to's, etc.) please show me the light!

Turning on scavenging: any potential side-effects? What period is good practice?

 

[TopRung]

Correction:

We have to Servers running DNS, and only one running both DHCP and DNS.

The one running only DNS, has 4 entries for the IP. THe three mentioned above, and the new hostname "myprinter".

The one runnngin both DNS and DHCP has the three names listed above.

 

[NetIntruder]

Are you using Primary/Secondary DNS or AD Integrated?

Turning on scavenging is a best practice to remove your junk with very little admin overhead. You should not have any ill effects to turning this on.

~Intruder~

"The Less You Do, The Less Can Go Wrong"

 

[candyman200]

For what it's worth, I prefer reserving DHCP if for no other reason but to know what IP is assigned to which printer without either hopping around or pinging a printer name. If your replace a printer all you need to do is change the MAC address in the DHCP table, plug in the new printer and you're up and running in a minute or so as opposed to manually (or via HP WebJet Admin) setting up the printer.

Just my personal preference...

 

[NetIntruder]

I've gone both ways on this one too, Candyman. I have issues where people (techs in other offices, etc) will move a printer to another floor (another VLAN) quite frequently which messes up this philosophy and results in a lot of calls. If your environment does not change often, you could certainly go with DHCP reservations with very little admin overhead.

~Intruder~

"The Less You Do, The Less Can Go Wrong"