Thanks: 
Likes: I have some customers with older machines that I use FTP. A have a handful that I can use the hostname but most is IP. I'll use these recommendations to hopefully resolve this as well.
Dislikes: 0
I have some customers with older machines that I use FTP. A have a handful that I can use the hostname but most is IP. I'll use these recommendations to hopefully resolve this as well.
One huge problem with trying to edit the computer's hosts file. It does nothing to help the copier find the computer. Now if there is a hosts file on the copier and if you can edit it.....Originally Posted by adecanmin
You're right. It's not gonna do a thing to help the copier find the PC. From my understanding, he's having no problem with communication between the PC and copier as long as he's using the IP address. The problem is when he tries to use the hostname that he loses communication.
If I remember correctly, and I think I do, when an entry is made in the host file for the PC with the copier's IP address, the PC will look there first before trying to look at DNS cache or router.
The problem with that is, if the host name is ever changed, the PC will still link that IP address to the old host name. I did this by accident when I was playing around with it.
Another problem is when the network itself is changed. I have had instances where the customer has changed their ISP or had to replace cable/dsl modem. If they are using the modem for DHCP then the entire local network can change. Like from 192.168.1.xxx to maybe 192.168.3.xxx or maybe even to a different class of network.
Wrong information as ALWAYS
Basic networking
Hostname Resolution refers to the process through which an assigned hostname is converted or resolved to its mapped IP Address so that networked hosts can communicate with each other.
And in the case of scan to SMB is accomplished through DNS
External DNS will do nothing to help resolve local network host names
Sent from my Pixel 4 XL using Tapatalk
This is true. External DNS deals with the internet. A local DNS resolver has to do the the Intranet.
I went to a c3850 the other day I could not get it to scan smb 2.0 using the computer name in a workgroup for the longest time. I tried using the name this time and now it works. I did nothing to the computer aside from using the name. I had another that was on a public network and it worked using the computer name. I'm gathering there is no definitive answer as to why some can scan using the name while others need an IP in the same office. I'll keep looking for a solution.
Some times the answer is poor network mgmnt due to a lack of or little care about the network. When Joe from the church is the "network' guy, you can bet he's going to blame the machine. These guys will add equipment, change routers and ISP without any regard to the problems they will induce..Then they expect the copier repair guy to work it out. Sometimes you just want to say..use the scan to usb thumb drive, I'm done with you. E
Reply With Quote
Bookmarks