Configuring a primary Linux server with a secondary Windows server
- The
Linux system must have
Samba for Linux installed.
To create mapped drives of Linux directories exported by Samba on RedHat Enterprise Linux, when SELinux is in enforcing mode and you need interoperability with AIX, Linux, or Windows, you must run this command as root:
setsebool -P samba_export_all_rw=1
To restore the previous behavior, run this command as user root:setsebool -P samba_export_all_rw=0
Note: For more information on Samba, go to www.samba.org.
Samba Server and Client software to interoperate Linux with Windows machines allows Linux servers and workstations to share files and printers with personal computer clients running Windows operating systems. Because Samba for Linux uses industry-standard Microsoft networking protocols, PC clients can access Linux files using Microsoft networking client software. PC users can use remote Linux file systems directly from their machines like local file systems. The namespace will appear on the network just like any other Windows shared folder. Samba for Linux provides these services by implementing the SMB networking protocol to run on NetBIOS over TCP/host name.
By doing this set of procedures on both an InfoPrint Linux server and an InfoPrint Windows workstation, you can configure InfoPrint Manager to support interoperability between InfoPrint Linux servers and InfoPrint Windows servers.
When configuring InfoPrint Manager for Linux and Windows servers to support interoperability, make sure that these rules are followed:
- Each InfoPrint Manager server must be accessible by all of the other InfoPrint Manager
servers using the same host name.
For example, if Server1 is an InfoPrint Manager server with a host name of
server.local, then all other InfoPrint Manager servers must useserver.localto access Server1. - The host name address for each InfoPrint Manager server must be the host name that is identified for the first (or primary) network card that is defined to that server.
- All printer objects (whether logical destination, actual destination, or queue) must
have unique names if they are used by interoperating InfoPrint servers.
If the printer objects do not possess unique names, you might have trouble viewing them through the InfoPrint Manager Interface from a non-namespace server.
- InfoPrint Manager Notifications should only run on the primary server and should be stopped on the secondary servers.
LPD service for Linux can be used however, by submitting jobs with the lpr command to actual destinations on the Linux server. The lpr command can also still be used as before with Windows printer destinations (just not InfoPrint Manager printers).