[wetabax]

Hello experts!
I always had access to a hard drive connected to the modem via USB port for several computer backups . It still works on both cell phones and a computer running Windows 10.

Only this computer running windows 8.1 will not work anymore. And this was after downloading Outbite PC (immediately uninstalled) to try to resolve an issue that causes my computer to freeze suddenly. After that this computer no longer accesses a simple command \\192.168.0.**** - the error code 0x80004005 results.

However, all other PCs and cell phones in the house continue to access the HD without problems.

In this Windows 8.1 I can still access via FTP. If I write ftp[:]//192.168.0.**** I have access to the backup folders . What happened? How do I disable this "lock" that Windows created somewhere lost in the registry?

OTHER INFORMATION:
Ping working perfectly:
C:\Users\Tbx>ping 192.168.0.****:

Firing 192.168.0.**** 32 bytes of data:
Response from 192.168.0.****: bytes=32 time=3ms TTL=64
Reply from 192.168.0.**** bytes=32 time=2ms TTL=64
Response from 192.168.0.****: bytes=32 time=2ms TTL=64
Response from 192.168.0.****: bytes=32 time=4ms TTL=64

Ping stats for 192.168.0.****:
Packets: Sent = 4, Received = 4, Lost = 0 (0% of
loss),
Approximate a round number of times in milliseconds:
Minimum = 2ms, Maximum = 4ms, Average = 2ms

*** Already tried: C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth
*** Already tried: sfc /scannow
*** Already tried: netsh winsock reset
*** Already tried: netsh int ip reset

 

[Corday]

MBAM can pick up remnants of Outbyte and any remnants from 3rd party suppliers since you didn't say where you got it from. You could also do a registry search and manually delete any Outbyte stuff. Get rid of anything Crunchbase also as that's the developing firm. In the future, do not use any Registry Cleaners or their "cousins".

 

[wetabax]

MBAM can pick up remnants of Outbyte and any remnants from 3rd party suppliers since you didn't say where you got it from. You could also do a registry search and manually delete any Outbyte stuff. Get rid of anything Crunchbase also as that's the developing firm. In the future, do not use any Registry Cleaners or their "cousins".

I suspect that Outbite changed some lines in registry. As I uninstalled it still after noting that I will have problems, but it had run before this, so, it's impossible to rid back what it changed. (Thank you for your answer. I will see this MBAM)

 

[spunk.funk]

To add to what has been said
Download ADWCleaner scan and remove anything it finds. Then from the same Download page, download Malwarebytes (MBAM) scan and quarantine, Restart. That should catch any remnants and remove them.

 

[wetabax]

To add to what has been said
Download ADWCleaner scan and remove anything it finds. Then from the same Download page, download Malwarebytes (MBAM) scan and quarantine, Restart. That should catch any remnants and remove them.

Mr Spunk Funk. I've done what you suggest. No effort. Still the same scenario: ftp is avaiable to access, but the HD directly using command \\192.168.0.xxx returns the same error code 0x80004005.

 

[spunk.funk]

On the other computers that can access the drive, reconfirm that the IP address of the drive is the \\192.168.0.xxx and is the one you are typing in.
If the drive has a name, try typing that name in (ie) \\Share Name
Go to Control Panel/Network and Sharing/Advanced Sharing. Make sure Network Discovery is on and Sharing is Enabled.

Redirecting

If doesn’t work type Ipconfig /all> 0 & notepad 0 and press Enter

copy the Notepad results and paste them into your next post

 

[wetabax]

On the other computers that can access the drive, reconfirm that the IP address of the drive is the \\192.168.0.xxx and is the one you are typing in.
If the drive has a name, try typing that name in (ie) \\Share Name
Go to Control Panel/Network and Sharing/Advanced Sharing. Make sure Network Discovery is on and Sharing is Enabled.

Redirecting

If doesn’t work type Ipconfig /all> 0 & notepad 0 and press Enter

copy the Notepad results and paste them into your next post

Yes, that is the same address I'm typing in. In all computers and cell phones, I access normally as 192.168.0.44
I will do what you suggest, but I can only answer at begin next week.
sorry and thank you
w.

 

[wetabax]

Hi, spunk funk! thanks again for your help.
The answers.
1) No name to access the Hdisk. Only the IP address.
2) "...Make sure Network Discovery is on and Sharing is Enabled. " - yes, it's enabled.
3) copying and pasting bellow the results.

On time: I apologize, but this matter is beyond my computer literacy skills.

Microsoft Windows [versão 6.3.9600]
(c) 2013 Microsoft Corporation. Todos os direitos reservados.

C:\WINDOWS\system32>ipconfig /all

Configuração de IP do Windows

Nome do host. . . . . . . . . . . . . . . . : Win8
Sufixo DNS primário . . . . . . . . . . . . :
Tipo de nó. . . . . . . . . . . . . . . . . : híbrido
Roteamento de IP ativado. . . . . . . . . . : não
Proxy WINS ativado. . . . . . . . . . . . . : não

Adaptador de Rede sem Fio Conexão Local* 2:

[...]

Adaptador de Rede sem Fio Wi-Fi:

Estado da mídia. . . . . . . . . . . . . . : mídia desconectada
Sufixo DNS específico de conexão. . . . . . :
Descrição . . . . . . . . . . . . . . . . . : Realtek RTL8188EE Wireless LAN
802.11n PCI-E NIC
Endereço Físico . . . . . . . . . . . . . . : 6C-71-D9-D2-B0-32
DHCP Habilitado . . . . . . . . . . . . . . : Sim
Configuração Automática Habilitada. . . . . : Sim

Adaptador Ethernet Ethernet:

Sufixo DNS específico de conexão. . . . . . :
Descrição . . . . . . . . . . . . . . . . . : JMicron PCI Express Gigabit Eth
ernet Adapter
Endereço Físico . . . . . . . . . . . . . . : 80-EE-73-7C-38-FB
DHCP Habilitado . . . . . . . . . . . . . . : Sim
Configuração Automática Habilitada. . . . . : Sim
Endereço IPv6 . . . . . . . . . . : 2804:431:e7d9:c067:1558:d2c7:ae6a:f9(Pref
erencial)
Endereço IPv6 Temporário. . . . . . . . : 2804:431:e7d9:c067:e405:8d1e:34f3:b
f06(Preferencial)
Endereço IPv6 de link local . . . . . . . . : fe80::1558:d2e7:ac6a:f9%9(Prefe
rencial)
Endereço IPv4. . . . . . . . . . . . . . . : 192.168.0.54(Preferencial)
Máscara de Sub-rede . . . . . . . . . . . . : 255.255.255.0
Concessão Obtida. . . . . . . . . . . . . . : sábado, 14 de maio de 2022 17:5
9:25
Concessão Expira. . . . . . . . . . . . . . : sábado, 14 de maio de 2022 23:5
9:25
Gateway Padrão. . . . . . . . . . . . . . . : fe80::dac6:78ff:fe53:d098%9
192.168.0.1
Servidor DHCP . . . . . . . . . . . . . . . : 192.168.0.1
IAID de DHCPv6. . . . . . . . . . . . . . . : 159444595
DUID de Cliente DHCPv6. . . . . . . . . . . : 00-01-00-01-29-8F-36-FE-6C-71-D
9-D2-B0-32
Servidores DNS. . . . . . . . . . . . . . . : fe80::dac6:78ff:fe53:d098%9
192.168.0.1
Servidor WINS Primário. . . . . . . . . . . : 192.168.0.1
NetBIOS em Tcpip. . . . . . . . . . . . . . : Habilitado

Adaptador de túnel isatap.{947F1D91-46B5-4B3B-A8A4-6C21ACED998A}:

Estado da mídia. . . . . . . . . . . . . . : mídia desconectada
Sufixo DNS específico de conexão. . . . . . :
Descrição . . . . . . . . . . . . . . . . . : Adaptador do Microsoft ISATAP
Endereço Físico . . . . . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Habilitado . . . . . . . . . . . . . . : Não
Configuração Automática Habilitada. . . . . : Sim
=============================================================================================================

PS C:\WINDOWS\system32> Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
Feature Name : SMB1Protocol
Display Name : Suporte para Compartilhamento de Arquivos SMB 1.0/CIFS
Description : Suporte para o protocolo de compartilhamento de arquivos SMB 1.0/CIFS e para o protocolo do
Pesquisador de Computadores.
Restart Required : Possible
State : EnablePending
Custom Properties :
ServerComponent\Description : Suporte para o protocolo de compartilhamento de arquivos SMB
1.0/CIFS e para o protocolo do Pesquisador de Computadores.
ServerComponent\DisplayName : Suporte para Compartilhamento de Arquivos SMB 1.0/CIFS
ServerComponent\Id : 487
ServerComponent\Type : Feature
ServerComponent\UniqueName : FS-SMB1
ServerComponent\Deploys\Update\Name : SMB1Protocol

PS C:\WINDOWS\system32> Get-SmbServerConfiguration | Select EnableSMB1Protocol

EnableSMB1Protocol
------------------
False


PS C:\WINDOWS\system32> Get-SmbServerConfiguration | Select EnableSMB2Protocol

EnableSMB2Protocol
------------------
True

Microsoft Windows [versão 6.3.9600]
(c) 2013 Microsoft Corporation. Todos os direitos reservados.

C:\WINDOWS\system32>sc.exe qc lanmanworkstation
[SC] QueryServiceConfig ÊXITO

NOME_DO_SERVIÇO: lanmanworkstation
TIPO : 20 WIN32_SHARE_PROCESS
TIPO_DE_INÍCIO : 2 AUTO_START
CONTROLE_DE_ERRO : 1 NORMAL
NOME_DO_CAMINHO_BINÁRIO : C:\WINDOWS\System32\svchost.exe -k NetworkServi
ce
GRUPO_DE_ORDEM_DE_CARREG. : NetworkProvider
MARCA : 0
NOME_PARA_EXIBIÇÃO : Estação de trabalho
DEPENDÊNCIAS : bowser
: mrxsmb20
: nsi
NOME_DO_INÍCIO_DO_SERVIÇO : NT AUTHORITY\NetworkService