Windows/Linux on WiFi side of LAN can use port 80/web sites on my Linux server on wired side of LAN, but not NFS shares or SMB shares (Samba).
Is my Arris router blocking the traffic? If both/all systems are wired, everything works/connects. Does anyone know how to make file sharing work?
Related
I have a windows machine that has a local WAMP server running without the Internet. I would need to connect a few Mac computers to that local server via Ethernet cable stream some video content.
I kind of know that I would need a router to connect all to Mac computers and a server computer. I am still not clear how to do it without the Internet.
Any Help would be really appreciated! Thank you!
You should be able to just get an ethernet switch (something like this) and connect everything. You would then just reference your server in a browser or other app by it's IP address or computer name instead of a www address.
What you are talking about is soomthing called a peer-to-peer setup. See this Setting up a Peer to Peer Network
I can access my computer's (localhost) web service using eclipse mars and jax-ws. However, I'm just curious, how can I make it so that other remote computers that is not connected by LAN?
Any advice, direction, or what I should research is welcomed.
Your computer is invisible to internet. It will connect to internet
via a router (ADLS modern for en example).
Your router is visible on Internet and with a public IP Address, you
can try some website to see what its address is (for example
http://whatismyipaddress.com/)
You need to config your router to make it forward the request from internet
to you computer LAN address and your web-service port, the way to
config port forwarding is depend on your router.
I like to connect to a TCP server that run in a machine that is connected to the LAN in my home network. This LAN can be connected to internet via either following methods.
1. Through a router which has a wireless or wired WAN connection
2. Through a router which uses a mobile broadband connection, for example a router that accept a USB modem to connect to internet.
I know in the first case, we can use port forwarding.
In the second case, I believe telcos use PPP protocol and port forwarding does not work.
In addition, even in the first case, if ISP does not give a static IP, then we need to use DNS mapping service to map a fixed URL to the allocated dynamic IP and we need to configure router to go and register the dynamic ip at the start up.
My question is, are there any other better methods that can be used in this situation? I am wondering how chat applications connect to each other? I hope they maintain a TCP connection between two devices, without a central relay server?
I have 2 devices on the same network and I want to communicate via TCP on the same network. Device 1 is a computer running a Debian OS on virtualbox, and another is an android tablet. Interesting enough, my tablet acts as a server no problem via an app. Any other device on the same network can connect to the tablet. The computer on the other hand is not so cooperative. Running netcat -l -p 6667 on my computer should allow incoming connections to communicate with my computer via TCP on port 6667, but this is not the case. Netcat opens a socket but I can't connect to it in anyway. Is there an underlying reason as to why this does not work? All device are under the same router. I have disabled firewall on my computer as well.
From your information, i would say your problem is you need to set up port forward.
VirtualBox and VMware both create virtual machines with the NAT network type by default. If you want to run server software inside a virtual machine, you’ll need to change its network type or forward ports through the virtual NAT.
here is a guide that will show you how to Forward ports to virtual machine
I'm writing a C# remote control for my media player. It runs on my Android phone.
I have a client app listening for TCP connections on my computer which, one a connection has been established, processes commands (Volume up, volume down, ...). I've tested that part using telnet 127.0.0.1 on my computer, and it works great.
Things are trickier when it comes to connecting from my phone, since it's not on the same network (I don't have Wi-Fi, only wired connections), so I'm not sure how to proceed. Basically I want to connect to a computer that's behind a router.
Should I rather host the TCP server on my phone, and have the PC connect to it? Take IRC as an example: although I'm behind a router, I can connect to servers outside, without port forwarding.
Or if hosting the server on my computer is fine, how do I connect to it?
I don't understand everything to this yet, so feel free to correct me if I got something wrong.
It would be more logical to keep the PC hosting the server, and configure your router to forward connections to your PC. You have two options:
Establish a DMZ: all incoming connections on the router will be forwarded to one PC only. This is easiest when you only have 1 PC on the network that needs to accept connections.
Configure port forwarding: you can instruct the router to forward connections incoming on port X to the IP Y on port Z. This way, multiple PC's can listing for connections (using different ports on the router). It is also a bit more secure.
How to set these up depends on your router, but most routers just accept connections on their port 80 and offer an easy web-interface. If you give your router brand, we can link you to the manual.
Things are trickier when it comes to connecting from my phone, since
it's not on the same network (I don't have Wi-Fi, only wired
connections), so I'm not sure how to proceed. Basically I want to
connect to a computer that's behind a router.
What you want to achieve is possible, but you need to learn about NAT traversal and hole punching.
Most often, devices behind a NAT/Router have a private IP address only valid on the LAN. Remote devices can't guess it. This private address is translated into a public IP address by the NAT when the device wants to communicate with the WAN.
The easy solution is you can give a public IP address to the device behind the NAT. In this case, remote devices on the WAN will easily be able to reach it, because its address is public.