Displaying 6 results from an estimated 6 matches for "ktindl".
Did you mean:
kindl
2005 Sep 15
2
Driver for Tripp Lite SmartPro SLT
I have a new SMART1050SLT Tripp Lite UPS that both tripplite
and tripplitesu drivers hate. Both simply time out with a "can't
find" message.
Does anyone know about the SmartPro series?
2006 Feb 08
1
TrippLite SmartPro and 2.0.3
I'm running Ubuntu 5.10, featuring a patched kernel 2.6.12. I have a
Tripp Lite SmartPro SLT ups connected via USB. I have cleanly compiled
and installed the new nut 2.0.3. I do have the "extras", like libusb,
installed too.
I need some USB advice- that is, I'm not sure what a normal baseline
should look like.
At boot, the modules usb_core and uhci_hcd are loaded. dmesg
2004 Feb 26
1
Samba and firewall
Hi Everyone,
I'm new to Samba. I have setup a samba server (Redhat 9) in the internal
LAN and a samba client (Win2k) in the external LAN. There is a firewall
between these two LANs. My problem is I cant see my workgroup in the
client Microsoft Windows Network window. I have open 139, 445 tcp ports
and 137, 138 udp ports. I have open 901 port as well.
Before this I have tried connect to the
2006 Feb 08
3
Tripp Lite is up to no good
Well, I have good news and bad news.
I have a Tripp Lite SmartPro UPS attached to a Linux server running Ubuntu
5.10, and I'm running the just-released nut 2.0.3.
I had error -71 from the UPS, which Charles Lepple correctly called out as
a likely cable problem (thank you, Charles.) The cable provided with the
UPS by Tripp Lite was just plain bad. Not too long, mind you- defective.
I
2004 Feb 18
2
Printing vs. iptables
Recently, Windows 2000 SP4 clients have developed a problem when using a
network printer connected to a Samba print share.
Some applications are OK. But take, well, notepad, for example. Selecting
a local printer is normal, but there is a two minute delay (!) in selecting
a network printer. Once selected, all is well. All smb operations are
frozen until the selection happens. This is
2004 Mar 22
0
Registry hack needed
I set up some W2K machines under Samba 2.2.1a for printing using the spoolss
features in that Samba release. I now have Samba 3.02a, and have been
forced to use:
disable spoolss = yes
Now, the W2K machines give the error dialog "could not connect to printer"
because the Windows box is still trying to use the spoolss system, rather
than plain LanMan calls, to figure out whether you