Olá
Otávio Lima Neto,
tudo bem?
Por gentileza, verifique esta
documentação, acredito que estas informações talvez sejam úteis para te auxiliar a resolver este problema.
Também pode-se usar Network Monitor e Process Monitor tool para tentar descobrir se algum processo tem um BAD_NETWORK_PATH
como resultado.
"On Network
Monitor, looking for 135 port communication filtering the events"
307 16:18:23 05/02/2015 0.2242935 svchost.exe <hostname><IP Address>TCP TCP:Flags=...A...., SrcPort=54602, DstPort=DCE
endpoint resolution(135), PayloadLen=0, Seq=2102590773, Ack=2602397804, Win=64240 (scale factor 0x0) = 64240 {TCP:20, IPv4:17}
477 16:18:23 05/02/2015 0.3461022 System < hostname> MSRPC MSRPC:c/o Continued Response: unknown
Call=0x39FF98 Context=0x0 Hint=0x27F0 Cancels=0x0 {MSRPC:156, SMB2:155, SMBOverTCP:154, TCP:153, IPv4:148}
38 16:18:23 05/02/2015 0.0173274 svchost.exe < hostname> <IP Address> DCOM DCOM:IObjectExporter:ServerAlive2
Request {MSRPC:19, TCP:18, IPv4:17}
"Looking for
some process sending the package to 135 port"
101 16:18:23 05/02/2015 0.0328385 UaService.exe <IP Address><hostname> MSRPC MSRPC:c/o Response:
unknown Call=0x2B Context=0x2 Hint=0xBC Cancels=0x0 Warning: GssAPIMechanism is not found, possibly caused by hard-coded mechanism, conversation off or filtering or wrong parser set. Loading full parser set may solve the problem.
See {MSRPC:24, TCP:23, IPv4:17}
102 16:18:23 05/02/2015 0.0330478 UaService.exe< hostname> <IP Address> MSRPC MSRPC:c/o Request:
unknown Call=0x2C Opnum=0x5 Context=0x0 Hint=0x58 Warning: GssAPIMechanism is not found, possibly caused by hard-coded mechanism, conversation off or filtering or wrong parser set. Loading full parser set may solve the problem.
See the {MSRPC:24, TCP:23, IPv4:17}
103 16:18:23 05/02/2015 0.0336743 UaService.exe <IP Address><hostname> MSRPC MSRPC:c/o Response:
unknown Call=0x2C Context=0x0 Hint=0xC Cancels=0x0 Warning: GssAPIMechanism is not found, possibly caused by hard-coded mechanism, conversation off or filtering or wrong parser set. Loading full parser set may solve the problem.
See t {MSRPC:24, TCP:23, IPv4:17}
104 16:18:23 05/02/2015 0.0339203 UaService.exe <hostname> <IP Address> MSRPC MSRPC:c/o Request:
unknown Call=0x2D Opnum=0x14 Context=0x3 Hint=0xA4 Warning: Octets trailer appends to authentication token {MSRPC:24, TCP:23, IPv4:17}
"Looking for process using the Process Monitor. We can see the UaService.exe sending the package
and getting status BAD_NETWORK_PATH. "
16:18:16,2896141 UaService.exe 2216 CreateFile \\IP_ADRESS\PIPE\wkssvc BAD NETWORK PATH Desired Access: Generic Read/Write,
Dis"EN-US">
16:19:53,4933801 UaService.exe 2216 CreateFile \\IP_ADRESS\PIPE\wkssvc BAD NETWORK PATH Desired Access: Generic Read/Write,
Dis"EN-US">
16:21:41,6018584 UaService.exe 2216 CreateFile \\IP_ADRESS\PIPE\wkssvc BAD NETWORK PATH Desired Access: Generic Read/Write,
Dis"EN-US">
16:23:29,8677706 UaService.exe 2216 CreateFile \\IP_ADRESS\PIPE\wkssvc BAD NETWORK PATH Desired Access: Generic Read/Write,
Dis"EN-US">
16:24:29,1771086 UaService.exe 2216 CreateFile \\IP_ADRESS\PIPE\wkssvc BAD NETWORK PATH Desired Access: Generic Read/Write,
Dis"EN-US">
Marcos SJ
Esse conteúdo e fornecido sem garantias de qualquer tipo, seja expressa ou implícita
MSDN Community Support
Por favor, lembre-se de Marcar como Resposta as postagens que resolveram o seu problema. Essa é uma maneira comum de reconhecer aqueles que o ajudaram e fazer com que seja mais fácil para os outros visitantes encontrarem
a resolução mais tarde.
