1 Aug 2005 02:25
[SLE] printer loss [susepro 9.1]
Serge Naggar <naggar <at> sprintmail.com>
2005-08-01 00:25:58 GMT
2005-08-01 00:25:58 GMT
Hi, I still have not been able to resolve the print problem I have been having. I believe it is probably a combination of the susepro 9.1 and samba 3.0.9-2.6-suse interactions as the two systems on the lan have had the same problem of losing their printer and then not being able to regenerate them. I tried to access cups via //localhost:631/ with no success. I have tried a number of approaches: upgraded kde to v3.4; taken the unit out of the lan but nothing works so I am hoping somebody out there will have suggestion[s] which will solve the problem. Following is a copy of the /var/log/cups/errorlog: Listening to 0:631 E [31/Jul/2005:18:40:00 -0400] Unknown Location directive # on line 811. I [31/Jul/2005:18:40:00 -0400] Loaded configuration file "/etc/cups/cupsd.conf" I [31/Jul/2005:18:40:00 -0400] Configured for up to 100 clients. I [31/Jul/2005:18:40:00 -0400] Allowing up to 100 client connections per host. I [31/Jul/2005:18:40:00 -0400] Full reload is required. I [31/Jul/2005:18:40:03 -0400] LoadPPDs: Read "/etc/cups/ppds.dat", 3592 PPDs... I [31/Jul/2005:18:40:04 -0400] LoadPPDs: No new or changed PPDs... I [31/Jul/2005:18:40:04 -0400] Full reload complete. E [31/Jul/2005:18:40:04 -0400] StartListening: Unable to bind socket - Address already in use. Can someone tell me what the last line means? It seems to me to have the key? Thanks for your input. -- -- Cheers,(Continue reading)
>..
>Hm...ok...now RUNAS is working (though not exactly as I'd like...but can
>probably figure that out by consulting my books)...
>Seems user <at> domain doesn't work in simple case -- their example shows:
>user <at> domain.microsoft.com. Maybe it needs the dots in the domain name?
the syntax user <at> domain.com is the w2k dns based naming scheme whereas the
domain\user is the old netbios one. both should work but with some
third-party tools which don't understand dns naming.
> Bash.exe (cygwin toolset) is on the local machine. I can now
>start bash, but not "explorer". When I try to start Explorer, I get
>no error message and nothing happens (or starts).
Explorer is a much more funny thing to handle
I got it from m$ support : you just can't run explorer as runas with
another user, officially it conflicts with the desktop explorer instance.
but the following works : open a dos command prompt window, start the task
manager, kill explorer : your desktop disappears. then run explorer from
RSS Feed