I actually managed to access the 'User home folder' in 64bit 7 ultimate,
using both Ubunutu 10.10 and 11.04 in x32.
The trick is to go there via nautilus/file/connectToServer/windosShare.
Add then the IP of win7 machine to field Server. Add win7user(which is set up
on 7machine) to field User. Ad
Update to #22
I actually resolved the problem by reinstalling Windows 7, and - far more
important - used Win7-computer-name instead of actual Domain Name to Login.
Probably this is the hole point.
I'm not sure if under XP the Domain Name *was* the Domain Name and not
the computer-name. However
** Summary changed:
- Can't access Windows 7 computer via SAMBA
+ SAMBA - Can't access Windows 7 computer via SAMBA
--
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/731976
Title:
SAMBA
Hi guys, I know what i'm about to say will sound down-right strange, but
my ubuntu 10.10 server (dist-upgrade from 10.04), the samba server
worked flawless. But now, I installed Ubuntu 10.10 desktop, and Samba
3.5.4 is giving me the exact same issues. No matter what
username/password I type in, sam
I tested the issue with SMBNETFS and FUSESMB and it still happens...
** Tags added: apport-collected
** Description changed:
Binary package hint: samba
Hello,
I have 4 computers in my home (mine is not included), being 2 of them
Windows 7 Ultimate and 1 of them Windows XP Professio
PROBLEM SOLVED:
Problem Solved... I recovered my Windows 7 Ultimate image (with Norton
Ghost 15) to the problematic Windows 7 Ultimate PC and now I can connect
it... Surprisingly I could access it via my Windows 7 Ultimate before
this recovery, but I couldn't in my Linux.. This was probably caused
Please see the last comment for a WORKAROUND to this issue...
** Changed in: samba (Ubuntu)
Status: Incomplete => 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/731
Hi Andrè,
Thank you for your comment, however, I do not agree that recovering a
whole system image, is a solution, nor a workaround.
In my case, the Windows 7 clients never changed, the ubuntu
machine/SAMBA installation did. The problem is also not isolated to one
or two clients, but all of them,
Hi kwagga,
Is this a recent problem or does it happens since you have been using
Ubuntu 10.10?
If this problem is recent, so I suggest you yo recover your LINUX with
any IMAGE RECOVERY program (dd or CLONEZILLA or anything related) if you
have an image of it...
MORE INFO: I also use Ubuntu 10.10
Please keep the discussion centered around how to effectively reproduce
the bug. Otherwise developers will have no idea how to help with this
issue. Workarounds are fine, but should not be the focus of the
discussion other than to provide insight into what is causing the issue.
To recap where we s
Hi Clint,
Unfortunately reproducing the error, isn't so easy, since I spoke to a
friend of mine, and he is having no issues, I even took his smb.conf
file, overwrote mine, and the errors are still the same.
What I can do, is create a video, upload to youtube, and then you can
see step by step wha
** Changed in: samba (Ubuntu)
Status: Incomplete => 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/731976
Title:
SAMBA - Can't access Windows 7 computer via SAMBA
--
Ubun
PROBLEM (ACTUAL RESULTS):
Can't see the remote paths nor files, but I can see the remote
computer...
EXPECTED RESULTS:
See the path and files of the remote computer...
POSSIBLE CAUSE TO THE PROBLEM:
Windows 7 Configuration that don't work well in Ubuntu SAMBA package (client)
when accessing i
I've made an interesting discovery, if someone also experiencing the
problem could also check it:
If you add, 'public = yes' (without quotes) to the share, and remove any
valid users, read list, force user, etc, are you able to access the
share?
This seems to be working for me, and seems to be a
Alright, Firstly, André let me sincerely apologize for thinking that
your original idea, of wiping the clients was ludicrous, as it would
seem that the problem was on their side.
I was so frustrated with my computers/samba this weekend, I decided to
try one last thing and formatted/reinstalled two
Well it seems that something does get out of sync on windows 7 machines
that causes them to have trouble accessing samba. However, this doesn't
sound like a bug in samba, so I'm marking this one as Invalid.
Thanks so much to Andre and kwagga for all the work and feedback trying
to reproduce the is
I had a similar problem... But mine I solved by reinstalling Windows...
So, this bug might be in Windows network configuration file...
Strangely, I could access the problematic PC with my Windows without
problem... So, this configuration in Windows only affects Linux SAMBA
access to it...
In m
17 matches
Mail list logo
