Well I cleared the Domain name from the router did nothing just reappeared
after I rebooted the router. Called Brighthouse Cable they report no
problem but gave me some IP addresses to try instead of letting windows
doing it automatically they did not help. Reloaded XP to see if the
settings were they same as Windows 7 and for the most part they are
unchanged. Windows 7 has some extra settings in the ISP connection
properties but even with them turned off still no dice. Unless there is
some mystery setting that could be selected I'm at a loss.
"Paul" wrote in message
"Paul" wrote in message
For what it is worth, my router has a "LAN Settings" window
and "Local Domain Name (optional)". I leave the Local Domain Name
blank. What I was trying to do, is have the router just use
DHCP to automatically fetch the public IP address, and the
two ISP provided DNS server addresses.
Your router got that "twmi.rr.com" value somehow. Perhaps the
router is a rental that comes with the service, and that
dialog was populated by RoadRunner before shipping it to
you ? I'd write down the current settings, and experiment
with changing it.
Purely for your amusement, there *is* a way for a router
settings to get changed
But since twmi.rr.com looks
legit, I wouldn't panic just yet. This highlights the need
to use a real password (not the default password) with any router.
When you get a router, change the administration password
on it immediately, and place a sticky paper on the router
casing so you won't forget.
http://blog.washingtonpost.com/securityfix/2008/06/malware_silently_alters_wirele_1.html
Have you tried this ? And did the BNSF site appear ?
http://170.49.49.66
No just got the browser statement could not connect. IE diagnoses reports
nothing is wrong. It is a store bought router so I'm not sure where the
twmi.rr.com came from??
So
http://170.49.49.66 doesn't work ? That should have worked as
it wouldn't need to use DNS to get there.
Some software uses "reverse translation" before carrying out a protocol.
I used to have problems with that, for network equipment without DNS
entries. Some OSes do the reverse translation as a means of detecting
spoofing. I thought the browser test, of the form we're testing,
should work. But it might not work on all OSes, as for security
reasons some may want to reverse translate and verify what
symbolic address that is. If an OS does the reverse translation, and
the answer is "there is no translation for 170.49.49.66", then the
OS would conclude that it shouldn't carry out the request. In your
case, whatever is doing DNS for you at the ISP, may not have an
entry for 170.49.49.66 . I didn't think browsing in Windows, would
involve such a check.
I'd try experimenting, by removing the optional LAN domain in your
router, and see if a different DNS server gets used automatically.
If things become worse, you can always put it back.
Your ISP *can* mess around, and do things to the DNS entries
if they want, preventing you from getting to certain sites.
This is one of the reasons, occasionally, there is a need to
verify with a third party DNS lookup, to see what the
address is supposed to be. Using OpenDNS or Google DNS are
options (your computer consults Google instead of the ISP),
but if an ISP really wants to block a site, they can also
filter the IP address itself. ISP networking equipment
has become quite powerful, with all sorts of
capabilities, such as detecting and stopping certain
protocols put by the user on arbitrary ports and so on.
The network equipment now, can look into the payload of
the packets, for hints about what the user is doing
(BitTorrent) and respond in some way. So just about anything
is possible now, in terms of networking problems.
To give an example, a couple years ago, my ISP had just
received such a networking box, and were using it to slow down
BitTorrent. But they also managed to "splatter" port 80 HTML traffic,
inserting RST packets where they didn't belong. That causes
web browsing problems, where a week ago there were none. They
eventually figured it out.
Paul
