Re: [Samba] Samba 2.2.7 and Windows XP
Hello All: Problem solved!! What was the correction?? Go into the BIOS, and disable the onboard parallel port. It seems that XP takes a different view of mapping network resources when there is an existing physical resource, either a partition, or a physical printer port. It refuses to overlay any physical resource with a mapped resource, even though this has been normal behaviour of all preceeding versions of 32-bit Windows that I am aware of. And, true to Microsoft form, XP doesn't give a reasonable error message; it asks for other credentials for a resource that it will REFUSE to connect to regardless of what is supplied. Ahhh well . . . Hope this helps someone else who may be as confused as I was. A. Becker Alan Becker wrote: Several months ago, I replaced a WinNT4 PDC with a Samba server. It was a successful transition, and has been working without trouble. Since the beginning, I have had no issues with file sharing/locking at all, but printing was another matter. In this network, there are several dot-matrix printers that are ONLY printed to from a DOS application, and a laser for Windows printing. All printers are ethernet-connected, using either internal or external Jet-direct interfaces. There are no special user requirements for connecting to shared printers. Problem: I just added a WinXP Pro workstation as a member of the Domain. It authenticates, and runs the logon script as expected (up to a point). It is able to connect drive letters to network shares, no problem. As soon as it gets to the NET USE statements that map printers, it stops and wants a username and password. Nothing that I give it is acceptable. As a test, I created a shared print queue for one of the dot-matrix printers on the XP workstation itself, and oddly enough, XP asks for a username/pw to map LPT1 to a queue located on ITSELF!! The PDC is RedHat 9 with current updates (kernel 2.4.20-28.9, Samba 2.2.7a-8.9.0, Cups 1.1.17-13.3.0.3). The majority of the clients on this network are Win98 or Win NT4. All these older clients have no problem mapping either drives or printers. Circumstantially, the finger seems to point to the XP workstation in some way, especially its inability to map a printer located on itself. Does anyone know of anything peculiar about XP and printer mapping?? Of course, I'd love to have someone offer up a magic bullet solution, but even a suggestion for a direction to investigate would be gratefully received. A. Becker -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 2.2.7 and Windows XP
Several months ago, I replaced a WinNT4 PDC with a Samba server. It was a successful transition, and has been working without trouble. Since the beginning, I have had no issues with file sharing/locking at all, but printing was another matter. In this network, there are several dot-matrix printers that are ONLY printed to from a DOS application, and a laser for Windows printing. All printers are ethernet-connected, using either internal or external Jet-direct interfaces. There are no special user requirements for connecting to shared printers. Problem: I just added a WinXP Pro workstation as a member of the Domain. It authenticates, and runs the logon script as expected (up to a point). It is able to connect drive letters to network shares, no problem. As soon as it gets to the NET USE statements that map printers, it stops and wants a username and password. Nothing that I give it is acceptable. As a test, I created a shared print queue for one of the dot-matrix printers on the XP workstation itself, and oddly enough, XP asks for a username/pw to map LPT1 to a queue located on ITSELF!! The PDC is RedHat 9 with current updates (kernel 2.4.20-28.9, Samba 2.2.7a-8.9.0, Cups 1.1.17-13.3.0.3). The majority of the clients on this network are Win98 or Win NT4. All these older clients have no problem mapping either drives or printers. Circumstantially, the finger seems to point to the XP workstation in some way, especially its inability to map a printer located on itself. Does anyone know of anything peculiar about XP and printer mapping?? Of course, I'd love to have someone offer up a magic bullet solution, but even a suggestion for a direction to investigate would be gratefully received. A. Becker -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Packet filter rules for outgoing SMB connections/mounts only?
Try the firewall script at: http://projectfiles.com/firewall. I have used this script on RH 7.x, 8 and 9 boxes. It is very simple to use for simple applications, and yet has considerable power for more challenging situations. It requires iptables in order to operate. The graphical installer actually uses 'dialog', and has a text-based menu interface. If I understand your request correctly, it would be handled that way by default. Once the firewall is started, any external connection that is not explicitly allowed will be denied. HTH, A. Becker Rashkae wrote: The standard internet sharing firewall scripts will do this and then some automagically. See www.netfilter.org for examples. On Thu, Feb 19, 2004 at 12:03:36PM +0100, Andreas Schildbach wrote: Hello everyone, Is it possible to configure the packet filter for Linux kenel 2.4.x in a way so outgoing connections (mounts) from the firewalled machines (to a specific IP address) are possible, but no incoming SMB mounts are allowed at all. In other words, I want to be able to mount a share of an external machine, but like to keep the security risks involved as small as possible. Regards, Andreas -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS and raw printing
I have replaced an NT4 file/print server with a Samba server (built on RH9 with all current patches (kernel 2.4.20-28.9, Samba 2.2.7a-8.9.0, Cups 1.1.17-13.3.0.3). Having trouble with a DOS application and raw printing. This DOS app exclusively prints to any of several dot-matrix printers, running fan-fold paper. When I set up a raw queue and map LPT1 to it, the DOS app prints just fine. However, the queue manager does absolutely nothing (like ejecting a page) to segregate the output from different jobs. This behaviour normally completes printing a job somewhere in the midst of a page and stops. When a new job is routed to that printer, it continues printing where the previous job ended. Thus there is output from 2 jobs on the same page, and the 2nd (or nth) job is not printing aligned at page boundaries. Is there any config available to set up a queue that is raw as far as the print stream is concerned (does no filtering or translation), and yet can eject a page after each job to keep different print streams on separate pages?? Any suggestions will be welcome. TIA, A. Becker -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CUPS printing from Windows
I have replaced a WinNT4 PDC with a Samba server. I'm not experiencing problems with file sharing/locking at all, but printing is another issue. In this network, there are several dot-matrix printers that are ONLY printed to using a DOS application, and a laser (HP 2300, PCL and PS) that is primarily used for Windows printing. Problem: Windows clients (using downloaded drivers from print$) don't seem to have full or proper control of printing. Example 1: An excel user has to click on Print to fit in Page setup in order for the page to be scaled properly. Otherwise it prints on multiple pages in very large type. Example 2: Another Excel user attempts to set Landscape orientation. The setting is accepted. no error is generated, but the page continues to print in portrait orientation. To begin with, this unit is based on RedHat 9 with all current updates (kernel 2.4.20-28.9, Samba 2.2.7a-8.9.0, Cups 1.1.17-13.3.0.3). After discovering that CUPS was the only printing system that RH9 installed, I went to the documentation and read the HOWTO chapters 18 (Classical printing support) and 19 (CUPS printing support). I then did the following: (1) Create the print queues using the RH/Gnome Printing control applet (2) Test printing from Linkx (ok) (3) Obtain the Windows drivers from the NT4 PDC (copied the whole c:\winnt\...\w32x86 structure to a scratch area. (4) Obtain the detailed descriptions of each installed driver using the rpcclient utility from the Samba server, querying the old NT4 server (temporarily attached) with the getdriver queue_name function. Route the query results to a file. Repeat for all queues. (5) Write a script to parse the output of (4) and automate steps 4-10 of Manual Driver Installation in 15 Steps from Chapter 19. (6) Run the script for each print queue. Drivers appear to be added without problem. (7) Join a WinNT workstation to the Samba domain (8) As Administrator, connect to the laser print queue. Succeeds, no error message. (9) Bring up Excel, attempt to print Landscape as noted above. This fails. Questions:: (A) The failure to command the printer properly suggests a problem with the uploaded drivers. Are there any other common explanations for this type of behavior?? (B) I attempted to set the dot-matrix queues to the Generic printer/Raw device. In this mode, I printed a short text file (in Linux), and copied a test file to the network queue (under Windows). In either case, the file was printed, but the paper was not advanced to the next page. In other words, this queue is so raw that it doesn't even recognise the end of a print job, so multiple print jobs can be printed on the same page. Is there any middle ground, where inter-job pagination occurs, but no other filtering is enabled?? TIA for your attention. A. Becker -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
