1 / 15

Cosc 4750

Chapter 27: Working with Windows. Cosc 4750. Working with Windows. File and print sharing Windows and UNIX can share printers and files NT/2000/XP has a lpr client that can be installed, so that UNIX can print to a win32 machine.

ramya
Download Presentation

Cosc 4750

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 27: Working with Windows Cosc 4750

  2. Working with Windows • File and print sharing • Windows and UNIX can share printers and files • NT/2000/XP has a lpr client that can be installed, so that UNIX can print to a win32 machine. • Many Unix machines print through the windows server or visa versa in the cosc department.

  3. file sharing • There is PC-NFS programs for NT/2000 that allow you mount UNIX NFS exports • problems with file permissions. Windows use super set of UNIX file permissions • Sharity allows UNIX to mount NT shares • again, problems with file permissions • mounts NT shares with root ownership of all files.

  4. Samba • Allows UNIX machines to create NT shares. • installed by default by redhat. • Windows machines, can use the shares just like any other windows shares. • Gets around file ownership problems, but matching usernames between NT and UNIX. • You can specify "windows shares", and by default, home directories are shared. • Also allows for print sharing to UNIX from windows machines.

  5. Samba (2) • smbfs connections from windows to UNIX mount –t smbfs –o usename=seker //engserver/admin /mnt/smbmount • mount calls smbmount, which has more options, but mount provides a more consistent and easier interface. • Either direction, current problem is EOL marker is different in windows and UNIX.

  6. Samba (3) • Since Redhat 7.2, you are allowed to use samba to authenticate users via a windows system instead of the password file. • Samba 3.X now understands trusts. • Good idea? • Creates a single “username domain”

  7. Samba (4) • Version 3 • Now can join the windows domain as a member server • Can eliminate the need for Windows servers. • An AD structure can be created for windows clients, so that they believe they are talking to a “windows Server” • Including authenication, login scripts, group policies, etc. • Including downloading of printer drivers, updates, etc.

  8. Emulators • Xwin32 and eXceed are clients that allow you login to UNIX machine with a gui interface. • There are many others as well. • VNC allows you work at a remote desktop on windows, at the same time as some else works at it. • Mail clients, use pop server on UNIX or imap servers. • Also there are UNIX clients that allow you to fake a NT login and use the console. • There are unix programs to connect to terminal services/remote connections on windows

  9. Windows Applications • Wine and other programs allow you run windows applications on a UNIX platform. • With the release of StarOffice/OpenOffice (sun), these products are starting to fall out of favor. • They are hard to configure and don’t always work. • Wine creators states, that there are a lot of problems. (installed default since Redhat 7.2)

  10. Windows emulators • Vmware and softwindows are window emulators. Gives you look and feel of windows 9X and XP. • Allows all windows applications to be installed an used. • Problem with softwindows: • Even idle and minimized, used 100% of a cpu.

  11. VMware • Although expense ($120 with ed discount) • Works very well. • Can either run windows on a linux machine • Or a linux machine on a windows client • Works really well for hardware that linux currently doesn't support! • Either way the VMware O/S believes it is running directly on the hardware • As such, you need to make sure there is enough memory and hard space to run two O/S.

  12. Dual Booting • Dual booting, at startup you can choose which O/S to start. The other is not running. • With linux, you can mount the "windows" partitions • But NTFS is currently read-only • FAT/FAT32 can be mounted as read/write.

  13. filesystem sharing. • There are now hardware venders that sell products that connect to both UNIX and NT machines at the same time. • Both platforms can use the same hard drives. • leads to questions of file locking. Handled mostly by the vendors hardware instead of O/S.

  14. Windows • Microsoft is being to emulate UNIX networking systems daemons. • Telnetd, ftpd (through IIS) can use wu_ftp and skip IIS • In the future, Windows and UNIX may be communicate directly without the need of a third party programs/daemons. • ie. mount an nfs drive on an windows machine. • UNIX utilities for windows

  15. Q A &

More Related