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

found a problem in my netstat setting


  • Please log in to reply
1 reply to this topic

#1 tolsta

tolsta

  • Members
  • 1 posts
  • OFFLINE
  •  

Posted 11 February 2018 - 06:54 PM

 Proto  Local Address          Foreign Address        State
  TCP    192.168.1.123:49703    104.47.148.199:https   ESTABLISHED
  TCP    192.168.1.123:49878    db5sch101110923:https  ESTABLISHED
  TCP    192.168.1.123:49959    a23-195-135-39:http    TIME_WAIT
  TCP    192.168.1.123:49963    a104-98-2-179:http     TIME_WAIT
  TCP    192.168.1.123:49964    104.244.42.69:http     TIME_WAIT
  TCP    192.168.1.123:49965    104.244.42.69:http     TIME_WAIT
  TCP    192.168.1.123:49967    104.244.42.195:https   ESTABLISHED
  TCP    192.168.1.123:49978    104.244.43.80:https    ESTABLISHED
  TCP    192.168.1.123:49985    wo-in-f188:5228        ESTABLISHED
  TCP    192.168.1.123:49994    94:https               ESTABLISHED
  TCP    192.168.1.123:49995    23.111.10.140:https    CLOSE_WAIT
  TCP    192.168.1.123:49996    srv-eu-ldn-4:https     CLOSE_WAIT
  TCP    192.168.1.123:50000    23.111.10.152:https    CLOSE_WAIT
  TCP    192.168.1.123:50001    ec2-52-44-189-113:https  ESTABLISHED
  TCP    192.168.1.123:50002    66-180-66-123:https    CLOSE_WAIT
  TCP    192.168.1.123:50004    66-180-66-123:https    CLOSE_WAIT
  TCP    [2a00:23c4:5482:8100:ae81:12ff:feb7:9e6c]:49991  rtr3:https             ESTABLISHED
  TCP    [2a00:23c4:5482:8100:ae81:12ff:feb7:9e6c]:49992  [2400:cb00:2048:1::681f:4ade]:https  ESTABLISHED
  TCP    [2a00:23c4:5482:8100:ae81:12ff:feb7:9e6c]:49993  [2400:cb00:2048:1::6813:c066]:https  ESTABLISHED
  TCP    [2a00:23c4:5482:8100:ae81:12ff:feb7:9e6c]:49997  lhr35s02-in-x02:https  ESTABLISHED
  TCP    [2a00:23c4:5482:8100:ae81:12ff:feb7:9e6c]:49998  lhr35s04-in-x0e:https  ESTABLISHED
  TCP    [2a00:23c4:5482:8100:ae81:12ff:feb7:9e6c]:49999  lhr25s02-in-x0e:https  ESTABLISHED
  TCP    [2a00:23c4:5482:8100:ae81:12ff:feb7:9e6c]:50003  lhr35s07-in-x02:https  ESTABLISHED
 
 
 
can anyone help as to stop this intrusion or what are the os referring too ???
thanks if you can help

Edited by Chris Cosgrove, 12 February 2018 - 07:11 PM.
Moved from 'Internal hardware' to 'Networking'.


BC AdBot (Login to Remove)

 


#2 Orecomm

Orecomm

  • Members
  • 261 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Roseburg, Oregon
  • Local time:09:35 PM

Posted 21 February 2018 - 07:04 PM

I don't see a problem as such. These are connections, mostly originating from your device, to various points on the Internet. Many are Google addresses, some Android/Google messaging services. I see one or two that look like Microsoft telemetry addresses, but I don't have my list handy. The ones with the long addresses at the bottom are IPV6 addresses, the lhr25s0x at least appear to be Google. Are there any of these in particular you are concerned about? It's a fair bit of work to chase each one down individually.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users