Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: Router Interface.  (Read 7577 times)

UncleUB

  • Helpful
  • Senior Kitizen
  • *
  • Posts: 29543
Router Interface.
« on: December 11, 2009, 02:07:18 PM »

Not sure this is the right section to post in.

I have just looked at the inernet and network log viewer in McAfee and al the numbers are 192.168.1.254 which is the O2 WirelessBox.lan ICSLAP,but I have one entry dated the 7th Dec which scared me a bit.

The number is 207.46.125.254 no host name,but under where it says event information it says, UDP port 53963.

The details say,

A computer at 207.46.125.254 has attemped an unsolicited connection to UDP port 53963 on your computer.

Thereare some options to either add this IP as trusted,add as standard,ban this IP or trace this IP.

I tried doing a trace but nothing came up?
Logged

tuftedduck

  • Senior Kitizen
  • ******
  • Posts: 29658
  • Router Luvvin Duck
Re: Router Interface.
« Reply #1 on: December 11, 2009, 02:42:21 PM »

This is possibly something to do with Windows updates..........do you have them set to automatice ?

The IP address is traced to the Microsoft Corporation, in which case it is probably nothing to worry about.  :)
Logged

camallison

  • Kitizen
  • ****
  • Posts: 1357
Re: Router Interface.
« Reply #2 on: December 11, 2009, 02:43:26 PM »

Could be Microsoft doing a validation check - see the entry for that IP address:

OrgName:    Microsoft Corp
OrgID:      MSFT
Address:    One Microsoft Way
City:       Redmond
StateProv:  WA
PostalCode: 98052
Country:    US

NetRange:   207.46.0.0 - 207.46.255.255
CIDR:       207.46.0.0/16
NetName:    MICROSOFT-GLOBAL-NET
NetHandle:  NET-207-46-0-0-1
Parent:     NET-207-0-0-0-0
NetType:    Direct Assignment
NameServer: NS1.MSFT.NET
NameServer: NS5.MSFT.NET
NameServer: NS2.MSFT.NET
NameServer: NS3.MSFT.NET
NameServer: NS4.MSFT.NET
Comment:    
RegDate:    1997-03-31
Updated:    2004-12-09

RTechHandle: ZM39-ARIN
RTechName:   Microsoft
RTechPhone:  +1-425-882-8080
RTechEmail:  noc@microsoft.com

OrgAbuseHandle: ABUSE231-ARIN
OrgAbuseName:   Abuse
OrgAbusePhone:  +1-425-882-8080
OrgAbuseEmail:  abuse@microsoft.com

OrgAbuseHandle: HOTMA-ARIN
OrgAbuseName:   Hotmail Abuse
OrgAbusePhone:  +1-425-882-8080
OrgAbuseEmail:  abuse@hotmail.com

OrgAbuseHandle: MSNAB-ARIN
OrgAbuseName:   MSN ABUSE
OrgAbusePhone:  +1-425-882-8080
OrgAbuseEmail:  abuse@msn.com

OrgNOCHandle: ZM23-ARIN
OrgNOCName:   Microsoft Corporation
OrgNOCPhone:  +1-425-882-8080
OrgNOCEmail:  noc@microsoft.com

OrgTechHandle: MSFTP-ARIN
OrgTechName:   MSFT-POC
OrgTechPhone:  +1-425-882-8080
OrgTechEmail:  iprrms@microsoft.com


All courtesy of Sam Spade.

Colin

[EDIT - TD got in before me!]
Logged

UncleUB

  • Helpful
  • Senior Kitizen
  • *
  • Posts: 29543
Re: Router Interface.
« Reply #3 on: December 11, 2009, 02:59:13 PM »

Oh that was quick guys........where have you sprung from TD  ;D

I have just phoned O2 and it is indeed  the Microsoft Corporation which that IP number belongs to.

Quote
This is possibly something to do with Windows updates..........do you have them set to automatice ?

Yes I do, and there was a couple of updates on that date.  :)

It just puzzled me as that is the only entry in the log viewer which I can see as far back as 11/11/2009,all the others are for the O2 wireless box.lan


« Last Edit: December 11, 2009, 03:01:44 PM by UncleUB »
Logged

tuftedduck

  • Senior Kitizen
  • ******
  • Posts: 29658
  • Router Luvvin Duck
Re: Router Interface.
« Reply #4 on: December 11, 2009, 05:07:44 PM »

If that IP pops up again in the logs you can deem it as trusted, then it will not be logged in the same way and all the options won't appear again.  :) 
Logged

UncleUB

  • Helpful
  • Senior Kitizen
  • *
  • Posts: 29543
Re: Router Interface.
« Reply #5 on: December 11, 2009, 05:33:24 PM »

Thanks TD,tbh its something I very rarely look at.I was just looking at the details of my weekly scan and decided to explore a few other options in McAfee.
As it was different and every other one was for the O2 wirelessbox it just set the alarm bells ringing.
« Last Edit: December 11, 2009, 05:58:21 PM by UncleUB »
Logged

BritBrat

  • Kitizen
  • ****
  • Posts: 1359
Re: Router Interface.
« Reply #6 on: December 11, 2009, 06:26:14 PM »

As it is Microsoft I would block it  :lol:

And only allow it when you want it to.
Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33884
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: Router Interface.
« Reply #7 on: December 13, 2009, 02:34:29 PM »

Thats a weird port.

Guessing - Could it be a program crash report to microsoft?
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

UncleUB

  • Helpful
  • Senior Kitizen
  • *
  • Posts: 29543
Re: Router Interface.
« Reply #8 on: December 13, 2009, 03:00:43 PM »

Thats a weird port.

Guessing - Could it be a program crash report to microsoft?

I haven't a clue,but can't remember having any programmes crash.

This was imbound,so why would Microsoft want to do this? Sorry to sound a bit vacant.

I had an update dated 07/12/09...Windows Defender KB915597 at 17.01pm,but the time of the other in the log viewer was 12.07pm?
Logged
 

anything