Printing by hostname is very very Rare only had one account in thousands of installs at one college.
Best practice ia via ipaddress.
You may wish to be careful as some advise here is from non IT Tech's.
I hear ya, but we want to know all of our options, right?
I even found this bit of information on the Ricoh site about using host files to resolve the printer host name to the IP address.
resolove hostname 2.JPG
Edit: I'm not planning to run out and print to host. Nope. I just want to know how to do it if there's ever a need. And I want to know EVERYthing about it. Or as much as possible. Like I said earlier, I've never gotten in trouble for knowing too much.
Keep this is mind, also. I'm new to all of this so everything new excites me. You'll have to overlook me. lol
Last edited by BillyCarpenter; 11-26-2020 at 11:19 PM.
This goes waaaaay back.
Anyone remember the old color Colorbus Cyclone RIPs?
They were UNIX based (technically Irix) and required an entry in the RIP’s host file of the sending workstation to accept print jobs when printing over IP.
Keep in mind that back then most color printing was coming from Mac workstations, and they would usually use AppleTalk, so IP printing was fairly rare. Micro$oft didn’t include IP printing in Windows 3.x, 95, or 98, only in NT. There was software to add AppleTalk, such as PC MacLAN and COPSTalk. NT supported AppleTalk natively.
I also recall needing to put an entry in the host table of Windows machines for the early Fiery utilities, such as Downloader and Calibrator. I think that went away with Command Workstation.
“I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins
this explains how some viruses and malware can redirect traffic away from malware removal resources online... interesting... all IT knowledge intersects sooner or later...
that being said... 15 years in the field... never seen or heard of it before... I have heard of netbios name issues once in 15 years... but thats about it...
doesn't mean it does not occur... just never had any issues with it...
good info to know though
Sad To Say I Don't Have a Life
I do this stuff on the weekends too
correction... if dhcp is down just do an ipconfig from command line and see if you get a 169.xxx.xxx.xxx address if you do its down... thanks for the correction all...
and below is some command prompt wizardry to check if dns and dhcp servers are up...
to check if dns is working is to ping host name of copier from command line in windows... if all things are connected and settings are good you should get a response... and it should respond with the ip address if it responds with the gibberish thats ipv6 you can force it to do ipv4
below is an example with google.com
ping google.com
Pinging google.com [2607:f8b0:4000:801::200e] with 32 b
Reply from 2607:f8b0:4000:801::200e: time=34ms
Reply from 2607:f8b0:4000:801::200e: time=34ms
Reply from 2607:f8b0:4000:801::200e: time=34ms
Reply from 2607:f8b0:4000:801::200e: time=34ms
Ping statistics for 2607:f8b0:4000:801::200e:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 34ms, Average = 34ms
ping google.com -4
Pinging google.com [172.217.2.238] with 32 bytes of dat
Reply from 172.217.2.238: bytes=32 time=55ms TTL=112
Reply from 172.217.2.238: bytes=32 time=37ms TTL=112
Reply from 172.217.2.238: bytes=32 time=36ms TTL=112
Reply from 172.217.2.238: bytes=32 time=37ms TTL=112
Ping statistics for 172.217.2.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 55ms, Average = 41ms
How to find dhcp server from command prompt in windows...
ipconfig /all | find /i "DHCP Server"
DHCP Server . . . . . . . . . . . : 192.168.1.254
How to check from command prompt that dhcp server is working
ping 192.168.1.254
Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=74ms TTL=64
Reply from 192.168.1.254: bytes=32 time=6ms TTL=64
Reply from 192.168.1.254: bytes=32 time=6ms TTL=64
Reply from 192.168.1.254: bytes=32 time=6ms TTL=64
Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 74ms, Average = 23ms
How to see what servers are running in windows or at the least are configured for the nic card either automatically or hard wired as a setting
ipconfig /all | find /i "Server"
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Last edited by n25an; 11-27-2020 at 02:57 PM.
Sad To Say I Don't Have a Life
I do this stuff on the weekends too
That's good stuff to know and it works. See below:
dhcp server.JPG
The only way it can resolve a hostname is through DNS not DHCP.
Bookmarks