File sharing problem ?



  • I have a computer with pfsense 2.4.3-RELEASE Installed on it
    Is there any option in pfsense
    Create a "server" to register all computers on the network

    My goal is
    That all computers on the network will see each other without problems and it will be easy to share files

    Currently
    None of the computers see any other computers or the shares (which in any case do not work)

    All computers are connected to Cisco switch (SG 200-26 26-port Gigabit Smart Switch) And the switch is connected to pfsense
    All computers have a fixed address


  • LAYER 8 Global Moderator

    So all these computers are in the same network, ie your lan - you do not have them in different vlans?

    Pfsense has zero to do with communication between devices on the same network.

    There is no such thing as "register" a computer on a network.  Do you mean for the computers to join something like MS Active Directory domain - nothing to do with pfsense.  Your closest thing would be for the computers names to listed in dns for their IPs.  Which really has zero to do with sharing..

    If your computer on 192.168.1.100 can not access share on 192.168.1.101 then that has to do with the file share settings on 101…



  • Create a "server" to register all computers on the network

    You're talking about a domain controller.  Active Directory is commonly used in Windows, but you can also set up a Linux box as a domain controller with Samba.  Of course, for a small network, you don't need a domain controller.  Windows computers advertise their presence without needing any other assistance.  If you're running Linux, Samba on Linux works pretty much the same as Windows file sharing.



  • So all these computers are in the same network, ie your lan - you do not have them in different vlans?

    yes  all in the same network 192.168.1.2-100

    There is no such thing as "register" a computer on a network.  Do you mean for the computers to join something like MS Active Directory domain - nothing to do with pfsense.  Your closest thing would be for the computers names to listed in dns for their IPs.  Which really has zero to do with sharing..

    If your computer on 192.168.1.100 can not access share on 192.168.1.101 then that has to do with the file share settings on 101…

    pfsense is on 192.168.1.1 and dhcp is 192.168.1.2 - 100

    You're talking about a domain controller.  Active Directory is commonly used in Windows, but you can also set up a Linux box as a domain controller with Samba.  Of course, for a small network, you don't need a domain controller.  Windows computers advertise their presence without needing any other assistance.  If you're running Linux, Samba on Linux works pretty much the same as Windows file sharing.

    The different computers have shared folders or shared drives
    But no folders or drives or computers appear on the network
    nothing


  • Netgate Administrator

    You can have pfSense register dhcp host names for dns resolution but that's not what you're asking here.

    Devices in the same subnet should 'discover' each other even without a domain controller so it looks like they are either not trying or are unable. Possible the switch has port isolation of some type enabled?

    You haven't mentioned these are Windows clients, we are just assuming that….

    Steve


  • LAYER 8 Global Moderator

    Well what version of windows are you running?  For stuff to show in "network" windows was using SMBv1 - which on windows 10 for example has been disabled recently.  And to be honest should have been disabled years and years ago.

    If you want to "discover" them and list them use say ws-discovery.  But none of this has anything to do with pfsense - this is all layer 2 stuff and your OS and the services they use on the layer 2, be it broadcast or multicast protocols.

    Even if you register them in dns via dhcp or create your own dns records in pfsense so you can resolve them via fqdn this has nothing to do with what populates that useless network tab in windows.



  • Well what version of windows are you running?  For stuff to show in "network" windows was using SMBv1 - which on windows 10 for example has been disabled recently.  And to be honest should have been disabled years and years ago

    computer 1 windows 10
    computer 2 windows 7
    computer 3 windows 7
    computer 4 ubuntu 16.04
    computer 5 ubuntu 16.04

    I am trying to find the option in the switch that stephenw10 has suggested


  • LAYER 8 Global Moderator

    What switch do you have - that is not something that would be on by default for sure.  And would only be available in a smart/managed switch - Can you ping the other computers IP?



  • What switch do you have - that is not something that would be on by default for sure.  And would only be available in a smart/managed switch - Can you ping the other computers IP

    All computers are connected to Cisco switch (SG 200-26 26-port Gigabit Smart Switch)

    and yes i can ping other computers

    i just reset the switch to factory Default
    Still the same result

    Thanks for the help


  • LAYER 8 Netgate

    The firewall is not involved at all in same-subnet traffic. You need to dig into your Windows networking and figure out what's missing.


  • Netgate Administrator

    Doesn't look like that switch does PVLAN/Port Isolation. Like you say it wouldn't be enabled by default and you would't be able to ping between hosts if it were.

    Looks like some smb setting issue.

    Steve



  • windows firewall is probably set to 'public' or they are not in the same workgroup.

    either way, try finding some windows file sharing tutorials


  • LAYER 8 Global Moderator

    workgroup a machine is nothing more than a place holder for browse service has zero to do with file access or permissions.

    Is quite possible they are in wrong network type, ie public and firewall blocking on the windows machines.

    Linux to windows could be a problem if windows turned off smbv1 and how the samba is setup on the linux box.  What I would do is troubleshoot your problem between 2 windows machines to start with.  Get them working and then move on to what your problem might be between linux and windows.

    A simple sniff is going to be very handy… Do you even get prompted for creds when you hit \computername or \IPaddress?

    If not then file sharing is not enabled or you have a firewall problem.. None of which pfsense has anything to do with when computers are all on the same L2..

    Other than pfsense handing out dhcp I assume it is not involved at all in this scenario... You could just connect your boxes to your switch setup static IPs for file sharing.. Only time pfsense would be involved is if your machines were on 2 different networks and pfsense was the router/firewall between these networks.

    What happens exactly when you hit \computername or \ipaddress of box sharing files?



  • Thanks for the help even though it has nothing to do with pfsense

    What happens exactly when you hit \computername or \ipaddress of box sharing files?

    nothing happens The computer thinks a bit and that's it

    What I would do is troubleshoot your problem between 2 windows machines to start with.  Get them working and then move on to what your problem might be between linux and windows

    I tried what you wrote
    Results
    A computer with Windows 10 recognizes computers with Windows 7 and Linux
    A computer with Windows 7 does not recognize anything
    A computer with Linux does not recognize anything

    On a computer with Windows 10 it only recognizes the other computers
    You can not access shared folders

    If not then file sharing is not enabled or you have a firewall problem.. None of which pfsense has anything to do with when computers are all on the same L2..

    There is no firewall on all computers

    and All shares are set to
    Everyone has the maximum permissions

    again thanks


  • LAYER 8 Global Moderator

    so can windows 7 access the other windows 7 machine?

    As to \computername or \ipaddress = nothing..  I would suggest you sniff when you do it.  Can you resolve the computer name when you just ping via hostname?



  • so can windows 7 access the other windows 7 machine?

    no
    the computer with Windows 7 does not even see the other computers

    Can you resolve the computer name when you just ping via hostname?

    I did not understand
    The intention to ping a computer name and not ip  ?


  • LAYER 8 Global Moderator

    if your using \ipaddress never mind.

    Or are you trying to browse to them via your network tab?

    Why linux can not access windows 7 or windows 7 access the other windows 7 seems odd.  I would assume an issue with smbV1 but if both are running smbv1 you shouldn't have issue access each other.  Or the linux windows combo.

    Your going to have much better luck with help over on a windows forum or a linux forum on access windows shares..

    again pfsense has zero to do with whatever your problem is… I would suggest again you sniff on one of your windows 7 machine while you try and access the \IPaddress of the other windows 7 machine.  This will show you exactly what is happening and why your having a problem... Feel free to post up here you want and will take a look.



  • @andresontom said in File sharing problem ?:

    consulted with the Microsoft tech support canada to know about this problem. I tried to overcome but still its a problem.so is there any solution?

    Microsoft - as any other site that talks about networks : you should put all devices that share and access these shares on the same network segment (LAN or VLAN).
    To make a long story short : the sharing protocol doesn't travels through routers.


  • LAYER 8 Global Moderator

    @gertjan said in File sharing problem ?:

    the sharing protocol doesn’t travels through routers.

    What?? You mean discovery protocols?? SMB works just fine through routers/firewalls - if it didn't corp networks would have a hell of a time and really large flat networks.

    Same goes for other non microsoft/windows sharing protocols like NFS and AFP... All of them work through firewalls/routers just fine.. Lame discovery protocols are what is limited not the actual sharing protocol.

    You might think your helping the user understand their problem at a basic level - but then they pick that up and parrot it elsewhere and the next thing you know you have some nonsense FUD that just will not die.. Like the one where machines need to be in the same workgroup to share files, etc... This is been FUD for years that is just pure utter nonsense..


Log in to reply