SG1100 after configuring switch Network shares not accessible to win 10
-
Hello to all,
Thank you for taking the time to read this message. I am using a SG1100 which works well so far. I needed to connect another switch to it so I followed this guide:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/switch-overview.html
And very quickly my unifi controller saw the switch and I Was able to use it, internet access and all.
The problem started when I tried to access a synology nas on that switch from my windows box using file explorer. I was able to connect to it and then I am prompted for a password. I enter the user name and password and it did not work. I then connected the laptop to the same switch and it still did not work. I tried it from my PoP OS box and I am able to access the share via smb just fine. Both machines can access the web interface of the synology and that is how I am transferring files but it is inefficient as I am moving about 110 gigs of data and I need to just do a copy and past if possible.The win10 machine was able to access the shares just fine before I configured the switch, and everything else seems just fine right now. To test I added a very old dlink NAS and I am able to access that just fine over the network with file explorer.
Any ideas? I am blanking out on this as I have tried a few other things with no success. Everything I mentioned is running the latest software available to it.
-
@alfaro so when you say on the same switch.. You also mean these devices are in the same network/vlan?
Or are you devices on different vlans/networks that are routed via pfsense?
Devices on the same network/vlan talking to each other have nothing to do with pfsense.
-
@johnpoz
Thank you for your reply.
I apologize I did not add more info. Well, they are on the same VLAN, at least from my understanding they must be from the instructions on configuring the switch. That said, both my linux box and the Win10 machine could access both the LAN and web last week. After configuring the switch, both my linux box and win10 can access the web but only the linux box can access the synology via smb. The only thing that has changed in the last week is the fact that I configured the switch on the SG1100. I can access the web interface as well from both.
I have gone over the instructions and they seems clear and I know that they are correct because I can still access it from linux, just not sure ho wit affected the win10 machine. I only use it for one or two things but I do need to transfer files. Now sure what could have gone wrong. I even moved the win10 machine to the same switch, actually the port next to the port to which the synoloy is connected. They are both in the same IP range x.x.x.40 and x.x.x.47.
I actually get the prompt to enter a user name and password and it say I can't access. I use the same user name and password on the linux box and it works.Any thoughts?
-
@alfaro said in SG1100 after configuring switch Network shares not accessible to win 10:
Any thoughts?
Again devices on the same network have nothing to do with pfsense.. So whatever your issues is, its not related to pfsense. Unless its somehow dns related, and your resolving dns from pfsense?
When devices are on the same network, be it native or vlan - the router (pfsense) is used to get off the network and has no involvement at all with client A talking to client B. If your having issues with devices talking to each other via whatever protocol.. Its not related to pfsense.. When client A talks to B on the same network - there is no way pfsense would even see that conversation let alone interfere with it in any way.. So unless your doing bridging on pfsense where one of these clients on 1 side of the bridge and the other client is on the other side.. Pfsense is not involved in whatever issue your seeing.
This is not a pfsense thing, this is not a sg1100 thing.. This is networking at basic level. When a devices wants to talk to IP address xyz. If that IP is on the same network as it via what its IP address and mask is - it just arps for the mac of this IP, if it gets a response it send the traffic to that mac. A router is to get off the network (pfsense) and has nothing to do with that devices on the same network talking to each other.
Maybe your doing some sort of client isolation at your switch? Can you ping client A from B?
-
@johnpoz
Thank you for replying.I am with you that this is basic networking. I have both devices getting an ip from the pfsense dhcp server. Both are as follows: 192.168.1.40 for Synology and 192.168.1.47 for teh win 10 machine. My linux box is 192.168.11.48.
I can ping from win10 both my synology and the linux box. I can ping from the linux box to both synology and win 10 - there is no isolation on the switch as this is my "trusted" area of the network. Anything on a VLAN gets 192.168.10.x address to prevent them from coming to my network and it is reserved for two separate switches (IOT specifically).I will to ping fromsynology out but my linux box reaches it hyst fuine.
It all started after configuring the second prot of sg1100 as switch and it is the only readon why I think there is something there -
@alfaro said in SG1100 after configuring switch Network shares not accessible to win 10:
My linux box is 192.168.11.48.
Well your linux box is not on the same network, unless that is a typo and you meant 1 or you have some crazy large mask.. My guess that is a typo.
How do you have everything wired together to this sg1100 and its ports.. But let me stress this yet again!! Pfsense has ZERO to do with devices on the same network talking to each other ZERO!!
I don't know what to tell you about your problem.. But devices on the same network don't do anything with pfsense to talk to other devices on the same network!! So unless your pfsense IP on this network is same as one of your devices..
How do you have this all wired to your sg1100? You could unplug your sg1100 and devices on the same network can talk to each other - since its not involved at ALL in this communication..
If your devices are all on the same switch.. Why don't you do that - unplug the wired that runs from the switch to pfsense.. And go ahead and ping your other device by IP.. See! pfsense has nothing to do with them talking to each other..
