Results 1 to 10 of 10

Thread: Unable to see my Windows Network

  1. #1
    robertomason NNTP User

    Default Unable to see my Windows Network

    I have a Domain server (Samba) setup. I have Opensuse 11.1 installed along with Ubuntu 9.04. Both use Gnome as my Desktop. On Ubuntu, I see and can access my Windows Network. With Opensuse I can't. Something is not properly set up. If anybody could help, I greatly appreciate it.

    Thanks

  2. #2
    robertomason NNTP User

    Default Re: Unable to see my Windows Network

    Solved my own problem, I'm learning. Problem had to do with firewall. Open appropriate ports, or disable your firewall

  3. #3
    PV NNTP User

    Default Re: Unable to see my Windows Network

    On Sat August 1 2009 05:06 pm, robertomason wrote:

    >
    > I have a Domain server (Samba) setup. I have Opensuse 11.1 installed
    > along with Ubuntu 9.04. Both use Gnome as my Desktop. On Ubuntu, I see
    > and can access my Windows Network. With Opensuse I can't. Something is
    > not properly set up. If anybody could help, I greatly appreciate it.
    >
    > Thanks
    >
    >

    robertomason;

    Take a look at this HowTo:
    http://opensuse.swerdna.org/suselanprimer.html

    For more advanced information you will find a number of HowTos at:
    http://opensuse.swerdna.org/

    If after reading these you are still unable to connect, post the contents
    of /etc/samba/smb.conf.

    The most common problems are:
    A. Not starting smbd and/or nmbd;
    B. Not opening ports on your firewall, including broadcasts; and
    C. Not creating users with "smbpasswd -a <username>"

    --
    P. V.
    "We're all in this together, I'm pulling for you." Red Green

  4. #4

    Default Re: Unable to see my Windows Network

    It's because by default every NIC is set in external zone which by default blocks every port. If you set your NIC as internal zone and won't tick "Protect firewall from internal zone" then you should be fine.
    How does a linux geek make love??

    - rtfm; unzip; strip; touch; finger; mount; fsck; more; yes; umount; zip; sleep;

  5. #5
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    11,731
    Blog Entries
    2

    Default Re: Unable to see my Windows Network

    Quote Originally Posted by BenderBendingRodriguez View Post
    It's because by default every NIC is set in external zone which by default blocks every port. If you set your NIC as internal zone and won't tick "Protect firewall from internal zone" then you should be fine.
    That's invalidating the firewall IMO, might as well turn it off.
    Leap 42.3 & 15.1 &KDE
    FYIs from the days of yore

  6. #6
    robertomason NNTP User

    Default Re: Unable to see my Windows Network

    Thanks for the info

  7. #7

    Default Re: Unable to see my Windows Network

    No, why? Even if it is in internal zone it still blocks every port but allows the broadcast and multicast on some ports so that you can see printers, files etc.
    How does a linux geek make love??

    - rtfm; unzip; strip; touch; finger; mount; fsck; more; yes; umount; zip; sleep;

  8. #8
    Join Date
    Jun 2008
    Location
    Mallow, Ireland
    Posts
    1,031
    Blog Entries
    1

    Default Re: Unable to see my Windows Network

    Quote Originally Posted by BenderBendingRodriguez View Post
    No, why? Even if it is in internal zone it still blocks every port but allows the broadcast and multicast on some ports so that you can see printers, files etc.
    Internal zone interface are completely unprotected. Thought I try it after reading this post since I to want to see my Windows network.

    This is what the summary of my firewall says after moving my wireless to the internal zone.

    Code:
    Internal Zone
    Interfaces
    Atheros AR5001X+ Wireless Network Adapter / ath0
    Open Services, Ports, and Protocols
    Internal zone is unprotected. All ports are open. 
    So I'm leaving mine in the external zone with Samba Server and Client services allowed.
    "To err is human... to really foul up requires the root password."

  9. #9

    Default Re: Unable to see my Windows Network

    Hmmm then i was wrong, i guess internal zone is for sub networks that are protected from an internal firewall.
    How does a linux geek make love??

    - rtfm; unzip; strip; touch; finger; mount; fsck; more; yes; umount; zip; sleep;

  10. #10
    Join Date
    Mar 2008
    Location
    Oz
    Posts
    11,731
    Blog Entries
    2

    Default Re: Unable to see my Windows Network

    Samba generally needs ports TCP 139 & 445 + UDP 137 & 138 (& broadcasts). That's for a workgroup. In windows server situations there's TCP 135 as well, so in this situation here it's perhaps not enough to open in Yast just the netbios server and the samba server services, I suppose you should also open TCP135. This is all a bit hazy to me but the services modules seem to leave out 135.
    Leap 42.3 & 15.1 &KDE
    FYIs from the days of yore

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •