by Dan » Wed, 18 Jan 2006 16:33:03
My home network is mostly XP boxes. I'm having trouble sharing the
printer connected to an XP box with other XP boxes. Is my best option to
use Samba and create an NT domain? I don't really want to do that just
to share a printer, do I have any other options?
Dan
by alex » Wed, 18 Jan 2006 21:23:25
> Dan
Check to make sure both pc's are on the same workgroup, i find MS likes
to randomly change the workgroup names from time to time back to "MSHOME".
by Dan » Wed, 18 Jan 2006 22:47:39
Dan
by Larry Finge » Thu, 19 Jan 2006 07:43:21
>>Can't imagine what issues you might be having sharing a printer from XP to
>>XP, but involving a linux samba server surely wouldn't help the issues.
> I got the idea from somewhere that XP worked better in a domain rather
> than in a workgroup. Sometimes the share works, sometimes it doesn't.
Larry
by Matt Payto » Thu, 19 Jan 2006 09:00:01
>> Can't imagine what issues you might be having sharing a printer from XP
>> to XP, but involving a linux samba server surely wouldn't help the
>> issues.
> I got the idea from somewhere that XP worked better in a domain rather
> than in a workgroup. Sometimes the share works, sometimes it doesn't.
> Dan
Anyway, if you install Print Services for Unix, there will be a new
service, TCP/IP Print server.
When running it allows connections to tcp port 515, and allows lpd
connections to all printers configured on that box. You would then
install Print Services for Unix on the other XP boxes, and configure the
printer on those to use the lpr port on the machine with the printer
connected. No file/print sharing needed. this works equally well for
Windows and *nix client.
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/prints...
Pros :
- No need to configure file and print sharing.
- Works reliably using a standard protocol ( lpd ).
- Cross platform...If your client(s) supports lpd, this should work.
Cons :
- No auto driver installation like when connecting to a "shared" printer.
- Some cheap deskjet type printers do not play well with it.
- Can't use permissions to control access to printers for specific users.
--
- Matt -
by Kurt » Thu, 19 Jan 2006 14:09:28
> Dan
...kurt
by Dan » Thu, 19 Jan 2006 14:58:49
I realise that. I've had a Samba based domain set up before, and didn'tQuote:> Sharing a printer in a domain
> environment is far more complicated than "simple file sharing" (which also
> includes printers), or even user-level sharing (both are available on an
> XP Pro box.
No I haven't. Thought that the linux gurus would be a good place toQuote:> Have you posted in one of the Windows groups? There are many
> and answers are plentiful.
Dan
by Kurt » Fri, 20 Jan 2006 00:14:16
>>XP Pro can join a domain, but XP Home can't.
> They're all XP Pro machines.
>>Sharing a printer in a domain
>>environment is far more complicated than "simple file sharing" (which also
>>includes printers), or even user-level sharing (both are available on an
>>XP Pro box.
> I realise that. I've had a Samba based domain set up before, and didn't
> want that level of complication. But the printer share seems to be hit
> and miss in a simple workgroup setup. I got the idea from somewhere that
> XP Pro shares worked better in a domain. Windows networking certainly has
> it's idiosyncrasies.
>>Have you posted in one of the Windows groups? There are many
>>and answers are plentiful.
> No I haven't. Thought that the linux gurus would be a good place to
> start, even if it is somewhat off topic. I'll give one of them a try,
> thanks.
> Dan
...kurt
by Kurt » Fri, 20 Jan 2006 00:16:06
>>XP Pro can join a domain, but XP Home can't.
> They're all XP Pro machines.
>>Sharing a printer in a domain
>>environment is far more complicated than "simple file sharing" (which also
>>includes printers), or even user-level sharing (both are available on an
>>XP Pro box.
> I realise that. I've had a Samba based domain set up before, and didn't
> want that level of complication. But the printer share seems to be hit
> and miss in a simple workgroup setup. I got the idea from somewhere that
> XP Pro shares worked better in a domain. Windows networking certainly has
> it's idiosyncrasies.
>>Have you posted in one of the Windows groups? There are many
>>and answers are plentiful.
> No I haven't. Thought that the linux gurus would be a good place to
> start, even if it is somewhat off topic. I'll give one of them a try,
> thanks.
> Dan
...kurt
by Dan » Fri, 20 Jan 2006 13:37:34
Thanks.
Dan
>>>XP Pro can join a domain, but XP Home can't.
>> They're all XP Pro machines.
>>>Sharing a printer in a domain
>>>environment is far more complicated than "simple file sharing" (which
>>>also includes printers), or even user-level sharing (both are available
>>>on an XP Pro box.
>> I realise that. I've had a Samba based domain set up before, and didn't
>> want that level of complication. But the printer share seems to be hit
>> and miss in a simple workgroup setup. I got the idea from somewhere
>> that XP Pro shares worked better in a domain. Windows networking
>> certainly has it's idiosyncrasies.
>>>Have you posted in one of the Windows groups? There are many and answers
>>>are plentiful.
>> No I haven't. Thought that the linux gurus would be a good place to
>> start, even if it is somewhat off topic. I'll give one of them a try,
>> thanks.
>> Dan
> If security isn't an issue, try enabling the guest account. Since security
> probably is an issue, create user accounts on the print server that
> exactly match each user account on the other XP boxes that will need to
> print. The usernames and passwords must be identical. Share the printer
> and set the permissions to "Everyone - Print". Open any folder and go to
> tools -> folder options and make sure "Use Simple File Sharing" is NOT
> checked. On the other computers, log the users out and back in. Network
> access may require a password - it does on Server 2003 - unless you make a
> security setting change to remove this requirement. To install the printer
> the easy way on the clients, go to the "Run" dialog, type \\servername.
> When the window opens, right-click the printer and select "connect" (or
> whatver) from the context menu.
> ...kurt
1. Routing Dual-Homed Network to Share Network Resources
I'm running a OBSD 3.3 gateway with a hardwired nic (dc0) and a wireless nic
(wi0). The machine is acting as a wireless accesspoint using hostap.
Been reading through documentation for route (8) and routed, as well as the
FreeBSD Handbook on advanced networking.
I'm having trouble parsing the information to understand how to set the
routing tables so that clients connecting on the wi0 can see the printing
resources and other shared network items on dc0.
wi0 serves up dhcp leases on 192.168.1.0/32 and dc0 serves up dhcp leases on
192.168.0.0/16.
Any resources such as a FAQ or howto would be greatly appreciated. Thanks a
lot in advance for any and all help.
2. 2.5.59 spinlock BUG upon loading initial ramdisk
3. How to access resources on UNIX network from your Windows network.
5. Linux and Windows 3.1 resource-sharing.
7. Sharing resources between Windows and Solaris 8
8. LILO and 2 hard drives - help needed
9. Mounting a Windows shared resource to a Linux computer
10. Accessing Windows for Workgroups shared resources from Linux ???
11. Sharing network resources. Solaris / NT.
12. Changing window resources after window created
13. windows shares across networks?