jwaterfield wrote:
> Great, thanks for all the feedback! I'm trying to connect to the router
> through my browser and configure it that way, like a few of you
> suggested. It hasn't worked yet, but I'll play with the
> internet/firewall settings more tomorrow and see what happens. I'll let
> y'all know how it goes.
>
> Thanks again!!!
>
If you're trying to do this with a wireless connection, then you may
have some problems with just making a wireless connection. You should be
using a wire connection on a LAN port to configure the router for
wireless connections with wireless machines.
You should always have a machine that can connect to the wire/wireless
Access Point router that uses a wire connection to the router, as you
can have problems on the wireless side that you may need to trouble
shoot. If you got a problem on the wireless that's preventing a
connection for a wireless machine, then you have to go with a wire
connection.
A FW works in two ways, you can manually open inbound ports on the FW to
allow unsolicited inbound traffic through the FW to the machine.
The case of opening those Windows network ports on the PFW. Traffic from
a machine on the LAN (Local Area Network) can reach another computer on
the LAN that can share resources, with both FW(s) with their respective
ports for networking manually opened or auto opened, a setting on the
PFW configuration, which must be enabled.
The other way a FW works is if any program on the machine behind the FW
sends outbound traffic to a remote machine on the LAN and that other
machine is not blocking the inbound traffic to it, the port is open on
the FW on the remote computer. The machine and its FW that sent the
outbound traffic to the remote machine, its FW will open the inbound
ports automatically for the machine that sent the outbound traffic and
allow the inbound traffic back.
That's called a solicitation for traffic and the FW on the machine will
allow all inbound traffic back to the FW, if a solicitation has been
made by sending out bound traffic. All unsolicited inbound traffic is
blocked.
Allowing unsolicited inbound traffic, which is the case of opening those
ports for the Windows networking between the machines manually, must
done to allow unsolicited through the FW on the ports, because each
machine is not initiating the solicitation for that traffic by sending
outbound traffic and the FW would block that unsolicited inbound traffic
coming to it.
In your case of the machine behind the PFW on the LAN, the FW is not
blocking any traffic either way inbound or outbound, since the browser
on the machine has made the solicitation and the router is sending back
inbound to it.
So the PFW I don't think is the issue, but you can drop it, if you like.
The problem with the PFW will come-up when trying to make the machines
contact each other on the networking if the FW(s) are not configured
properly.
BTW, the router works in the same way as the PFW. Solicited traffic from
a machine that has sent outbound to a remote IP a Wide Area Network-IP
or WAN IP, the router will open the inbound port to allow the traffic to
reach the machine. Any unsolicited inbound traffic coming to the router
is blocked.
Sometimes you may have to open a port on the router to allow unsolicited
inbound traffic to reach a machine. It's called port forwarding.
http://www.homenethelp.com/web/expla...arding-dmz.asp
Of course, you would need to open the same ports on the PFW in order for
the unsolicited inbound traffic coming through the router to reach the
computer.
Keep the machine out of the DMZ.