gateway.2wire.net vs 192.168.1.254

Started by LesD, Oct 25, 2008, 21:30:59

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

LesD

Calling all 2Wire experts,

I have been discovering the "delights" of Vista on a new machine I built getting on for a month or more ago. Slowly but surely I have been pealing off lots of "features" I don't like or even want and sooner or later I will have XP back without having to install it!   ;)

My intention was to migrate from my tried and tested XP Pro machine to my new machine with Vista Home Premium on it. Within days (hours most probably) I knew this was not going to happen in a hurry!  :thumbd:

So I invested in an Aten DVI KVM switch (CS52D) a very nice piece of kit if a bit pricey compared to some of the analogue one that you can get.

Well yesterday against my usual diligent practice I was persuaded to open an email with something nasty in it and my PREVX malware software went into Red alert and insisted I do a Cleanup straightaway, which I did and PREVX has the machine, my older well loved tried and tested XP Pro machine clean and healthy again I am pleased to report.

As what I assume is a consequence of this Cleanup I find that I can no-longer access my 2Wire (BT Home Hub) login page with:

http://gateway.2wire.net/xslt?PAGE=J03&THISPAGE=A02_POST&NEXTPAGE=J03

I have to use instead the IP address as follows:

http://192.168.1.254/xslt?PAGE=J03&THISPAGE=A02_POST&NEXTPAGE=J03

OK no big deal I know but why is this?  ???

The Vista machine that was not involved in the malware incident will still access the 2Wire using:

http://gateway.2wire.net/xslt?PAGE=J03&THISPAGE=A02_POST&NEXTPAGE=J03

so it is not a router issue as far as I can see.

I have check the Windows\System32\drivers\etc\Hosts file and the:

192.168.1.254 gateway.2wire.net

lookup is not present on either machine. I know I could add it to the hosts file on the XP box to get this working again but that would not solve the mystery of why this has happened!  :(

So common who's going to cheer me up and explain this little phenomenon to me?  :)
Regards,

Les.


Lance

Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

I am sure your on the right lines something wonky with regard to DNS lookup for a local address.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

The only thing I can think of, Les, is that you've defined the DNS addresses manually in Windows.

The DNS needs to be the router, otherwise gateway.2wire.net will not work. When the DNS is set as the router, it won't actually pass on gateway.2wire.net to the real DNS'. But if you definite IDNet's DNS' in Windows directly, the request is bypassing the router and going straight to IDNet's DNS', which won't find the site.

Steve

I always thought that the first step in a DNS request was to the local resolver and then on to the selected DNS server. :)
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Only if the router is defined as the DNS. If you have actually defined IDNet's DNS' in Windows, it'll bypass the local resolver.

LesD

I have not knowingly changed the Windows DNS but the Cleanup process may have done.
In the 2Wire I have it set to get the DNS automatically so this should be IDnet's DNS and as I say the Vista machine has no problem with the name rather than the IP address.

Where do I get at the Windows DNS on the XP box?
Regards,

Les.


Rik

Right-click the network icon in the system tray, Les, select Status > Properties > TCP/IP > Properties and it's on general tab.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Quote from: LesD on Oct 26, 2008, 11:32:17
I have not knowingly changed the Windows DNS but the Cleanup process may have done.
In the 2Wire I have it set to get the DNS automatically so this should be IDnet's DNS and as I say the Vista machine has no problem with the name rather than the IP address.

That's absolutely fine, Les. The router will have got IDNet's DNS already anyway, so you'd only want to manually define on the router if you wanted to use OpenDNS, for example.

Quote from: LesD on Oct 26, 2008, 11:32:17Where do I get at the Windows DNS on the XP box?

See Rik's reply. ;)

LesD

Thanks Rik,

I got there myself and was coming back to say I have fixed it when I saw your Post.

So for the record at Internet Properties (TCP/IP)

The selection was:
Use the following DNS server addresses

85.255.112.237

Where ever or what ever that one is!

I set this back to Automatic detection and the gateway name URL works again.

Next quest is to find out where 85.255.112.237 came from.

It might be a PREVX one in the Cleanup or a left over from the bug.  :eek4:
Regards,

Les.


Sebby

I've got a feeling that's a dodgy DNS, Les. A quick Google shows that DNS on a lot of anti-malware forums. If it is, it could be seriously compromising your security. I'd set it to automatic right away!

LesD

Quote from: Sebby on Oct 26, 2008, 11:45:45
I'd set it to automatic right away!

Too true Sebby I did that as soon as I discovered it.  :phew:
Regards,

Les.


Sebby


LesD

#13
Answer yes Sebby see above or below.  ;)


Quote from: LesD on Oct 26, 2008, 11:44:13
Thanks Rik,

I got there myself and was coming back to say I have fixed it when I saw your Post.

.....................................

I set this back to Automatic detection and the gateway name URL works again.



Mind you I thought I would take a look at the (TCP/IP) DNS setting on the Vista machine but can I find it!
The h*ll I can! I have come up with the word "Vistery" to embrace all the new name/home/locations and downright mysteries Vista has confounded me with to date. Not the Post to elaborate on this here though!

Regards,

Les.


Sebby


LesD

#15
Quote from: LesD on Oct 26, 2008, 11:58:01

Mind you I thought I would take a look at the (TCP/IP) DNS setting on the Vista machine but can I find it!
The h*ll I can! I have come up with the word "Vistery" to embrace all the new name/home/locations and downright mysteries Vista has confounded me with to date. Not the Post to elaborate on this here though!



Ah Eureka I have have last discovered the contorted Route Vista makes you follow through:
Control Panel
via
Network and Sharing Center (with Centre spelt wrong!)
then
Manage Network Connections
to see
Local Area Connection

A Start - Connect to gets me there in XP. Oh joy!

Oh yes like a lot of the contortions I find myself going through in Vista it is so easy to forget why you started by the time you get there so I am adding this edit to say that at the two TPC options I eventually found the DNS was set to automatic in both.  :thumb:
Regards,

Les.


Rik

It's probably wise to write a big sign before you begin, Les. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Mytheroo

 __________________________________
|                                                     |
|   Vista investigations in progress         |
|                                                     |
|     DO NOT approach the operator       |
|                                                     |
|     DO NOT offer your 2peneth worth   |
|                                                     |
|     DO NOT feed the techs                 |
|_________________________________|
There are 10 kinds of people, those who understand binary and those who don't.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.