deleted

[Q48VW]

deleted

[drgeoff]

I very much doubt that port forwarding on your router has any bearing on your troubles. On every home router I have encountered the port forwarding only affects traffic between the LAN and the WAN. All the LAN ports connect to a simple switch and there is no traffic control between them whatsoever.

The IP address of your RPi is 192.168.137.179. I'd wager that your other PCs and router are not 192.168.137.x.

From http://windows.microsoft.com/en-gb/wind ... on-sharing
"Do not use ICS on a network with domain controllers, DNS servers, gateways, or DHCP servers. And don't use ICS on systems configured for static IP addresses." Isn't your router a gateway and a DHCP server?

Perhaps http://windows7themes.net/networking-qu ... perly.html is what you need? I can't say for certain as I've never had occasion to do what you are attempting.

[FTrevorGowen]

Hello all, I recently purchased a Model B Raspberry Pi and am having some troubles with the network.

OS: Raspbian "wheezy"
SD: 32gb micro with an adapter

To begin, I should mention that my Pi's ethernet cable is connected to the ethernet port on the motherboard of my PC.
...

Presumably you have a good reason (eg. no spare ethernet ports elsewhere) for trying to do things this way but you are making very difficult for yourself. The simplest way to achieve all the (inter-connected) networking you desire is to either:
1) Plug the Pi into a spare LAN port on your router (if you have one).
2) (Better still) invest in a cheep and cheerful 5-port network switch and connect the Pi, your PC and that to the router.
Assuming the Pi and the PC both then use DHCP to get their IP addresses from the (server on the) router then all are on the same local network and all can (gateway through) see the internet (WAN) via the router. There are 9 machines (not counting mobile 'phones via WiFi) that connect to each other (and the 'net) via this "hardware-based" approach in our household - four of them being Pi's, the others a mix of Linux, Windows and "dual-boot" machines. The nearest I've come to doing things "your way" was when I had a "Smoothwall Linux" PC as a hardware firewall between other machines and, what was then, a "single point" connection (ie. not a router) to my ISP in the early days of "broadband" (it having been a "dial-up" connection [2nd. 'phone line] previously).
Trev.

[pluggy]

The shared internet connection is another NAT connection and the Pi will be on a different subnet to the rest of your network. Th Pi will be able to 'see' the other machines on the network but not vice versa. As as been said, you are making life very difficult for yourself. I'd plug the Pi directly into your router (or use a wireless adaptor if the router has wireless cababilities) wherever it may be and set it up via ssh or something.

[Q48VW]

deleted

[drgeoff]

Now the only troubles I'm having are the actual port forwarding. I setup the forwarding on the actual address (192.168.0.32) from 80 to 80, 443 to 443, and 22 to 22 for SSHing. I still cannot reach my Apache2 server outside the network or SSH. I followed this man's instructions about setting up the server names, local hosts, and fixing the "127.0.0.1 reliable address" problem, so now my router recognizes the Pi on the ethernet cables as '.0.32. http://my-music.mine.nu/images/rpi_rasp ... _setup.pdf

You did read and understand all of C3.1?

[Q48VW]

deleted

[Q48VW]

deleted

[pluggy]

Somewhere between very highly unlikely and impossible without seeing how you configured the gateway/router on the way in. Unless you have programmed the Pi to pull stuff off the other machines and serve it up through the web server.......

[Q48VW]

deleted

[pluggy]

Its mainly how you've configured the port forwarding on the router that controls how secure it it. If its only forwarding ports 80/443 to the Pi's internal IP adddress, no problem, but its possible to configure other ports to go elsewhere and I wouldn't have it forwarding port 22 if you can avoid it, because if they can gain control of the Pi through it, there could be a big problem.