Kommentare zu: Why cant my Linux server communicate with my local PC’s on the same subnet? http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/ Centos Neuigkeiten Mon, 10 Oct 2011 04:29:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Von: nitu http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/comment-page-1/#comment-502 nitu Sun, 27 Jun 2010 06:29:49 +0000 http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/#comment-502 cisco certification bootcamp http://ciscotutorial.info/ cisco certification bootcamp
http://ciscotutorial.info/

]]> Von: franky http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/comment-page-1/#comment-501 franky Sun, 27 Jun 2010 05:48:39 +0000 http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/#comment-501 technology http://aalpha.org/ technology
http://aalpha.org/

]]> Von: Loggsie http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/comment-page-1/#comment-500 Loggsie Sun, 27 Jun 2010 04:51:54 +0000 http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/#comment-500 Thomas, I expierenced the same issue when setting up the Linksys NAS200 on my home network. I found that the NAS was only accessible outside if I had Filter Internet NAT redirection disabled. You have done the correct thing in leaving this option out, the SPI firewall won't effect the matter however tweaking VPN may make a difference it did for me. I have mine setup like so: IPSec Passthrough, PPTP Passthrough, L2TP Passthrough - Disabled Filter IDENT Port 113 - Enabled Filter Multicast - Enabled Block Anonymous Internet Requests - Enabled Filter Internet NAT Redirection - Disabled Addtionally my Linksys router is my DHCP provider, and I have TCP port 23 enabled on port forwarding & port triggering to connect to my NAS at IP 192.168.1.108, just incase I decide to access this anywhere from the world. I suggest leaving DHCP enabled and setting a static IP for just the Linux Server, ensure you set up port forwarding & port triggering so this can be access via the Internet, this may also resolve internal issues you may be having. Also bear in mind that if you have any 3rd party firewall installed you may need to enable the NetBios port to communicate between your PC's and Linux Server, try disabling your firewall to see if this may be the root cause. As long as your router is configured as above there should be no issues. Thomas, I expierenced the same issue when setting up the Linksys NAS200 on my home network. I found that the NAS was only accessible outside if I had Filter Internet NAT redirection disabled. You have done the correct thing in leaving this option out, the SPI firewall won’t effect the matter however tweaking VPN may make a difference it did for me. I have mine setup like so:

IPSec Passthrough, PPTP Passthrough, L2TP Passthrough – Disabled
Filter IDENT Port 113 – Enabled
Filter Multicast – Enabled
Block Anonymous Internet Requests – Enabled
Filter Internet NAT Redirection – Disabled

Addtionally my Linksys router is my DHCP provider, and I have TCP port 23 enabled on port forwarding & port triggering to connect to my NAS at IP 192.168.1.108, just incase I decide to access this anywhere from the world.

I suggest leaving DHCP enabled and setting a static IP for just the Linux Server, ensure you set up port forwarding & port triggering so this can be access via the Internet, this may also resolve internal issues you may be having.

Also bear in mind that if you have any 3rd party firewall installed you may need to enable the NetBios port to communicate between your PC’s and Linux Server, try disabling your firewall to see if this may be the root cause. As long as your router is configured as above there should be no issues.

]]> Von: Dr_ice69 http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/comment-page-1/#comment-499 Dr_ice69 Sun, 27 Jun 2010 04:50:56 +0000 http://1299.de/2010/06/why-cant-my-linux-server-communicate-with-my-local-pcs-on-the-same-subnet/#comment-499 --EDIT: addition-- Sorry, I saw, "192.168.2 - 11 with 192.168.8.1" and thought "different subnets".. After re-reading your post, I realized, I've seen this same problem with linksys routers. Best way is to setup a static DHCP lease for your Linux box, in the linksys... Or make a BIG DHCP range, and statically set your linux box in the TOP of that range, so its IP is unlikely to get doled out by the linksys. I think the bottom line is, the linksys doesn't like clients it didn't send out the DHCP for... –EDIT: addition– Sorry, I saw, “192.168.2 – 11 with 192.168.8.1″ and thought “different subnets”.. After re-reading your post, I realized, I’ve seen this same problem with linksys routers. Best way is to setup a static DHCP lease for your Linux box, in the linksys… Or make a BIG DHCP range, and statically set your linux box in the TOP of that range, so its IP is unlikely to get doled out by the linksys.

I think the bottom line is, the linksys doesn’t like clients it didn’t send out the DHCP for…

]]>