Bt Infinity With Hh3

[Lwillis]

not had any issues naming it CCTV or DVR

[datadiffusion]

Good old HH3 Type A i'd guess...what a crock of brown stuff

 

https://community.bt.com/t5/Other-Broadband-Queries/Port-forwarding-and-Loopback-DO-work-YMMV/m-p/525363

 

Just one of the many threads, I have picked up a few HH3 Type B when out and about where customers have switched BB provider so always useful to carry about as it takes 2 mins to swap and sorts the issue

 

Draytek are fantastic but as with swapping the original BT gear to any other router if a BB issue comes up BT blame installer

 

HH5 is 100% , customers can ring BT and request upgrade to HH5, worth looking at equipment on inital survey and recommending its upgraded prior to install

 

Had no idea there was an A and B problem for HH3 (but there clearly is!) just like HH2 - except there didn't BT get forced to do a 100% recall?

 

HH5 is free if customers moan? Yes, wish I'd checked, except, I did just not knowing about the problems

 

 

 

I spoke too soon!  I have discovered a definate problem with the port forwarding on the BT Home Hub 3B.  In general, what wrote in my original posting is correct - it works. But only if you forward a single port at a time.

 

Even more interesting! Will make a few changes when I go back.

 

Thanks for all your replies by the way, its been helpful. So far the customer is chuffed with the camera quality and not too bothered about remote access, as that was never really what they wanted the system for (they have a problem with peoples sat navs taking 4x4s over a closed off road thats been landscaped and footpathed)

[sixwheeledbeast]

Another thing I have just thought could cause this issue is an incorrect Gateway IP on the DVR.

Worth double checking.

I can confirm you can find bugs in router firmware, I found with some brands (D-Link is one IIRC) you can have issues forwarding TCP/UDP in the same rule.

[datadiffusion]

Another thing I have just thought could cause this issue is an incorrect Gateway IP on the DVR.

Worth double checking.

I can confirm you can find bugs in router firmware, I found with some brands (D-Link is one IIRC) you can have issues forwarding TCP/UDP in the same rule.

 

Being lazy I did leave the TCP/UDP as 'all' initially, but soon changed it to TCP only.

 

I did check on the DVR and the gateway was 192.168.1.1 so that is correct for an unmodified hub,, isn't it?

[james.wilson]

Most hh are 192.168.1.254

what ip address were u using to program the hub?

[datadiffusion]

Most hh are 192.168.1.254

what ip address were u using to program the hub?

 

Sorry thinking of my own, that rings a bell, I think it was that now.

 

I just used bthomehub.home to prog, I am actually certain it did end .254 on the DVR readout.

[Cubit]

Most hh are 192.168.1.254

what ip address were u using to program the hub?

All the BT Routers i go to (fookin hundreds of them) have that as the default.

[21ninja]

I have had the issue where calling it cctv or dvr brings up the bt cctv. Took a minute to think of a solutions. Rename.

[9651]

ive not had that, but noted.

[datadiffusion]

Went back to site this Am

Changed the name from Cctv Dvr to just dvr

Changed the port forwarding so rather than one list of 3 ports, it was 3 separate services

Avoided using the name Cctv in any of the above

No reboot, worked immediately... Ffs bt, what a load of junk.