Connecting devices via the internet and exchanging files over Ethernet.
Connecting devices via the internet and exchanging files over Ethernet.
Yes, you can transfer files between devices simultaneously. Your laptop connects to Wi-Fi and shares internet via Ethernet, while your primary PC uses Ethernet for file transfers. You can enable network sharing settings so both devices access each other’s resources at the same time.
Using the approach you're considering hasn't been confirmed recently. It doesn't connect you to the same network, forces NAT traversal, and makes your device behave more like a router. There seems to be no known method to bypass this. Bridging adapters won't help either. Tunneling might be an option, but I haven't tested it. Another idea could involve sending requests over the internet, forwarding them through a server, and accessing via your public IP on the client machine. This approach is theoretically possible.
You're asking if a PC and its router on the same network can communicate. The setup you described—using the ISP router's IP (192.168.0.1)—means both devices share the same subnet, like 192.168.0.x. When you share the internet connection, the second PC will get an IP in a different range, such as 192.168.1.x, but they remain on the same local network. So yes, they should be able to talk to each other.
192.168.0.0/24 and 192.168.1.0/24 represent separate networks. The subnet configuration defines the starting point of the first network bit and the endpoint of the last bit, typically the broadcast address. For 192.168.0.0/24, the first usable address begins at 192.168.0.1, often reserved for the router. The final address in this range is 192.168.0.255, usually assigned for broadcasts. DHCP assigns addresses within the range .2 to .254. Any address outside this range belongs to another network. Since the subnet is /24, only eight host bits are available (255 minus two). Windows doesn’t simply add one to the network number like a router does; it uses irregular values such as 192.168.163.0/24. Because of this, devices acting as routers translate local requests to the internet. Clients on the same network cannot communicate with each other directly. This process is known as NAT (Network Address Translation), where multiple devices share a single public IP by creating a subnet. Sharing a network adapter on Windows is acceptable for basic internet access, but enabling file sharing will likely fail. For peer-to-peer sharing, consider using USB to Ethernet adapters and setting up a separate network. Windows may assign a default IP like 169.254.x.x/16.
Dude, I don’t need a long talk about networking basics. Those IP addresses were just samples, really. I just configured my notebook to expose its internet link. The notebook sits on the router’s network and broadcasts this connection at 192.168.137.1. That tells my desktop that it’s on the same network as the notebook—which is also part of the router’s network because it’s now functioning as a router itself, meaning it’s connected to two networks. Yes, the desktop can definitely see the notebook and communicate with it. I managed to set up a Windows share on my laptop that’s accessible from my Linux desktop. The desktop can also reach the router, since the notebook is handling requests for that private network. ~edit: Also, because I’m still online, my desktop stays linked to the internet (via LAN to the notebook, which connects to the router through Wi-Fi).
Interesting. I tried this earlier just to avoid seeming foolish, even though my home network was set to 192.168.0.0. The Windows setup for my Linux desktop looked completely different. I didn’t think about how you might still connect via protocols like SMB to other devices, but I assumed you couldn’t reach anything beyond the Windows host. That’s outside what the question is about, so it probably doesn’t matter. Damn...keep trying and hoping for the best. My life in a nutshell.
It works well enough for testing purposes. The desktop connects properly to the router's web interface, routing from its network (192.168.137.x) to the router's (172.16.4.x) and beyond. Internet access is normal. The only issue is the opposite direction—other devices on the router can't reach the desktop except through the notebook, which is directly linked. This suggests the notebook isn't functioning as a router in reverse. It might be due to a security setting I need to adjust.
I was planning to check if the sub-network Windows was set to /16. This might clarify why communication extends beyond the Windows host. It could also explain why you can't connect back except to the Windows host itself. But if your local network is 172.16.4.0, I'm really puzzled about how it's functioning.
Both networks use /24 subnets. Since they’re distinct, routing should function in either direction if the notebook is configured as the default router and connections are forwarded. When I issue a ping to 172.16.4.x from my desktop, it goes to the notebook, which is on that network, forwards the request, and handles the response. The same NAT behavior applies for outbound traffic to the Internet, except requests then go to the notebook’s default router, which in turn forwards them. I suspect the issue is the Windows firewall blocking the reverse path from 172.16.4.x to 192.168.137.x.