SOLVED Windows Share Still Not working.

[Patrick M. Hausen]

@lilg Thanks, now ipconfig from Windows, please.

 

[lilg]

Sorry I am hesitant to put my ipconfig out there. Don't want to expose my computer.

 

[Samuel Tai]

Sorry I am hesitant to put my ipconfig out there. Don't want to expose my computer.

We just need the netmask and the default gateway.

 

[Patrick M. Hausen]

You won't. It's a private LAN behind your Internet router, right?

 

[Patrick M. Hausen]

This does not make any sense. Your DHCP server is not in your LAN. So there is a relay involved. This is by no means a simple flat network. Are you in an enterprise environment with your systems?

 

[Samuel Tai]

That's a very peculiar setup for a home network. Your server is pingable on the Internet, but your PC is not. Usually, your server would be on the same subnet as your PC, so it would also have a 23.16.24x.x IP. I'm concerned in fact that you've plugged your server into the public side of your router, instead of the inside.

As the server and the PC are in separate subnets, additional configuration is needed to achieve SMB connectivity, mostly with LMHOSTS entries.

 

[Patrick M. Hausen]

He tried with the blank IP address. It would not be uncommon for the router to block 445 by default ...

But you are right, @Samuel Tai - if this is a home network, probably his FreeNAS is on the "outside".

 

[lilg]

OK so ... Network setup ...
ISP -> Modem -> 2x IPs
1st IP -> Wifi router for home use
2nd IP -> Switch -> office hardline computers & NAS Server

 

[Patrick M. Hausen]

You have to plug the NAS into a port of your Wifi router. Or buy an additional switch if the router has got only one port plus Wifi.

 

[lilg]

OK - so if I hardline the NAS on the Wifi router, can I access it from the Office computer considering it is on the other ip, using this setup above?

 

[Samuel Tai]

Let me sketch this up in Visio, so we all understand what's going on. Gimme a few.

 

[Samuel Tai]

OK, is this how your network is laid out?

If it is, then you should swing your hardline switch behind your router, and then re-IP everything to the 23.16.140.0/22 network, and the various guides will then work.

 

[Patrick M. Hausen]

@Samuel Tai If the router is not just an access point and so essentially a bridge, shouldn't the 23. network be behind the router? Or yet another perfix on that second interface? I am wondering where the DHCP server is located in this setup? At the ISP, hence the RFC 1918 address? I admit I have never seen anything like this.

 

[lilg]

This is my current setup

 

[lilg]

Would it be easier to just use simple FTP into the NAS?

 

[Patrick M. Hausen]

So essentially you plugged your computer and the NAS into "the Internet" without any router and firewall inbetween. This is not how this is intended to work in most cases.

 

[lilg]

How would this work?

 

[Patrick M. Hausen]

With most ISPs the idea is to plug a router into the modem and literally everything behind that. Who advised you to create a setup like this?

 

[Samuel Tai]

How would this work?
View attachment 39534

Move the switch/hub behind the Wi-Fi router. Everything, including the NAS, gets re-IPed to whatever the Wi-Fi router provides, most likely a private IP.

 

[lilg]

With most ISPs the idea is to plug a router into the modem and literally everything behind that. Who advised you to create a setup like this?

:) Advised. - I did it mostly to take full advantage of the unthrottled ISP Speed. The router I have is slower and I found an extra IP on my modem