Sudden behavior change in Device URL of samba for XP printer
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Sudden behavior change in Device URL of samba for XP printer
Hi. I encountered a very strange and sudden behavior change for my printer connected to Windows XP box. My ubuntu version is 8.04 LTS; samba's version is 3.0.28a-1ubuntu4.9; and cups's version is 1.3.7-1ubuntu3.6. I have been using these samba and cups to print things from my ubuntu boxes to this printer for a long time.
A couple of days ago, all of sudden, it stopped working. My printer jobs were queued but never printed. I checked the Printer Configuration, which says:
Device URL: smb://MSHOME/MYPC/Printer
as before.
Just in case, I changed this URL to the explicit IP address of my XP box at home as follows:
Device URL: smb://192.168.1.4/Printer
Then, it started working again. I do not understand why the previous setting stopped working and I have to put the explicity IP address now.
Since this IP 192.168.1.4 may change depending on the router setting, etc., it is much more convenient to set the Device URL the previous way.
I do not think that I made any change in XP, but I do not know whether some automatic windows update would cause such a behavior change or not.
Any suggestions/help would be greatly appreciated!
BVP
Thanks for your suggestion.
In fact, I just tried it:
$ ping MSHOME
ping: unknown host MSHOME
So, the system doesn't recognize MSHOME.
What should I do to fix this?
As I said, I rebooted both my linux box and XP box, but nothing changed.
Do you really want to use smb://MSHOME/MYPC/Printer?
What is wrong with smb://192.168.1.4/Printer?
Well, nothing is wrong with explicitly setting the IP address, but yet, I have two things I want to say:
(1) Setting with MSHOME was working before, and I want to know why all of sudden it stopped working; and
(2) Depending on the wireless setting, my XP box's IP address changes from 192.168.1.4 because it is connected via wireless.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.