Unable to share from one subnet to another?
First I have reviewed a few different solutions listed on Experts Exchange, but none seem to work, this is why I am posting this question.
Cannot connect to a network share across sub-domains. History on situation: Setup TEST AD (192.168.0.05). My IT staff and I we looking at applying a AD for Desktop security.
We joined about 5 computer all IT staff.
When the AD was active we all could share data across the subnets.
Worked great but when we went to Office 365 we decided to no use local AD and demoted our Domain server after dis-joining our computers.
So we are all using work groups.
Now as long as everyone is in the 0.X sub net they can see the shares in that sub-domain, but are unable to connect to the 30.X shares, and visa versa the 30.x users cannot see anything in the 0.x sub domain.
I tested the same situation on the 30.X sub domain and I am able to share across 30.x subnet but the 0.x subnet cannot connect.
I am looking for any type of suggestions to help?
My router does not have any rules for sub nets.
Our work stations are connected as a workgroup.
We are not using anything in the AD except we are connected to Office 365, we have not implemented Azure.
Cannot connect to a network share across sub-domains. History on situation: Setup TEST AD (192.168.0.05). My IT staff and I we looking at applying a AD for Desktop security.
We joined about 5 computer all IT staff.
When the AD was active we all could share data across the subnets.
Worked great but when we went to Office 365 we decided to no use local AD and demoted our Domain server after dis-joining our computers.
So we are all using work groups.
Now as long as everyone is in the 0.X sub net they can see the shares in that sub-domain, but are unable to connect to the 30.X shares, and visa versa the 30.x users cannot see anything in the 0.x sub domain.
I tested the same situation on the 30.X sub domain and I am able to share across 30.x subnet but the 0.x subnet cannot connect.
I am looking for any type of suggestions to help?
My router does not have any rules for sub nets.
Our work stations are connected as a workgroup.
We are not using anything in the AD except we are connected to Office 365, we have not implemented Azure.
We do this using IP addresses and not names. So, no inter-subnet name resolution is needed.
But, the Windows firewall needs to have the scope for incoming File and Printer Sharing rules set to include the other subnets.
I don't know, but can guess, what you mean by "see the shares".
If we Start \\[ipaddress] then we can see the shares.
But, we can't "see" the shares in the Network display that people have come to like.
Mapping, shortcuts, etc. work.
But, the Windows firewall needs to have the scope for incoming File and Printer Sharing rules set to include the other subnets.
I don't know, but can guess, what you mean by "see the shares".
If we Start \\[ipaddress] then we can see the shares.
But, we can't "see" the shares in the Network display that people have come to like.
Mapping, shortcuts, etc. work.
ASKER
I am using the IP address.
And is the scope in the Windows firewall on each file "server" expanded to include the other subnets? i.e. the File and Print sharing rules....
ASKER
\\192.168.0.27 I would normally put the IP address in the File Explorer and then the shares would display then I would be able to map the location of the share. I saw the comment about the "NetBIOS broadcasts do not cross subnets", this I believe is what I am running into and it sounds like I will need to make a change in order to share data, until I rebuild the domain.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
to see the computers at network node in windows explorer you may start services ComputerBrowser and Server for each client.
you also should use fixed IP4 addresses for each pc (not using a DHCP automatically). then subnet mask is 255.255.0.0 to cover both
192.168.0.X and 192.168.30.X.
note if the router's IP4 address is 192.168.0.y (or 192.168.30.y) and it is used as DHCP Server for WIFI clients, then the router has a range of IP4 addresses for those clients which you must not violate with the fixed IP4 addresses.
generally it would be better to use a second network adapter in each pc for the internal network. that would allow you to use a separate subnet, say 192.168.1.X, for this.
Sara
you also should use fixed IP4 addresses for each pc (not using a DHCP automatically). then subnet mask is 255.255.0.0 to cover both
192.168.0.X and 192.168.30.X.
note if the router's IP4 address is 192.168.0.y (or 192.168.30.y) and it is used as DHCP Server for WIFI clients, then the router has a range of IP4 addresses for those clients which you must not violate with the fixed IP4 addresses.
generally it would be better to use a second network adapter in each pc for the internal network. that would allow you to use a separate subnet, say 192.168.1.X, for this.
Sara
I stick with what I said earlier and the questions remain.
Fundamentally there needs to be a path between the subnets - a router would do that much with no NAT: one side connected to one subnet and the other side connected to the other subnet with their respective IP addresses belonging to the subnet they are connected to.
No local traffic would traverse the router because the idea is that packets destined for the other subnet will be directed to the router's local port and the router knows (has a route) to the other subnet / the other port on the router.
It's really very simple and adding anything else seems counterproductive to me at least.
I say this because I'm not sure just how you are interconnecting the subnets.
Beyond that you need Windows File and Printer Sharing firewall rules with scope to include the other subnets.
i.e. Remote Address includes the Local subnet AND the other subnets.
And, you need a route in the gateway that points to the local address of this router for packets destined to the other subnet.
That should be all you need for this to work just fine - well of course the file "servers" need to have appropriate Shares but I guess you already have that, right?
Now, you may implement this in various ways but this description should be easy to understand.
Fundamentally there needs to be a path between the subnets - a router would do that much with no NAT: one side connected to one subnet and the other side connected to the other subnet with their respective IP addresses belonging to the subnet they are connected to.
No local traffic would traverse the router because the idea is that packets destined for the other subnet will be directed to the router's local port and the router knows (has a route) to the other subnet / the other port on the router.
It's really very simple and adding anything else seems counterproductive to me at least.
I say this because I'm not sure just how you are interconnecting the subnets.
Beyond that you need Windows File and Printer Sharing firewall rules with scope to include the other subnets.
i.e. Remote Address includes the Local subnet AND the other subnets.
And, you need a route in the gateway that points to the local address of this router for packets destined to the other subnet.
That should be all you need for this to work just fine - well of course the file "servers" need to have appropriate Shares but I guess you already have that, right?
Now, you may implement this in various ways but this description should be easy to understand.
ASKER
Thank you added Net Bios rule to my firewall, everything is working accross subnets.
So, I wonder how NetBIOS could affect the IP Addressing that you said was in use? It shouldn't AFAIK.
ASKER
The Sonic wall did not have net bios rules.
Could be he enabled NetBIOS over TCP/IP to allow data transfer (TCP 139), which is different than NetBIOS name resolution. If that's the case, I would instead recommend enabling direct SMB over TCP port 445.
NetBIOS broadcasts do not cross subnets. What are you using for name resolution?