Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Hotmail Logout redirect


  • Please log in to reply
6 replies to this topic

#1 san2222

san2222

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:08:22 AM

Posted 17 May 2011 - 06:42 AM

Hi, i have been noticing that once i logout from my hotmail account, the browsers redirect me to a URL of "http://hmit.ww.msn.com/logout.aspx?mkt=en-IE".

Firefox shows that the DNS server may be down with the following error :Network Error (dns_server_failure)

Your request could not be processed because an error occurred contacting the DNS server.
The DNS server may be temporarily unavailable, or there could be a network problem.


I don't think it's a DNS problem as i have tried Vista to automatically assign DNS address and manually entering OpenDNS servers. Still the problem persists.

So say what friends?

I have Avast 6 installed. Ran MRT.exe from Microsoft yesterday, but found nothing.

Edited by san2222, 17 May 2011 - 06:45 AM.


BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:07:22 AM

Posted 21 May 2011 - 05:25 AM

Are you using any special DNS Servers?

I would suggest using your ISP's DNS Servers.

#3 san2222

san2222
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:08:22 AM

Posted 21 May 2011 - 05:44 AM

this happens with both the native ISPs Server as well as the OpenDNS servers.

A simple Google search , led me to a french forum, with a user having similar problem :
http://forum.touslespodcasts.com/telecharger/securite/redirection-vers-pages-infectees-451016/messages-1.html

but its in french, and i can't follow it.

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:07:22 AM

Posted 21 May 2011 - 01:09 PM

Here is my nslookup:

Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
hmit.ww.msn.com canonical name = hmit.ww.itm.asp.msn.com.nsatc.net.
Name: hmit.ww.itm.asp.msn.com.nsatc.net
Address: 65.55.84.38

C:\Users\cryptodan>nslookup hmit.ww.msn.com
Server: nsphil01.verizon.net
Address: 71.242.0.12

Non-authoritative answer:
Name: hmit.ww.itm.asp.msn.com.nsatc.net
Address: 65.55.84.38
Aliases: hmit.ww.msn.com

The server exists. Its time either change ISP's or talk to your ISP to check their DNS Servers.

#5 san2222

san2222
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:08:22 AM

Posted 22 May 2011 - 11:15 AM

Why would I choose to change my ISP? What kind of issue is this? I tried using Proxys such as HotSpot and Ultra, still the same issue. It may sound rude for asking so many questions..sorry :(

#6 san2222

san2222
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:08:22 AM

Posted 22 May 2011 - 12:01 PM

I checked out netstat command with -a and -an parameters. They show a lot of active connections. Here it is:


Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:80 BigBro-PC:0 LISTENING
TCP 0.0.0.0:135 BigBro-PC:0 LISTENING
TCP 0.0.0.0:445 BigBro-PC:0 LISTENING
TCP 0.0.0.0:3389 BigBro-PC:0 LISTENING
TCP 0.0.0.0:49152 BigBro-PC:0 LISTENING
TCP 0.0.0.0:49153 BigBro-PC:0 LISTENING
TCP 0.0.0.0:49154 BigBro-PC:0 LISTENING
TCP 0.0.0.0:49155 BigBro-PC:0 LISTENING
TCP 0.0.0.0:49159 BigBro-PC:0 LISTENING
TCP 127.0.0.1:5939 BigBro-PC:0 LISTENING
TCP 127.0.0.1:9421 BigBro-PC:0 LISTENING
TCP 127.0.0.1:9422 BigBro-PC:0 LISTENING
TCP 127.0.0.1:9423 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12025 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12080 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12080 BigBro-PC:52511 ESTABLISHED
TCP 127.0.0.1:12080 BigBro-PC:52513 ESTABLISHED
TCP 127.0.0.1:12080 BigBro-PC:52515 ESTABLISHED
TCP 127.0.0.1:12110 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12119 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12143 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12465 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12563 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12993 BigBro-PC:0 LISTENING
TCP 127.0.0.1:12995 BigBro-PC:0 LISTENING
TCP 127.0.0.1:49156 BigBro-PC:49157 ESTABLISHED
TCP 127.0.0.1:49157 BigBro-PC:49156 ESTABLISHED
TCP 127.0.0.1:52037 BigBro-PC:52038 ESTABLISHED
TCP 127.0.0.1:52038 BigBro-PC:52037 ESTABLISHED
TCP 127.0.0.1:52039 BigBro-PC:52040 ESTABLISHED
TCP 127.0.0.1:52040 BigBro-PC:52039 ESTABLISHED
TCP 127.0.0.1:52498 BigBro-PC:12080 TIME_WAIT
TCP 127.0.0.1:52511 BigBro-PC:12080 ESTABLISHED
TCP 127.0.0.1:52513 BigBro-PC:12080 ESTABLISHED
TCP 127.0.0.1:52515 BigBro-PC:12080 ESTABLISHED
TCP 192.168.254.1:139 BigBro-PC:0 LISTENING
TCP 192.168.254.1:49178 a541he:https CLOSE_WAIT
TCP 192.168.254.1:49179 a541he:https CLOSE_WAIT
TCP 192.168.254.1:52397 74.125.230.138:https TIME_WAIT
TCP 192.168.254.1:52430 bru01s01-in-f97:https TIME_WAIT
TCP 192.168.254.1:52489 www-11-01-tst1:https TIME_WAIT
TCP 192.168.254.1:52491 www-11-01-tst1:https TIME_WAIT
TCP 192.168.254.1:52492 a88-221-217-138:http TIME_WAIT
TCP 192.168.254.1:52493 www-11-01-tst1:https TIME_WAIT
TCP 192.168.254.1:52494 www-11-01-tst1:https ESTABLISHED
TCP 192.168.254.1:52495 www-11-01-tst1:https TIME_WAIT
TCP 192.168.254.1:52496 www-11-01-tst1:https TIME_WAIT
TCP 192.168.254.1:52497 api-read-10-02-snc5:https ESTABLISHED
TCP 192.168.254.1:52499 173:http TIME_WAIT
TCP 192.168.254.1:52501 173:http TIME_WAIT
TCP 192.168.254.1:52502 a184-26-194-110:https ESTABLISHED
TCP 192.168.254.1:52503 a184-26-194-110:https ESTABLISHED
TCP 192.168.254.1:52504 a184-26-194-110:https ESTABLISHED
TCP 192.168.254.1:52505 a184-26-194-110:https ESTABLISHED
TCP 192.168.254.1:52506 79.140.95.168:https ESTABLISHED
TCP 192.168.254.1:52507 79.140.95.168:https ESTABLISHED
TCP 192.168.254.1:52508 79.140.95.168:https ESTABLISHED
TCP 192.168.254.1:52509 a184-26-194-110:https ESTABLISHED
TCP 192.168.254.1:52510 a184-26-194-110:https ESTABLISHED
TCP 192.168.254.1:52512 fxfeeds:http ESTABLISHED
TCP 192.168.254.1:52514 a88-221-217-169:http ESTABLISHED
TCP 192.168.254.1:52516 a88-221-217-138:http ESTABLISHED
TCP [::]:80 BigBro-PC:0 LISTENING
TCP [::]:135 BigBro-PC:0 LISTENING
TCP [::]:445 BigBro-PC:0 LISTENING
TCP [::]:3389 BigBro-PC:0 LISTENING
TCP [::]:49152 BigBro-PC:0 LISTENING
TCP [::]:49153 BigBro-PC:0 LISTENING
TCP [::]:49154 BigBro-PC:0 LISTENING
TCP [::]:49155 BigBro-PC:0 LISTENING
TCP [::]:49159 BigBro-PC:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:10316 *:*
UDP 127.0.0.1:49705 *:*
UDP 127.0.0.1:51159 *:*
UDP 127.0.0.1:55150 *:*
UDP 127.0.0.1:62767 *:*
UDP 192.168.254.1:137 *:*
UDP 192.168.254.1:138 *:*
UDP 192.168.254.1:1900 *:*
UDP 192.168.254.1:55149 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::1]:1900 *:*
UDP [::1]:55147 *:*
UDP [fe80::3899:1079:a39d:ad8b%10]:1900 *:*
UDP [fe80::3899:1079:a39d:ad8b%10]:55148 *:*
UDP [fe80::f04f:8dba:3b80:6647%9]:546 *:*
UDP [fe80::f04f:8dba:3b80:6647%9]:1900 *:*
UDP [fe80::f04f:8dba:3b80:6647%9]:55146 *:*

Edited by san2222, 22 May 2011 - 12:37 PM.


#7 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:07:22 AM

Posted 22 May 2011 - 01:16 PM

The issue is that your ISP has poorly configured DNS servers, and it is not providing correct name resolution.


nslookup hmit.ww.msn.com 71.242.0.12


And youll see what I mean.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users