Port Forwarding / Windows Home Server / 2700HGV

[Charley_Lima]

I am a residential customer on BT Broadband Option 3. Due to the distance from the exchange, BT provided me with a 2700HGV Business Hub which did appear to handle the speeds and connection better than the Home Hub. My 2700HGV gave up the ghost and I was relegated to the Home Hub 2 [as I make great use of Broadband Talk, the HH3 was inappropriate] as BT have decided in their wisdom that residential customers no longer receive Business designated kit. I have an HP Mediasmart Home Server which requires Ports 80, 443 and 4125 to be open to permit remote connection and web site access. This worked well with my old 2700HGV but does not work with the HH2 as while this router lists UPnP and Port Forwarding in its functions, they don't. I have now managed to buy a 2700HGV, set it up in exactly the same way as previously but can get nowhere. I had a feeling that the BT MacAfee firewall might be the problem and disabled this with no difference. If I choose DMZ mode in the router, a new IP address is given to the Home Server but I am then denied access. Any ideas would be greatly appreciated. To post here, I should point out that I also have a business domain account.

[MHC]

Have you done a full factory reset on te new hub?   and have you matched EVERY setting from the old one?

Is te hub you have purchased of te same build standard - both hardware and software as the old one?   If not you may need to get a firmware update.

[Charley_Lima]

After the reset, the software updated to the version I had previously after a couple of days.

The build and firmware are identical.

The only difference is that I have migrated from AVG to MacAfee but while it didn't work with the MacAfee firewall disabled, the ports I require are checked in the MacAfee firewall as being permitted.

Even if 4125 was blocked, 80 and 443 would allow me to access the web site and they both show as 'open' on a variety of software scanners.

[kimura]

Also try disabling the Windows firewall. Sometimes those windows automatic updates can cause this.