I thought about this and you're right. I do plan to learn wireshark but at this point in the process, I don't want to put the cart before the horse. There are other things I need to learn at this time. Honestly, I question how much of a need I'll ever have for wireshark. To this point, we've never had to use it.
I want to learn how to do this because I can see where it would come in handy but I'm having a hard time grasping how this is gonna work for a copier. I get that a DNS server ties an IP address to a webpage but how does it tie a copier IP address to the copier hostname?
I see nothing on youtube about it.
How do I set this up?
Okay, I'm gonna take a wild guess here and say that the client is gonna need a DNS server and that an entry will need to be made for the copier IP address. Am I right?
It was authentication that wasn't failing, but instead of being almost instantaneous, it would take about 35-40 seconds, far too long for a user to stand and wait. (Also, please realize that this was in a large law office, so...)
The customer's IT manager never did give me a clear explanation as to what happened to the faulty DNS server. I think he was afraid to admit that he messed up somewhere.
GlobalScan would try to respond to the MFP using its hostname first, then after trying about 30 seconds, fall back to its IP address.
Another simple fix (although not the best) would have been to put entries for the MFPs in the GlobalScan server's host table.
I also have a hunch that setting the MFPs to get all addressing, including DNS, via DHCP would have also worked, then set up reservations for the copiers in DHCP. That would also explain why the workstations had no issues, as they were all DHCP.
BTW...The easy test (which I thought of far too late) was to ping an MFP by its IP address with the -a switch, which will show its hostname; that test would pass. Pinging it using the hostname would fail, indicating a DNS issue. That test is one that is also commonly used when you can't access a website.
“I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins
“I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins
Apart from the situation I described I doubt you will ever need wireshark at work and the fact in captures packets and unencrypted passwords means its a bit of a liability.
However for someone with an interest in networking you can install it and see the various packets floating around their home network after you have seen a few video's on the various types you will know why the device is doing it and for what reason.
When you think you have made a procedure idiot proof your company employs a better idiot.
Your ISP is most likely providing the DNS. A few routers can provide it, but very few.
Run ipconfig / all from a PC and it will show the DNS servers in use. You plug those into the MFP, or have DNS do it for you. If the DNS is your router, the router is most likely just passing the information to the PC. If you have access (and permission), check the configuration on the web page of your router; it will be an address outside your organization.
If you have a server to play with (ideally a VM) you can set up DNS services on it to play with, but don't KEEP IT OFF your production network.
I found this video on DNS (amidst hundreds of others)which is quite informitive (albeit a bit dry):
DNS Essentials - Understanding & Working With DNS - YouTube
“I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins
Keep in mind, Wireshark is for last resort advanced troubleshooting. I have used it to prove that the problem isn't the copier but the environment. It sees every packet across the network including passwords and other critical information. Using a simple hex converter, you can decipher passwords or other information that company does NOT want you to have! Definitely a last resort for me.
Bookmarks