Why can some computers use the name for SMB while others need the IP
Collapse
X
-
Comment
-
Re: Why can some computers use the name for SMB while others need the IP
I remember how that used to confuse the hell out of me when I was learning this stuff.
In his case (if I'm understanding correctly) the router is the DNS server. If it were me, the first thing I'd do is ping the hostname of the copier or do a NSLOOKUP. If the hostname isn't being resolved then he can investigate further.Adversity temporarily visits a strong man but stays with the weak for a lifetime.Comment
-
Adversity temporarily visits a strong man but stays with the weak for a lifetime.Comment
-
Re: Why can some computers use the name for SMB while others need the IP
Here's some notes I kept from the networking thread. Adding the IP address of the copier in the host file is kind of a pain in the ass, but it works every time regardless of the DNS server.
EDIT: I recommend this as a last resort because it could cause a problem if/when the copier is removed from the network. That IP address will be permanently resolved to the hostname of the copier until it's deleted from the host file.
resolove hostname 2.JPGLast edited by BillyCarpenter; 02-25-2021, 06:07 AM.Adversity temporarily visits a strong man but stays with the weak for a lifetime.Comment
-
Adversity temporarily visits a strong man but stays with the weak for a lifetime.Comment
-
Re: Why can some computers use the name for SMB while others need the IP
- Launch Terminal
- Type sudo nano /etc/hosts and press Return
- Enter your admin password
nano is command line text editor you might want to try the gui app textedit as it comes with macos as standard.
Make a backup first.Comment
-
Re: Why can some computers use the name for SMB while others need the IP
Hi, it's usually a Workgroup problem. But it could also be Windows with security settings. In other cases, be sure to set "Private Network" and not "Public Network". This allowed me to solve many problems on Windows 10.
If I don't solve it, I will set a static address on the computer if possible.Comment
-
Re: Why can some computers use the name for SMB while others need the IP
EDIT: I recommend this as a last resort because it could cause a problem if/when the copier is removed from the network. That IP address will be permanently resolved to the hostname of the copier until it's deleted from the host file.
I'll try that, thanks. It is an issue I've been dealing with on and off for years. I don't mind deleting the information in the hosts file if the copier is replaced down the road if this works. I'll also to check to see if it is private network.Comment
-
Re: Why can some computers use the name for SMB while others need the IP
If all of the network pre-reqs are configured correctly..
TCP/IP (IP/Subnet/gateway)
DNS server (s)
Domain name (if required)
Your MFP should be able to resolve a host name. You can always try a ping (try both IP and Host Name)..this is using a different protocol to communicate with the remote node, but should verify connectivity.
Add a global DNS server if possible, 8.8.8.8. that ISP provided router may not do either job (router/DNS server) well
Another thing to remember, at least in KM world , Host Names are case sensitive..Your laptop may be able to see suzycomputor1, but the MFP needs to read SuzyComputor1. KMs have the ability to browse back out across the network..This can be a useful tool when you can see 9 out of 10 Host Names, and the customer is blaming the machine because it can't see the 10th. I've been out of the network side team for a little while now, but I absolutely loved a mystery..And nothing put a bigger smile on my face than proof that my machine was working just as it should..EComment
-
Re: Why can some computers use the name for SMB while others need the IP
EDIT: I recommend this as a last resort because it could cause a problem if/when the copier is removed from the network. That IP address will be permanently resolved to the hostname of the copier until it's deleted from the host file.
I'll try that, thanks. It is an issue I've been dealing with on and off for years. I don't mind deleting the information in the hosts file if the copier is replaced down the road if this works. I'll also to check to see if it is private network.
Before you attempt to make an entry in the host file, I highly recommend that you try to get things working as they should be. You haven't demonstrated that you've covered the basics. Before you do anything, do this:
1. Ping the hostname of the copier. Or run NSLOOKUP followed by the IP address of the copier.
To run NSLOOKUP, go to command prompt and type in NSLOOKUP followed by the IP address of the copier. Example: NSLOOKUP 192.168.1.154. It should return with the host name of the copier. If not, DNS is not set up correctly or there's another problem. With a little patience and troubleshooting, you'll find the problem. It's not that difficult.
A lot of good advice has been given in this thread. Make sure network is set to private. Make sure file sharing in on, ect., ect.
Let us know if you can ping the hostname of the copier or the results from NSLOOKUP. First things first. Good luck.Adversity temporarily visits a strong man but stays with the weak for a lifetime.Comment
Comment