svchost.exe traffic banned in most devices

[Marinos 0]

For those who know, i had a problem with the 502 cmos checksum error and it would make my eset product network inspector go crazy and add the same devices two times. Now though that i took it to a service and they "fixed" it, i see a lot of svchost.exe traffic banned. What is going on and sohuld i worry? Should i enable it ? Also what is NT Kernel&System? Should i post a screenshot?

[itman 1,659]

2 minutes ago, Marinos said:

Should i post a screenshot?

Yes. Also post as much available data that exists related to this problem such a screen shot of Eset alert of blocked svchost.exe network traffic.

[Marinos 0]

3 minutes ago, itman said:

Yes. Also post as much available data that exists related to this problem such a screen shot of Eset alert of blocked svchost.exe network traffic.

i hope these arent sensitive data

 

[itman 1,659]

Just now, Marinos said:

 

i hope these arent sensitive data

 

Edit out any data related to the local device such as local subnet IP addresses; user id info., etc..

[Marinos 0]

 

1 minute ago, itman said:

Edit out any data related to the local device such as local subnet IP addresses; user id info., etc..

[Marinos 0]

2 minutes ago, itman said:

Edit out any data related to the local device such as local subnet IP addresses; user id info., etc..

i think i really got some viruses im scared

 

 

[itman 1,659]

Do you have the Eset firewall set to "Allow all outbound traffic?"

[Marinos 0]

2 minutes ago, itman said:

Do you have the Eset firewall set to "Allow all outbound traffic?"

Let me check also can I contact you to discord or something cause I believe that it would be faster to talk from there

[Marinos 0]

4 minutes ago, itman said:

Do you have the Eset firewall set to "Allow all outbound traffic?"

Can't find the setting where is it?

[Marinos 0]

5 minutes ago, itman said:

Do you have the Eset firewall set to "Allow all outbound traffic?"

Also I think it says inbound cause it says εισερχόμενα 

[Marinos 0]

16 minutes ago, itman said:

Do you have the Eset firewall set to "Allow all outbound traffic?"

Itman where is this setting located at?

[Marinos 0]

37 minutes ago, Marinos said:

For those who know, i had a problem with the 502 cmos checksum error and it would make my eset product network inspector go crazy and add the same devices two times. Now though that i took it to a service and they "fixed" it, i see a lot of svchost.exe traffic banned. What is going on and sohuld i worry? Should i enable it ? Also what is NT Kernel&System? Should i post a screenshot?

@Marcosplease help

[Marinos 0]

38 minutes ago, Marinos said:

For those who know, i had a problem with the 502 cmos checksum error and it would make my eset product network inspector go crazy and add the same devices two times. Now though that i took it to a service and they "fixed" it, i see a lot of svchost.exe traffic banned. What is going on and sohuld i worry? Should i enable it ? Also what is NT Kernel&System? Should i post a screenshot?

Olay apparently this has happened again when I first set up my eset product and it just wanted some time now I can't see the blocked traffic I guess it is okay?

[Marinos 0]

8 minutes ago, Marinos said:

Olay apparently this has happened again when I first set up my eset product and it just wanted some time now I can't see the blocked traffic I guess it is okay?

I know I'm getting rude but I really need help @Marcos @itman please am i okay now?

[Marinos 0]

41 minutes ago, Marinos said:

I know I'm getting rude but I really need help @Marcos @itman please am i okay now?

@itman @MarcosI know it's rude to fag someone but please answer me asap

[itman 1,659]

1 hour ago, Marinos said:

Itman where is this setting located at?

Also, verify that the "Also evaluate rules from Windows Firewall" setting is enabled.

[Marinos 0]

Just now, itman said:

Also, verify that the "Also evaluate rules from Windows Firewall" setting is enabled.

Hey itman I said that I think its fine now read my last message but now I don't have the 192.168.1.3 ip why that? I can't find it neither through avr -ap command

 

[itman 1,659]

2 minutes ago, Marinos said:

Hey itman I said that I think its fine now read my last message

Probably not. Eset Network Wizard by default only shows network connections blocked in the last 15 mins. All the System and svchost.exe blocking most likely occurred at system startup time when Windows performs numerous outbound connections from these processes for Win Update checking and various maintenance activities. Again, verify your Eset settings are the same as shown in the posted screen shot.

8 minutes ago, Marinos said:

but now I don't have the 192.168.1.3 ip why that?

No clue what you are referring to. If you open your router's GUI, it will show you what device on your network that IP address is associated with.

[Marinos 0]

2 minutes ago, itman said:

Probably not. Eset Network Wizard by default only shows network connections blocked in the last 15 mins. All the System and svchost.exe blocking most likely occurred at system startup time when Windows performs numerous outbound connections from these processes for Win Update checking and various maintenance activities. Again, verify your Eset settings are the same as shown in the posted screen shot.

No clue what you are referring to. If you open your router's GUI, it will show you what device on your network that IP address is associated with.

My phone was the 1.3 but now it's 1.6 also my phone had the most blocked tries does that mean something? 

[Marinos 0]

4 minutes ago, itman said:

Probably not. Eset Network Wizard by default only shows network connections blocked in the last 15 mins. All the System and svchost.exe blocking most likely occurred at system startup time when Windows performs numerous outbound connections from these processes for Win Update checking and various maintenance activities. Again, verify your Eset settings are the same as shown in the posted screen shot.

No clue what you are referring to. If you open your router's GUI, it will show you what device on your network that IP address is associated with.

Also you may didn't understood there isn't any banned traffic now not only to see but there is nothing neither the blue icon that indicates a problem. And the settings are as you said 

[itman 1,659]

1 minute ago, Marinos said:

My phone was the 1.3 but now it's 1.6 also my phone had the most blocked tries does that mean something? 

Are you connecting to the Internet from your PC using your wireless phone connection?

[Marinos 0]

5 minutes ago, itman said:

Probably not. Eset Network Wizard by default only shows network connections blocked in the last 15 mins. All the System and svchost.exe blocking most likely occurred at system startup time when Windows performs numerous outbound connections from these processes for Win Update checking and various maintenance activities. Again, verify your Eset settings are the same as shown in the posted screen shot.

No clue what you are referring to. If you open your router's GUI, it will show you what device on your network that IP address is associated with.

Okay let me conclude: so the first time I setup the network inspector the same thing had happened but because I djdnt change it to a trusted now its a trusted but there this happened after multiple scans I closed eset gui and waited till there is no blue icon because it needed some time I think and now there is no 1.3 ip even at the routers gui I can't find it.

 

Just now, itman said:

Are you connecting to the Internet from your PC using your wireless phone connection?

I am from a laptop 

[itman 1,659]

I really have no clue what you are doing.

Do not run a Network Inspector scan immediately after a system startup. Full network connectivity usually takes a few minutes to fully initialize. This might explain the strange things you have been observing.

[Marinos 0]

2 minutes ago, itman said:

I really have no clue what you are doing.

Do not run a Network Inspector scan immediately after a system startup. Full network connectivity usually takes a few minutes to fully initialize. This might explain the strange things you have been observing.

Okay but what about the 1.3 ip that there isn't?  Wtf

[itman 1,659]

7 minutes ago, Marinos said:

Okay but what about the 1.3 ip that there isn't? 

The router via DHCPv4 processing auto allocates IP addresses on your local network. Most likely, the router allocated a new IP address to the phone; i.e. xxx.xxxx.1.3 is now xxx.xxxx.1.6.