[Bug 731976] Re: SAMBA - Can't access Windows 7 computer via SAMBA

[Michael Zverina]

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 this whole thing (in my specific case) looks
very likely to be a windows-(or configuration) and not a SMB problem.

However if someone tries to connect using "WORKGROUP" or similar instead
of "computer-name" under domain field this will NOT work.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/731976

Title:
  SAMBA - Can't access Windows 7 computer via SAMBA

Status in “samba” package in Ubuntu:
  Invalid

Bug description:
  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 Professional and the other
  one a Windows 7 Home Premium...

  PROBLEM:

  I can access with my LINUX (Ubuntu 10.10 and Kubuntu 10.10) via SAMBA
  the 3 computers in my home, but the other one (that is Windows 7
  Ultimate) I can't, and I don't know why... The message that shows when
  I try to access this PC is: "Cannot connect to the pc CONCE-CPU".

  IMPORTANT:

  I also have a Windows 7 Ultimate in my PC (I do a DUAL-BOOT with
  Windows 7 and Linux Ubuntu) that can access this computer and all of
  the others as well... So, the problem is not in the remote PC and not
  in my machine, it's a LINUX specific problem...

  DETAILS:

  My LINUX: Linux kernel 2.6.35-27-generic-pae; Ubuntu/Kubuntu 10.10 ;
  using most up-to-date  SAMBA ;

  The Problematic Remote PC: Windows 7 Ultimate; Up-to-date (without SP1
  of Windows 7); with AVAST (FREE - WITHOUT FIREWALL) and built-in
  Windows FIREWALL ENABLED;

  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  PS: I have a Windows XP Professional at home that also have AVAST and
  this SAMBA problem don't happen with it...

  PS²: I can ping the problematic remote PC (with Windows 7 Ultimate)
  with my LINUX if I use the IP of this problematic remote PC with the
  command "ping IP-OF-THE-REMOTE-PC" (if I use the host name - that is
  CONCE-CPU - instead of the IP, it don't answer to the ping because it
  shows the error message "ping: unknown host conce-cpu" - the command
  syntax used was "ping CONCE-CPU")...

  Thanks for your attention,

  André M.
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.10
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  NmbdLog:
   
  NonfreeKernelModules: nvidia
  OtherFailedconnect: Yes
  Package: samba 2:3.5.4~dfsg-1ubuntu8.3
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=pt_BR
   LANG=pt_BR.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-28.49-generic-pae 2.6.35.11
  SambaServerRegression: Yes
  SmbConfInclude: Yes
  SmbLog:
   
  Tags: maverick
  Uname: Linux 2.6.35-28-generic-pae i686
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/731976/+subscriptions