Virgin Media Discussion Thread

crinkleshoes · 16 Jul 2012 at 12:09

Unless the superhub is in modem mode & directly connected to the PC... then the PC firewall would come in to play.

Even then, by default - most firewalls do not block ping return (which is all the monitor is, really), including the std windows firewall.

However, the superhub does have respond to ping disabled by default - this needs to be enabled if using its routing functions.

wam7 · 16 Jul 2012 at 13:14

Awful upload speeds in Birmingham area

I am on the 100/10 package. The 100 not XXL one. Over the past few weeks I've noticed that only my upload speeds have been very poor in the Birmingham B70 area, especially in the day. Ironically the download speeds have never been better. Is anybody having the same issue?

SkeeterUK · 16 Jul 2012 at 13:15

The test i did confirms it. The win 7 firewall was blocking the TB monitor so as i have the superhubs FW on i reckon i can just keep the windows 7 one off for public and private. Then i can have a working monitor untill i dont need it then i can stick it back on.

I wonder tho. Could there be a setting in windows 7 fw that is blocking it and if so where would it be so i could disable it? If anyone knows.

crink, its not in modem mode, and it is a wired connection. I did enable and had enabled dmz respond to ping enabled for months when the monitor used to work then i never used the monitor in ages but i think it was still setup to work and then when i do want to check the data it was all red.

So for now the win fw is off for pub and priv till i can find out the cause and hopefully the routers fw is useful enough for now.

awinchurch · 16 Jul 2012 at 13:26

In case anyone is wondering whether or not the R36 update really does improve wireless I thought I would post my findings.

Before the R36 update my computer in the back bedroom was sat at 3 bars of signal and was getting speeds of around 45 - 55mbps

just tested and now im getting almost 73mbps consistant and it now hovers between 4 and 5 bars on wifi

It does appear that mu upload over wireless seems to have dropped a bit though as I'm sure I used to get between 7 and 9mbps :S

awinchurch · 16 Jul 2012 at 13:29

......

crinkleshoes · 16 Jul 2012 at 13:44

SkeeterUK said:
The test i did confirms it. The win 7 firewall was blocking the TB monitor so as i have the superhubs FW on i reckon i can just keep the windows 7 one off for public and private. Then i can have a working monitor untill i dont need it then i can stick it back on.

No... the win7 firewall had nothing to do with the monitor working or not, I'm afraid

It will have just been a coincidence that you played with these settings as it started working

I wonder tho. Could there be a setting in windows 7 fw that is blocking it and if so where would it be so i could disable it? If anyone knows.

Not by default, you would have had to disable it manually, which isn't the easiest of things to do on Win 7.

crink, its not in modem mode, and it is a wired connection. I did enable and had enabled dmz respond to ping enabled for months when the monitor used to work then i never used the monitor in ages but i think it was still setup to work and then when i do want to check the data it was all red.

I thought that would be the case...

It's more likely that your IP changed & you didn't update the monitor.

Once you updated the monitor, it started pinging again.

The only setting you have, in your specific setup, that can enable/disable the TB monitor from working is the ICMP respond checkbox in the superhub's web interface.

The packets don't go past the router, so your PCs firewall has nothing to do with it.

Most likely scenario is your IP changed

All of my PCs have firewalls disabled, only the hop between your PCs and the web really need a firewall (unless you leave your wireless unsecured, unlikely I bet).

The superhubs firewall will do all you need it to

yer_averagejoe · 16 Jul 2012 at 13:47

I've got the M 30mb package and it'd just been upgraded to 60mb. I haven't received the R36 firmware update, however. Tried turning it off for a good 15 minutes too. I thought M users were supposed to get the rollout first?

SkeeterUK · 16 Jul 2012 at 13:56

Sry crink but your wrong. I turn fw back on it goes red i turn it off it works. I have tested this and it is fact. I duno how its like this but that is the reality of it.

No the ip hasnt changed for quite some time i have checked this quite a lot for quite awhile. So no it is not the case for me.

You state "All of my PCs have firewalls disabled" is your windows firewall enabled for public and private for your lan? If not enable em and wait 15-20 mins and check your monitor see if it shows red or not.

Now if someone knows why this happens im all ears and know of a way to keep the fw on but allow the monitor to work. Yes the firewall is blocking something causing the monitor to not work so now i want to know if someone knows the windows firewall settings well enough to tell me which setting it could be and how to toggle it. I have looked and all i cant see anything specific which would cause it. Maybe its a deep setting i duno but if someone knows of somethings to try let me know.

awinchurch · 16 Jul 2012 at 14:10

yer_averagejoe said:
I've got the M 30mb package and it'd just been upgraded to 60mb. I haven't received the R36 firmware update, however. Tried turning it off for a good 15 minutes too. I thought M users were supposed to get the rollout first?

Nope yours will be upgraded on week 3 of the rollout

crinkleshoes · 16 Jul 2012 at 14:32

SkeeterUK said:
Sry crink but your wrong. I turn fw back on it goes red i turn it off it works. I have tested this and it is fact. I duno how its like this but that is the reality of it.

No the ip hasnt changed for quite some time i have checked this quite a lot for quite awhile. So no it is not the case for me.

You state "All of my PCs have firewalls disabled" is your windows firewall enabled for public and private for your lan? If not enable em and wait 15-20 mins and check your monitor see if it shows red or not.

Now if someone knows why this happens im all ears and know of a way to keep the fw on but allow the monitor to work. Yes the firewall is blocking something causing the monitor to not work so now i want to know if someone knows the windows firewall settings well enough to tell me which setting it could be and how to toggle it. I have looked and all i cant see anything specific which would cause it. Maybe its a deep setting i duno but if someone knows of somethings to try let me know.

I'm sorry matey, I know what I'm talking about here. I was a network tech for a few years

If that really was the case... every time you turned your computer off, the monitor would also stop functioning.

The packets do not get past the superhub (unless you have it in modem mode, which you don't). This is a simple technical fact.

Yeah, I have all software firewalls disabled on all PCs. The only needed firewall is one built in to a router (unless you operate an unsecured network).

SkeeterUK · 16 Jul 2012 at 14:44

Edited due to wanting to keep it more civil.

Thanks for the replies so far crink but it seems you do not want to believe it is the windows fw which it is as i have tested only this and it is the cause, dont ask me how or why but it is. I would appreciate no more replies from you tho because you dont seem to believe me and have not offered any advice in the windows fw settings to try. Also this quote from your previous post "I'm sorry matey, I know what I'm talking about here. I was a network tech for a few years

" sounds like a superior attitude response to me so i wont be asking for help on this from you.

Sp00n · 16 Jul 2012 at 14:49

It could be affecting it because you've got DMZ enabled and looks like your pc is in the DMZ (192.168.0.2).

Why do you have DMZ enabled?

SkeeterUK · 16 Jul 2012 at 14:53

Because the monitor requires it to be enabled otherwise it cant respond to the ping according to the setup guide at TB for it for the superhub.

As shown here.

http://www.thinkbroadband.com/ping/guides/routers/virgin-media-superhub-vmdg480.html

Sp00n · 16 Jul 2012 at 14:55

Have you got any port forwards set up? If so is the protocol set to TCP/UDP or BOTH?

SkeeterUK · 16 Jul 2012 at 15:07

Got a port open for utorrent on the router for both.

Sp00n · 16 Jul 2012 at 15:09

You need to change the protocol to TCP and change the DMZ back to 0.

Having the protocol as "both" stops the monitor from working but currently it's bypassing the port forwarding because the DMZ host (your pc) is accessible regardless.

I think this should sort it.

crinkleshoes · 16 Jul 2012 at 15:15

SkeeterUK said:
Edited due to wanting to keep it more civil.

Thanks for the replies so far crink but it seems you do not want to believe it is the windows fw which it is as i have tested only this and it is the cause, dont ask me how or why but it is. I would appreciate no more replies from you tho because you dont seem to believe me and have not offered any advice in the windows fw settings to try. Also this quote from your previous post "I'm sorry matey, I know what I'm talking about here. I was a network tech for a few years " sounds like a superior attitude response to me so i wont be asking for help on this from you.

I saw your original reply... I am, actually, trying to be helpful by explaining that you're looking in the wrong place.

Allowing you to know that I'm speaking from experience is not the same as an attempt to sound superior.

A very simple test is to turn your computer off - that's the same (as far as monitor is concerned) as blocking everything at your PC firewall level.

If you turn your computer off (leaving router on) and the monitor continues to function, then this would prove me correct.

If you turn your computer off and it stops functioning, this would prove you correct & that there is something very strange going on with your network...

crinkleshoes · 16 Jul 2012 at 15:18

Sp00n said:
It could be affecting it because you've got DMZ enabled and looks like your pc is in the DMZ (192.168.0.2).

Why do you have DMZ enabled?

SkeeterUK said:
Because the monitor requires it to be enabled otherwise it cant respond to the ping according to the setup guide at TB for it for the superhub.

As shown here.

http://www.thinkbroadband.com/ping/guides/routers/virgin-media-superhub-vmdg480.html

LOL!

Now that completely explains it...

Disable DMZ & enable respond to ping on WAN port.

DMZ is almost identical to modem mode, as far as the ****hub is concerned

awinchurch · 16 Jul 2012 at 15:18

crinkleshoes said:
I saw your original reply... I am, actually, trying to be helpful by explaining that you're looking in the wrong place.

Allowing you to know that I'm speaking from experience is not the same as an attempt to sound superior.

A very simple test is to turn your computer off - that's the same (as far as monitor is concerned) as blocking everything at your PC firewall level.

If you turn your computer off (leaving router on) and the monitor continues to function, then this would prove me correct.

If you turn your computer off and it stops functioning, this would prove you correct & that there is something very strange going on with your network...

It looks like as stated above that he has the DMZ set to his computer IP address and not the hub router which is 192.168.0.0

SkeeterUK · 16 Jul 2012 at 15:19

crink yes it proabably would stop working if i turned the comp off and yes its strange that it works with fw turned off in windows, it baffles me too i just duno why its like that.

Spoon, ta i will try that.