 |
Inicial ▼ Bookkeeping
Online ▼ Auditorias ▼
DNS
Administrado ▼
Acerca de DNS
Ordenar/Renovar
Preguntas Frecuentes
AUP
Dynamic DNS Clients
Configurar Dominios Dynamic DNS Update Password Monitoreo
de Redes ▼
Enterprise
Avanzado
Estándarr
Prueba
Preguntas Frecuentes
Resumen de Precio/Funciones
Ordenar
Muestras
Configure/Status Alert Profiles | ||
| ID de Informe | 4 |
| Vista Creada El: | Jan 1, 1970 00:00 GMT |
| Dirección(es) de Host: | X.X.X.X |
 |
| Puerto | Protocolo | Servicio Probable |
|
| ||
| 135 | TCP | loc-srv |
|
Defined as a "Location Service" in RFC1060, pre-SP3 versions
of Windows NT were susceptible to a denial of service attack
on this port that would cause NT's rpcss.exe process to consume
all available CPU cycles. The (easiest) recovery from this
attack is to reboot your machine.
You should do one of several things: a) upgrade/patch your operating system to make sure it is not susceptible to this attack; b) firewall your system so that port 135 is not visible from the internet c) configure your router to block port 135; d) Install one of several monitoring packages on your PC that block this denial of service. | ||
| 139 | TCP | netbios-ssn |
|
Port 139 is used on Windows machines for NetBios name resolution,
WINS, etc. A problem with older unpatched versions of Windows is that
they are susceptible to receipt of Out-Of-Band (OOB) data. This means
that someone can remotely send you OOB data on port 139 and can cause
numerous problems on your machine, including but not limited to
machine lockups, blue screens, loss of internet connection.
You should do one of several things: a) upgrade/patch your operating system to make sure it is not susceptible to this attack; b) firewall your system so that port 139 is not visible from the internet c) configure your router to block port 139; d) Install one of several monitoring packages on your PC that block this denial of service. | ||
| ||
| Número de puertos abiertos encontrados por el explorador de puertos:2 | ||