Site to site SMB discovery and sharing [closed]
-
Heh, I also have a few disagreements about how the software is done. However, it is sold as a pre-configured package, using its own wifi router that remains separate from our business network. The peer-to-peer network only has two servers and three clients, all supported remotely by the parent company under a support agreement, and we are not supposed to "mess with it". I do have access to the mobile laptop clients and can make minor tweaks to their configuration. I can also add a computer to the network.
The system is pretty cutting edge, servers control a material mill, shaping items from 3D scans created on the clients.
To be fair to the manufacturer, I am trying to extend the usability of the system beyond what they had envisioned. I have spoken to the company and explained what I want to do. They have no objections, but have never had anyone else do it, and offered no help in setting it up. So I'm hacking away at it, learning a few things along the way. :)
-
Hacking away….:)
If you have a machine that can do WINS server....
Or, Samba can do that too, it has a WINS server built-in, look Samba man.
Then, push "dhcp-option WINS x.x.x.x" in OpenVPN server. -
"using its own wifi router that remains separate from our business network."
So if its on a different layer 2 then your other networks, devices on this isolated network would never be able to "broadcast" for names.. If your just trying to hit some server that is on this isolated network. Just create a dns record that points to this IP.
How would you bridge this network into your if its behind its own router?? Do you have control over this router? Is it doing nat? Would really need more details to try and help you skin this breed of cat.
-
I really appreciate the replies, guys. This project is something I get to in between other duties so it's taking me some extra time.
To clarify, I no longer consider broadcast/discovery necessary for this particular setup. Using the HOSTS file will suffice for such a narrow case. Should probably change the title of the original post. Before I do that, allow me to answer your questions though.
I do not have access to the the router of the small network in question, so next step is to try the pfsense server on its NAT'd LAN side.
I have multiple static IPs available, and PfSense WAN will go on one of those. Access will be through this static IP.
Any thoughts on this scheme are appreciated, even if it is to instruct me to open a different thread.
-
Let me try to illustrate..
-
Why are you calling the wifi router a router when (apparently) the same subnet is on both sides?
-
In these kinds of setups I usually forego using the WAN side of the wifi router. Disable dhcp and set an IP address which is out of the way. Plug in a cable to LAN side and just let the traffic flow between the ethernet port and the wireless antennas.
Hey, I like the diagram in your sig. It would be nice if it was in an editable format, like .odg.
-
In that case it is not a router it is an AP or a bridge. Calling it a router just confuses people.
-
Okay, I understand.
-
Closing comment: My initial testing was done using Windows 7 clients. However, the laptop clients in use are actually Windows 10. When I tested the W10 clients, everything worked out of the box - browsing and sharing, as if they were on the same physical network.
So yes, a Peer to Peer (shared key) connection is a viable setup for me.
