Superhub One PC cannot access some sites - Page 2

navman · 03-08-2011, 14:27

Nope all set to home network...... I am glad it is not something simple that I had overlooked... Thanks for all the ideas folks

kwikbreaks · 03-08-2011, 14:34

I guess that makes some sort of sense because it probably wouldn't work with any sites if it was incorrect.

There are two puzzles here - why only one PC (and I suspect the fact it's Win 7 is somehow the reason) and why only some sites - especially as the DNS resolution and routing look good.

navman · 03-08-2011, 14:49

I agree... While I may not be the sharpest thing as far as DNS setting are concerned I have looked about a lot in the internet to find a solutions. As I said if I put a proxy in it works fine. I have tried FF, IE and Chrome, run virus and trogan checkers until they come out of my ear... :-)

Dai · 03-08-2011, 15:22

Quote:

Originally Posted by kwikbreaks

why only some sites - especially as the DNS resolution and routing look good.

That's the bit that's baffling me as well. I knew it was a long shot trying different dns servers but had to be done.

All I can think of now is either firewall or HOSTS file, but surely either of those would also block browsing via the proxy?

navman · 03-08-2011, 15:38

I have turned off the firewall to see if it was that... :-) No real knowledge about the host file...

Dai · 03-08-2011, 16:56

Quote:

Originally Posted by navman

I have turned off the firewall to see if it was that... :-) No real knowledge about the host file...

Look in C:/Windows/System32/Drivers/etc

Yes, the folder is really called "etc"

There should be a file in there called hosts. You can open it in Notepad or any text editor although it will need to be manually selected as the file has no .txt extension. The raw unchanged hosts file should look like this:

----------------------------------------------------------------------------

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

------------------------------------------------------------------------

navman · 03-08-2011, 17:05

This is the contents of mine....

127.0.0.1 localhost
::1 localhost
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost

General Maximus · 03-08-2011, 17:07

Quote:

Originally Posted by kwikbreaks

One thing you can try but I doubt it will help tbh is to right click on the connection icon in the system tray and select "repair". Note any error messages that may appear.

Is it only some sites that fail? How exactly do they fail? What messages?

---------- Post added at 10:13 ---------- Previous post was at 10:10 ----------

That's one of the (many) features the Superhub doesn't support.

as far as I am concerned then VM shouldn't legally be allowed to call it a router. What sort of [mod:edit] routers [mod:edit] dont let you specify your dns servers?

qasdfdsaq · 04-08-2011, 22:05

Quote:

Originally Posted by kwikbreaks

It sounds to me like your network type may not be set to "Home network" and your firewall is blocking you from connecting.

Windows firewall places no controls or restrictions on connecting to anything. It only ever affects inbound connections.

---------- Post added at 23:05 ---------- Previous post was at 23:03 ----------

Quote:

Originally Posted by General Maximus

as far as I am concerned then VM shouldn't legally be allowed to call it a router. What sort of [mod:edit] routers [mod:edit] dont let you specify your dns servers?

Ones that obtain them automatically. 99%+ of home users won't ever change the DNS settings on their router, nor want to.

That said, the rest of us who want/need to change them for whatever reason, can't, but then again it's not far off wanting to use another device but they won't let you either.

kwikbreaks · 05-08-2011, 08:52

Quote:

Originally Posted by qasdfdsaq

Windows firewall places no controls or restrictions on connecting to anything. It only ever affects inbound connections.

Oh yes it can....

[img]Download Failed (1)[/img]

but only at program level admittedly.

Kymmy · 05-08-2011, 09:01

Can I remind members that the swear filter is there to stop members from breaking the rules and not as a shield to hide your swearing behind. Any more swearing on this family friendly forum will incur infractions whether or not the word is obfuscated out and the meaning is still clear.

qasdfdsaq · 05-08-2011, 16:24

Quote:

Originally Posted by kwikbreaks

Oh yes it can....

but only at program level admittedly.

That's still inbound connections, it has nothing to do with outbound.

kwikbreaks · 05-08-2011, 17:12

qasdfdsaq · 06-08-2011, 11:21

OK, fair point. If you go to advanced settings and go through a 15 step process to create a custom rule, then you can block outbound connections.

None of the options in control panel or the defaults, nomatter what the user clicks will do this however, so it won't be affecting anyone who hasn't gone through a very deliberate and long advanced rule creation process...

kwikbreaks · 06-08-2011, 11:28

When you connect to a new router (as he did) Win 7 detects it and asks you what network type it is. If you screw up and say it's a public network (easy to do in a rush as I've been stupid enough to do it myself which is why I remembered it can cause problems but not exactly what at the time I suggested checking) then by default it will block the browsers from accessing the internet as you can see in the first picture where it isn't allowing Firefox access.

It wasn't his problem and the symptoms as it happened didn't match but saying the Windows firewall is only applicable to inbound connects is plain wrong.