Windows 7: Router disabled in "Network"

Hi, I seem to have an odd problem with my router and Windows 7 64. I've recently gotten this new Thomson TG782 router which supports uPnP. It is enabled in the router and it is visible in the "Network" under "Network Infrastructure" listed as Thomson TG782 (1005NT2HL).

When I just installed these Windows this -connection- was actually enabled, because right clicking it gave a "Disable" option. I've since installed network drivers (Realtek RTL8111C) and the Realtek network diagnostic utility, and Outpost Pro Firewall 64.



Now, the connection is disabled, and trying to enable it gives a "Connection Failed!" message.
I'm not sure which of these things killed it, but I do believe uPnP is not working properly now (how can I test this?).

I have a parallel Windows XP installation with the same firewall, updated drivers (albeit for XP), and it works fine there (though the implementation is a bit different I assume).

How would I go about fixing this? I've tried turning the firewall off but it didn't seem to make a difference. I'm sure there is some setting or so blocking it.

Disabling the Outpost firewall usually won't cut it. You may need to uninstall it completely. Although I'm confused as to why you have a router in the middle of your network when it should be the first thing that everything else is connected too.

There are no other PCs on the network, just the one I'm using. The router is also a modem, I have a cable from the motherboard going into the router so I can have internet access, and another one downstairs going into the router for IPTV (but that's irrelevant). That's the only things I have, just this one router/modem.

I'm not sure why the firewall would block the uPnP gateway, like I said I have XP in dual boot with the same firewall and it works there without a hitch. Well, at least it says it's enabled.

Here is whats required for the outpost firewall to work properly with Windows 7. Hope this helps.

UPnP should work fine through the current and new version of Outpost as long as:

1. TCP Port 5000 (UPnP) is allowed for svchost.exe (XP, may be another executable on 2000, 98, etc.)

2. UDP Port 1900 (SSDP) is allowed for svchost.exe (XP, may be another executable on 2000, 98, etc.)

3. You have opened the necessary ports in Outpost itself to allow the necessary traffic for voice and video. These functions generally require a wide port range.

Following steps one and two should allow Windows the ability to perform the necessary UPnP negotiation to setup the NAT router to allow the Messenger traffic. And following step three should ensure no interference with the operations of your instant messaging client from Outpost.

That is my opinion and knowing your current situation, I really hope it works for you because I highly doubt that the next version of Outpost will allow an application to configure it's rules through the use of UPnP. UPnP configuration is generally applied to hardware devices like NAT routers anyway, so the three steps above really should work for you.

Again, that is my opinion, let's see what the developers have to say.

Source> Will version 2 be UPnP aware [Archive] - Outpost Users Support Forum

Didn't really do much, at least as far as enabling the connection goes. To be honest, I don't really care if that connection is disabled or not, I'd just like to make sure apps can open ports when they need them and that uPnP is working, especially considering this firewall is on.

Another thing, if the firewall in the router is set to disabled, then there is absolutely no point in opening ports anyway, or is there? Currently it is set to standard (allows outgoing, blocks incoming).

That is straight off the outpost forum, I'm not sure what more I can do here other than to mention that uninstalling the outpost firewall would be my first choice.

Which firewall for Win 7 64 would you recommend then?

The built in Windows 7 firewall is very good and works extremely well for most of us.