LinspireKwikis
If you're at all interested in LinspireOS, this was a good deal. Lifetime Click'N'Run and updates for a one-time price. Not at all that bad a deal if you're a fan or contemplating LinspireOS for a distro. They're all gone. We're #416: http://www.choicepc.com/choicepc-france.php The LinspireOS 4.5 Installation CD md5sum is: 2a998ded51d192e3d196dae70e58b6f8 Q: Setting up Epson C80 printer on a Linspire computer, and using it as network printer for a Windows LAN A: On the Linspire computer: Enable file sharing
Add the Printer through Linspire OS
On Windows XP machine:
Q: How do I integrate LinspireOS 3.x into my MSWindows network? A: This tip is recommended for advanced users of LinspireOS. This tip comes from Scott Lowe, on http://support.linspire.com/ Configuration changes are requiredBefore you can join a MS Windows network domain, you need to make some modifications to the Samba configuration file located at /etc/samba/smb.conf. Namely, Samba needs to be told to change its security mode to domain as well as the name of the domain of which it will become a member. I made changes to the smb.conf file using the nano editor, which I installed after the initial system setup. For your purposes, use any editor you like to make changes to the /etc/samba/smb.conf file. I recommend making a backup of the original just in case something goes wrong. Lab configurationFor this article I am running a Windows 2000 Server as a domain controller for the domain named lab2kd.com. The server is named lab2k. On the workstation side, I am running a Linspire 3.0 OS on a 350-MHz Pentium II PC with 128 MB of RAM. The Linspire workstation is getting an IP address via a separate DHCP server, but both machines coexist on the 192.168.1.0/24 network. Find the lines that begin with security, workgroup, and password server in the smb.conf file and change them to reflect the appropriate values as shown below. security = domain workgroup = LAB2KD password server = * The only difference between your installation and mine should be the workgroup because you will enter the name of your own Windows domain. If you are running Windows 2000 as a domain controller as I am, make sure to use the NetBIOS name rather than the fully qualified Windows 2000 domain name (in my case this is lab2kd.com). The password server = * line indicates that Samba will look for any domain controller in the domain. If you have problems, you can set this specifically to the name of a Windows 2000 domain controller. Once these changes are made, the Samba services need to be restarted using the following entry from a command prompt: /etc/init.d/samba restart Join the domainThe previous steps prepared the Samba server for assimilation into the Windows collective. Now, its time to actually join the domain. From a terminal window on the Linspire workstation, use the following command replacing LAB2KD with the name of your domain and LAB2K with the name of one of your Windows domain controllers. The U indicates a Windows domain administrator account that is capable of adding machines to the domain. You will be prompted to enter this users password during this process. smbpasswd j LAB2KD r LAB2K U administrator Once you type in the password associated with the Windows administrator account, you should get a message that says something like "Joined domain LAB2KD." To make sure it worked, you can use Active Directory Users And Computers (ADUC) to see if there is a computer account listed for this domain Browsing the Windows networkIf you attempt to browse the Windows network from the Linspire workstation, it may still not work out as expected. Linspire needs to be told what Windows user to emulate. In other words, you need to be browsing with a user account that exists in the Windows domain. You can configure this information by choosing the Network File Sharing applet from the Linspire Start | Settings | Network menu. The Network File Sharing applet takes three parameters: username, password, and domain name. For ease of demonstration, I will use the Windows administrator account from the Linspire machine. Obviously, if you used Linspire on a users desktop, you would want to use a less capable account. Once you make this configuration change, you can browse the Windows domain. I have created a share on the Windows 2000 server named Shared for demonstration purposes. In this image, you can see that the Linspire machine is browsing the Windows server. One problem that I have yet to work out is the initial error message that comes up when I click on the Network Neighborhood icon on the Linspire workstation, which indicates that the Windows network (smb:/) is not available. However, typing:
does bring up the appropriate associated resources. |
||||
|
||||