Hi ,
I guess I have a problem connected to this thread:
I installed latest image ubuntu-13.04-desktop-i386.iso,
on the laptop, I have HP printer connected to it and
work well, but when I share it I can see it and connect to
it from windows machine but not send a test page print.
Any Ideas ?
test for comment
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To manage notifications about this bug go to:
Hi ,
I guess I have a problem connected to this thread:
I installed latest image ubuntu-13.04-desktop-i386.iso,
on the laptop, I have HP printer connected to it and
work well, but when I share it I can see it and connect to
it from windows machine but not send a test page print.
Any Ideas ?
test for comment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To manage notifications about this bug go to:
Re #88: Yes, it was working with 3.6.3-2ubuntu2.3 and stopped working
with 3.6.3-2ubuntu2.4. However, the problem has changed. Before the fix
on any version, the shared printer was not visible to the workgroup, but
now they are. And now, when printing from a windows client, I'm getting
the
Re #88: Yes, it was working with 3.6.3-2ubuntu2.3 and stopped working
with 3.6.3-2ubuntu2.4. However, the problem has changed. Before the fix
on any version, the shared printer was not visible to the workgroup, but
now they are. And now, when printing from a windows client, I'm getting
the
Post #21 fixed issue for me, had to login as root, but it worked
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To
Post #21 fixed issue for me, had to login as root, but it worked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To manage
history.log shows samba:i386 (3.6.3-2ubuntu2.3) being installed, and I
could once again access printer shares from windows. However, this
morning, I could not! The history.log shows 2013-03-23 23:27:26
samba:i386 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4).
that's strange,
history.log shows samba:i386 (3.6.3-2ubuntu2.3) being installed, and I
could once again access printer shares from windows. However, this
morning, I could not! The history.log shows 2013-03-23 23:27:26
samba:i386 (3.6.3-2ubuntu2.3, 3.6.3-2ubuntu2.4).
that's strange,
What happened to the fix?
On 2013-03-09 23:20:24 /var/log/apt/history.log shows samba:i386
(3.6.3-2ubuntu2.3) being installed, and I could once again access
printer shares from windows. However, this morning, I could not! The
history.log shows 2013-03-23 23:27:26 samba:i386 (3.6.3-2ubuntu2.3,
What happened to the fix?
On 2013-03-09 23:20:24 /var/log/apt/history.log shows samba:i386
(3.6.3-2ubuntu2.3) being installed, and I could once again access
printer shares from windows. However, this morning, I could not! The
history.log shows 2013-03-23 23:27:26 samba:i386 (3.6.3-2ubuntu2.3,
This bug was fixed in the package samba - 2:3.6.3-2ubuntu2.4
---
samba (2:3.6.3-2ubuntu2.4) precise; urgency=low
[ Olly Betts ]
* Change net share allowedusers to use RPC call that works with
Microsoft Windows 2008 r2. (LP: #1061244)
[ Louis Bouchard ]
* Fix issue with
This bug was fixed in the package samba - 2:3.6.3-2ubuntu2.4
---
samba (2:3.6.3-2ubuntu2.4) precise; urgency=low
[ Olly Betts ]
* Change net share allowedusers to use RPC call that works with
Microsoft Windows 2008 r2. (LP: #1061244)
[ Louis Bouchard ]
* Fix issue with
Since the bug is difficult to reproduce in a systematic manner, I have
tested the version in -proposed twice with successful results. I will
mark it as verification-done even if I would like someone else who has
the bug to confirm.
Please be aware that if the samba registry is not destroyed and
** Tags removed: verification-done-precise verification-needed-quantal
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients
Since the bug is difficult to reproduce in a systematic manner, I have
tested the version in -proposed twice with successful results. I will
mark it as verification-done even if I would like someone else who has
the bug to confirm.
Please be aware that if the samba registry is not destroyed and
** Tags removed: verification-done-precise verification-needed-quantal
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to
Hello Tony, or anyone else affected,
Accepted samba into precise-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/samba/2:3.6.3-2ubuntu2.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Tony, or anyone else affected,
Accepted samba into precise-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/samba/2:3.6.3-2ubuntu2.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks for fixing this! I'm looking forward to getting my printer
working. I assume that once the fix is released, I'll get it with the
standard apt-get update and apt-get upgrade operation?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
@eric:
Yes, this will happen 7 days after the package gets uploaded into
-proposed and tests confirm that no regression are found. It is
currently still waiting for upload.
You will receive an update once it gets uploaded and made available for
testing.
--
You received this bug notification
Thanks for fixing this! I'm looking forward to getting my printer
working. I assume that once the fix is released, I'll get it with the
standard apt-get update and apt-get upgrade operation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@eric:
Yes, this will happen 7 days after the package gets uploaded into
-proposed and tests confirm that no regression are found. It is
currently still waiting for upload.
You will receive an update once it gets uploaded and made available for
testing.
--
You received this bug notification
One thing to be aware of that I noticed while testing.
Even with the patch applied, existing printers will not get updated
entries in the samba registry. I have found no other way than deleting
the registry file completely to get new entries created. I had to do the
following :
$ sudo rm -f
One thing to be aware of that I noticed while testing.
Even with the patch applied, existing printers will not get updated
entries in the samba registry. I have found no other way than deleting
the registry file completely to get new entries created. I had to do the
following :
$ sudo rm -f
@rickyrockrat
The updated fix is in the upload queue :
https://launchpad.net/ubuntu/precise/+queue?queue_state=1queue_text=
While I would advise against it, you can pickup the packaging files and
build yourself a PPA (clicking on the arrow symbol beside the package
name will expose the
@rickyrockrat
The updated fix is in the upload queue :
https://launchpad.net/ubuntu/precise/+queue?queue_state=1queue_text=
While I would advise against it, you can pickup the packaging files and
build yourself a PPA (clicking on the arrow symbol beside the package
name will expose the
Any news on the release of this fix for precise? I'm preparing to set up
servers for windows networks, and I need to know what workaround I have
to use. 3.6.6 as originally released is not going to go on these
servers.
I've made Ubuntu my distro of choice, but this was reported almost a
YEAR ago,
Any news on the release of this fix for precise? I'm preparing to set up
servers for windows networks, and I need to know what workaround I have
to use. 3.6.6 as originally released is not going to go on these
servers.
I've made Ubuntu my distro of choice, but this was reported almost a
YEAR ago,
** Changed in: samba (Ubuntu Quantal)
Status: Invalid = Fix Released
** Changed in: samba (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
** Changed in: samba (Ubuntu Precise)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared
Thanks for the work, I've merged that fix with the one which was
currently waiting in the SRU queue and uploaded a new update with both
included
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
** Changed in: samba (Ubuntu Quantal)
Status: Invalid = Fix Released
** Changed in: samba (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: samba (Ubuntu Precise)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To
Thanks for the work, I've merged that fix with the one which was
currently waiting in the SRU queue and uploaded a new update with both
included
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
** Changed in: samba (Ubuntu Precise)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients
Okay, after numerous retries (as in at least 20 virtual machines), I
think I have identified a systematic way to reproduce the problem.
Test environment
==
1 virtual machine running Ubuntu 12.04 Precise with USB connected printer [1]
1 virtual machine running Windows XP
1) add the
** Description changed:
- Since installing 12.04 I can no longer connect my windows XP clients to my
laser printers on the Ubuntu system using samba.
- It works on 11.10 using the exact same smb.conf file.
- I can see the printers from the windows clients, I can select it, I install
the
** Branch linked: lp:~louis-bouchard/ubuntu/precise/samba/samba-
lp_967410
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared
tested on Quantal and confirmed that the proposed fix for Precise is in
the source for Quantal. Marking it invalid
** Changed in: samba (Ubuntu Quantal)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: samba (Ubuntu Quantal)
Status: Confirmed = Invalid
**
** Changed in: samba
Status: Unknown = Fix Released
** Changed in: samba
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows
** Changed in: samba (Ubuntu Precise)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to
Okay, after numerous retries (as in at least 20 virtual machines), I
think I have identified a systematic way to reproduce the problem.
Test environment
==
1 virtual machine running Ubuntu 12.04 Precise with USB connected printer [1]
1 virtual machine running Windows XP
1) add the
** Description changed:
- Since installing 12.04 I can no longer connect my windows XP clients to my
laser printers on the Ubuntu system using samba.
- It works on 11.10 using the exact same smb.conf file.
- I can see the printers from the windows clients, I can select it, I install
the
** Branch linked: lp:~louis-bouchard/ubuntu/precise/samba/samba-
lp_967410
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To manage
tested on Quantal and confirmed that the proposed fix for Precise is in
the source for Quantal. Marking it invalid
** Changed in: samba (Ubuntu Quantal)
Assignee: (unassigned) = Louis Bouchard (louis-bouchard)
** Changed in: samba (Ubuntu Quantal)
Status: Confirmed = Invalid
**
** Changed in: samba
Status: Unknown = Fix Released
** Changed in: samba
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot
I have swat , samba 3.6.3 , ubuntu 12.04 server 64 , CUPS 1.5.3
I have printer1 without portname [],
printer 1 and 2 are the same model and I use the same protocol and ppd .
enumprinters 5
printername:[\\LOCALHOST\printer1]
portname:[]
attributes:[0x1048]
My solution to reset the rpcclient :
1) Stop Samba
2) Delete files:
/var/lib/samba/registry.tdb
/var/cache/samba/printing/*
4) Restart Samba
yeah !
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
I have swat , samba 3.6.3 , ubuntu 12.04 server 64 , CUPS 1.5.3
I have printer1 without portname [],
printer 1 and 2 are the same model and I use the same protocol and ppd .
enumprinters 5
printername:[\\LOCALHOST\printer1]
portname:[]
attributes:[0x1048]
My solution to reset the rpcclient :
1) Stop Samba
2) Delete files:
/var/lib/samba/registry.tdb
/var/cache/samba/printing/*
4) Restart Samba
yeah !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've spent something like 10 hours now (debugging from 1000 miles away), and
the other party has gone to bed. I just now got my printers to rename.
This works for renaming the printer (where the heck is the name stored??) (var
is on an different file system, so my path is different) symbolic
I've spent something like 10 hours now (debugging from 1000 miles away), and
the other party has gone to bed. I just now got my printers to rename.
This works for renaming the printer (where the heck is the name stored??) (var
is on an different file system, so my path is different) symbolic
** Changed in: samba (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
Well after numerous tests, I can no longer reproduce this bug ! I tested
the following :
Precise 12.04.1 VM
Precise 12.04 VM
Quantal 12.10 VM
Quantal 12.10 Baremetal
Raring 13.04 VM
From a vanilla install :
• Confirm Publish shared printers connected to this system is enabled in
** Changed in: samba (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To manage
Well after numerous tests, I can no longer reproduce this bug ! I tested
the following :
Precise 12.04.1 VM
Precise 12.04 VM
Quantal 12.10 VM
Quantal 12.10 Baremetal
Raring 13.04 VM
From a vanilla install :
• Confirm Publish shared printers connected to this system is enabled in
I do confirm that the steps outlined in the link in comment #69 did
allowed me to setup the printer. Moreover, testing the daily development
build indicates that the current version in Raring fixes this issue.
I will try to identify the fix so it may be brought to prior versions
** Changed in:
I do confirm that the steps outlined in the link in comment #69 did
allowed me to setup the printer. Moreover, testing the daily development
build indicates that the current version in Raring fixes this issue.
I will try to identify the fix so it may be brought to prior versions
** Changed in:
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=8769
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
** Changed in: samba
Status: Unknown = Fix Released
** Changed in: samba
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=8769
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows
** Changed in: samba
Status: Unknown = Fix Released
** Changed in: samba
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot
The information posted in #21 and #25 above is close but I could not get
it to work.
A solution that worked for me is at
http://forums.linuxmint.com/viewtopic.php?f=42t=28397p=618065#p618065
There were some additional instructions in setting /etc/samba/smb.conf
that were needed.
--
You
The information posted in #21 and #25 above is close but I could not get
it to work.
A solution that worked for me is at
http://forums.linuxmint.com/viewtopic.php?f=42t=28397p=618065#p618065
There were some additional instructions in setting /etc/samba/smb.conf
that were needed.
--
You
We all know there are workarounds for this and what surprises me more s
that after 8 months NO FIX! I just took my install of ubuntu 12.04 to
the latest samba packages from Raring and the problem is still there . I
was already running CUPS 1.61. What I did notice is something I did not
see before
We all know there are workarounds for this and what surprises me more s
that after 8 months NO FIX! I just took my install of ubuntu 12.04 to
the latest samba packages from Raring and the problem is still there . I
was already running CUPS 1.61. What I did notice is something I did not
see before
Hi all,
I'm having trubles adding shared printer from Xp clients.
I got the message Windows cannot connect to the printer. Either the printer
name was typed incorrectly or the specified printer has lost its connection to
the sever.
I tried solution @ #21 but when typing enumprinters i get
alfalfa, as quick solution, try adding printer using URL (there should be an
option for that in Add pritner dialog box. URL of printer page is the same it
has in CUPS webinterface (most likely it looks like
http://printserver.addr:631/printers/Printer_Name ).
It worked for me.
--
You received
Hi all,
I'm having trubles adding shared printer from Xp clients.
I got the message Windows cannot connect to the printer. Either the printer
name was typed incorrectly or the specified printer has lost its connection to
the sever.
I tried solution @ #21 but when typing enumprinters i get
alfalfa, as quick solution, try adding printer using URL (there should be an
option for that in Add pritner dialog box. URL of printer page is the same it
has in CUPS webinterface (most likely it looks like
http://printserver.addr:631/printers/Printer_Name ).
It worked for me.
--
You received
Hi to whom it may concern,
At the top of this posting, it states that this bug affects 40 people
but judging by the number of google references and comments on the
Ubuntu Forums, it affects a great deal than 40. I am referring to the
bug where one seems to be unable, to set up a printer attached
Hi to whom it may concern,
At the top of this posting, it states that this bug affects 40 people
but judging by the number of google references and comments on the
Ubuntu Forums, it affects a great deal than 40. I am referring to the
bug where one seems to be unable, to set up a printer attached
I have a home mixed network containing Ubuntu 12.04, linux mint 13, windows xp,
windows 7 computers.
p5q runs ubuntu 12.04 and has a brother mfc 7860dw printer
p5 runs win xp and has a HP photosmart 6510 printer
u64 runs ubuntu 12.04
LM13 and maya both run linux mint 13 (based on ubuntu 12.04)
I have a home mixed network containing Ubuntu 12.04, linux mint 13, windows xp,
windows 7 computers.
p5q runs ubuntu 12.04 and has a brother mfc 7860dw printer
p5 runs win xp and has a HP photosmart 6510 printer
u64 runs ubuntu 12.04
LM13 and maya both run linux mint 13 (based on ubuntu 12.04)
Has anyone come across a problem in the opposite direction (windows
printing server, local Ubuntu 12.04 machine)? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Has anyone come across a problem in the opposite direction (windows
printing server, local Ubuntu 12.04 machine)? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients
This bug seems to be similar to # 990388. I found an easy workaround in
askubuntu (you need to set up your printers again on a precise desktop),
which I posted also here:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/990388/comments/15
--
You received this bug notification because you are
This bug seems to be similar to # 990388. I found an easy workaround in
askubuntu (you need to set up your printers again on a precise desktop),
which I posted also here:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/990388/comments/15
--
You received this bug notification because you are
Since the last samba updates to precise the two workarounds (installing
3.5.6 deb package or using samba 4RC1 from the software centre) that I
mentioned above are no longer effective; 356 will not install, and 4RC1
will not start.
--
You received this bug notification because you are a member of
Since the last samba updates to precise the two workarounds (installing
3.5.6 deb package or using samba 4RC1 from the software centre) that I
mentioned above are no longer effective; 356 will not install, and 4RC1
will not start.
--
You received this bug notification because you are a member of
** Changed in: samba (Ubuntu Precise)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
Please don't change this bug's status without an explanation. Thanks.
** Changed in: samba (Ubuntu Precise)
Status: New = Confirmed
** Tags added: precise quantal
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Changed in: samba (Ubuntu Precise)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To manage
Please don't change this bug's status without an explanation. Thanks.
** Changed in: samba (Ubuntu Precise)
Status: New = Confirmed
** Tags added: precise quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have also found that installing samba 4rc1 from the Ubuntu software
centre has no problem with print and file sharing even though it does
give errors during the installation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
I have also found that installing samba 4rc1 from the Ubuntu software
centre has no problem with print and file sharing even though it does
give errors during the installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Colin
Thanks for providing this additional log data - assuming that the
printer you are trying to access is called merlin I think these are
the pertinent log messages:
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2012/09/07 07:08:19.643668, 5]
Colin
Are you using the standard install samba configuration?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To
Hello James, Pretty much, just a few minor changes that I've been using
for the last 10 years. Merlin is the printer and I'm using the standard
printer configuration:
[printers]
comment = All Printers
browseable = yes
path = /var/spool/samba
printable = yes
Hi Colin
Thanks for providing this additional log data - assuming that the
printer you are trying to access is called merlin I think these are
the pertinent log messages:
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2012/09/07 07:08:19.643668, 5]
Colin
Are you using the standard install samba configuration?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To manage notifications
Hello James, Pretty much, just a few minor changes that I've been using
for the last 10 years. Merlin is the printer and I'm using the standard
printer configuration:
[printers]
comment = All Printers
browseable = yes
path = /var/spool/samba
printable = yes
Well, I needed this to work now. Ubuntu software centre removed samba,
installed the deb 3.5.6 package, everthing works great.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Well, I needed this to work now. Ubuntu software centre removed samba,
installed the deb 3.5.6 package, everthing works great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows
I've split the cups/samba race bug out into bug 1047262
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared printers
To manage
Hi Colin
Thanks for the extra information; I have a hunch that this might be
upstream https://bugzilla.samba.org/show_bug.cgi?id=8769.
Please could you repeat with a log level of 10 - if the log looks
exactly the same as in the upstream bug I think we can confirm the issue
sufficiently.
However
Non-admin user:
ubuntu@hendrix:~$ smbclient //127.0.0.1/ip4000r -U ubuntu
Enter ubuntu's password:
Domain=[SHOUSE] OS=[Unix] Server=[Samba 3.6.6]
tree connect failed: NT_STATUS_ACCESS_DENIED
Admin user:
jamespage@hendrix:~/src/ubuntu/quantal$ smbclient //127.0.0.1/ip4000r
Enter jamespage's
Scrub that last comment - forgot to add ubuntu user to samba password
file.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/967410
Title:
Windows clients cannot connect to shared
1 - 100 of 210 matches
Mail list logo
