1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Solved: [Problem] - Windows 7 ask for password if I access a Windows XP computer

Discussion in 'Networking' started by pidgeon777, Jan 6, 2013.

Thread Status:
Not open for further replies.
Advertisement
  1. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    Well there are 2 PC in my LAN:
    • NB
      • Notebook
      • WiFi connection to my router NETGEAR DGN2200v3
      • Windows 7 Professional x64 SP1
    • DSK
      • Desktop
      • Cabled connection to my router NETGEAR DGN2200V3
      • Windows XP Home Edition 32bit SP3

    If from DSK I try to access NB shared folders through network, everything is fine.
    If from NB I try to access DSK shared folders through network, the following window appears:

    [​IMG]

    The strange thing is that this problem seems to occur randomly! Sometimes it occurs, sometimes not (during the same session of usage of NB). This is annoying because usually I need to work with NB on files which are stored in DSK through local network, so if I need to apply a change to a file, sometimes I won't have a chance to do that.

    Some minutes ago I configured DSK and NB so that the account for both has the same username and password.

    When on NB I try to access DSK shared folders, the window I posted above appears, I fill the data but neither this time I have granted access...

    This is what happens:
    - I reset NB WiFi connection
    - Using NB I try to access DSK shared folders --> everything is ok
    - About 5 minutes passes
    - Using NB I try to access DSK shared folders --> the authentication window appears, I fill the username and password fields but they won't be recognized

    I need to work on DSK files directly from NB through my local network, so it is very annoying to reset my WiFi connection every 5 minutes... Just I don't know what the solution to this problem could be.
     
  2. TerryNet

    TerryNet Moderator

    Joined:
    Mar 23, 2005
    Messages:
    77,178
    First Name:
    Terry
    What does "I reset NB WiFi connection" mean?

    Please show for both PCs when the access is OK and again for when it is not ...

    Open a (black) Command Prompt window:
    Hold the Windows logo key and press r; in the Run box type cmd and click on OK.

    Type the following commands:

    nbtstat -n

    IPCONFIG /ALL

    [Note that there is no space between the slash and ALL.]

    Right click in the command window and choose Select All, then hit Enter.
    Paste the results in a message here.

    If necessary use a text file and removable media to copy the results to a computer with internet access.
     
  3. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    With "I reset NB WiFi connection" I mean this:

    [​IMG]

    I click on "Disconnetti" (disconnect) then "Connetti" (connect). I do this on NB, because I want to access DSK shared folders.

    If I do this, I can access from NB to DSK shared folders (the window which ask me to enter username and password, doesn't appear).
    If I try to access them after 5 minutes of inactivity, then the authentication window appears.
    I fill the form with my username and password (which are the same for both NB and DSK), but they aren't reconized.

    So I have to click on "Disable" then "Enable" WiFi connection.
    Then after about 5 minutes it doesn't work anymore, so I have to reset the WiFi connection, and so on...

    nbtstat -n (NB):

    Code:
    VirtualBox Host-Only Network:
    Indirizzo IP nodo: [192.168.56.1] ID ambito: []
    
                    Tabella nomi locali NetBIOS
    
           Nome               Tipo         Stato
        ---------------------------------------------
        WORKGROUP      <00>  GRUPPO      Registrato 
        PIDGEON-NB     <00>  UNICO       Registrato 
        PIDGEON-NB     <20>  UNICO       Registrato 
        WORKGROUP      <1E>  GRUPPO      Registrato 
        WORKGROUP      <1D>  UNICO       Registrato 
        ..__MSBROWSE__.<01>  GRUPPO      Registrato 
        
    Connessione alla rete locale (LAN):
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione di rete Bluetooth:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione rete wireless:
    Indirizzo IP nodo: [192.168.0.3] ID ambito: []
    
                    Tabella nomi locali NetBIOS
    
           Nome               Tipo         Stato
        ---------------------------------------------
        WORKGROUP      <00>  GRUPPO      Registrato 
        PIDGEON-NB     <00>  UNICO       Registrato 
        PIDGEON-NB     <20>  UNICO       Registrato 
        WORKGROUP      <1E>  GRUPPO      Registrato 
        
    Connessione rete wireless 3:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione rete wireless 2:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
    IPCONFIG /ALL (NB):

    nbtstat -n (DSK):

    IPCONFIG /ALL (DSK):

    Please note that I can see NB shared folders if I access them from DSK, and it works all the time, but:
    • DSK (Win XP) doesn't ask me for a password
    • I can't modify/add/delete files of NB shared folders (a message tells me that I have no permissions)

    Anyway this is not my main problem for now. My problem is that I have no way to work on DSK shared files if I try to access them from NB, because it works for only about 5 minutes, then the authentication window appears and so on.
     
  4. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
  5. TerryNet

    TerryNet Moderator

    Joined:
    Mar 23, 2005
    Messages:
    77,178
    First Name:
    Terry
    I don't know if the above is for the OK or not OK condition, and do not see the other one with which to compare. There is nothing in the above that gives me any hint of what could be happening, so I hope it is for the OK time.
     
  6. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    My post went in the following pages of the section, so I added a "bump" to make it visible again, if it's what you meant :).

    Unfortunately the problem still persists...
     
  7. TerryNet

    TerryNet Moderator

    Joined:
    Mar 23, 2005
    Messages:
    77,178
    First Name:
    Terry
    You've shown the nbtstat -n and ipconfig /all for each PC. If that is during the five minutes that you get the desired access I want to also see the same output for when you cannot get the desired access.

    If your above output is for the time when you cannot get the desired access I'm stumped.

    In the ipconfig /all for the XP machine is
    That means "Node Type ....: Unknown", right? I was mostly hoping to find "Node Type .....: Peer-Peer" because we have a fix for that.
     
  8. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    Ok, here is the output of the commands when the NB to DSK access is not working:

    nbtstat -n (NB):

    Code:
    VirtualBox Host-Only Network:
    Indirizzo IP nodo: [192.168.56.1] ID ambito: []
    
                    Tabella nomi locali NetBIOS
    
           Nome               Tipo         Stato
        ---------------------------------------------
        PIDGEON-NB     <00>  UNICO       Registrato 
        WORKGROUP      <00>  GRUPPO      Registrato 
        PIDGEON-NB     <20>  UNICO       Registrato 
        WORKGROUP      <1E>  GRUPPO      Registrato 
        WORKGROUP      <1D>  UNICO       Registrato 
        ..__MSBROWSE__.<01>  GRUPPO      Registrato 
        
    Connessione alla rete locale (LAN):
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione rete wireless:
    Indirizzo IP nodo: [192.168.0.3] ID ambito: []
    
                    Tabella nomi locali NetBIOS
    
           Nome               Tipo         Stato
        ---------------------------------------------
        PIDGEON-NB     <00>  UNICO       Registrato 
        WORKGROUP      <00>  GRUPPO      Registrato 
        PIDGEON-NB     <20>  UNICO       Registrato 
        WORKGROUP      <1E>  GRUPPO      Registrato 
        
    Connessione di rete Bluetooth:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione rete wireless 3:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione rete wireless 2:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
    IPCONFIG /ALL (NB):

    Code:
    Configurazione IP di Windows
    
       Nome host . . . . . . . . . . . . . . : Pidgeon-NB
       Suffisso DNS primario . . . . . . . . : 
       Tipo nodo . . . . . . . . . . . . . . : Ibrido
       Routing IP abilitato. . . . . . . . . : No
       Proxy WINS abilitato . . . . . . . .  : No
    
    Scheda LAN wireless Connessione rete wireless 3:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2
       Indirizzo fisico. . . . . . . . . . . : 68-5D-43-82-6F-5A
       DHCP abilitato. . . . . . . . . . . . : Sì
       Configurazione automatica abilitata   : Sì
    
    Scheda LAN wireless Connessione rete wireless 2:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
       Indirizzo fisico. . . . . . . . . . . : 68-5D-43-82-6F-5A
       DHCP abilitato. . . . . . . . . . . . : Sì
       Configurazione automatica abilitata   : Sì
    
    Scheda LAN wireless Connessione rete wireless:
    
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 2230
       Indirizzo fisico. . . . . . . . . . . : 68-5D-43-82-6F-59
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
       Indirizzo IPv6 locale rispetto al collegamento . : fe80::14ee:2cdc:9be1:6c42%15(Preferenziale) 
       Indirizzo IPv4. . . . . . . . . . . . : 192.168.0.3(Preferenziale) 
       Subnet mask . . . . . . . . . . . . . : 255.255.255.0
       Gateway predefinito . . . . . . . . . : 192.168.0.1
       IAID DHCPv6 . . . . . . . . . . . : 359161155
       DUID Client DHCPv6. . . . . . . . : 00-01-00-01-18-08-A9-DC-10-BF-48-1D-F9-DC
       Server DNS . . . . . . . . . . . . .  : 213.205.32.70
                                               213.205.36.70
       NetBIOS su TCP/IP . . . . . . . . . . : Attivato
    
    Scheda Ethernet Connessione alla rete locale (LAN):
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Atheros AR8161/8165 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
       Indirizzo fisico. . . . . . . . . . . : 10-BF-48-1D-F9-DC
       DHCP abilitato. . . . . . . . . . . . : Sì
       Configurazione automatica abilitata   : Sì
    
    Scheda Ethernet Connessione di rete Bluetooth:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Dispositivo Bluetooth (Personal Area Network)
       Indirizzo fisico. . . . . . . . . . . : 68-5D-43-82-6F-5D
       DHCP abilitato. . . . . . . . . . . . : Sì
       Configurazione automatica abilitata   : Sì
    
    Scheda Ethernet VirtualBox Host-Only Network:
    
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
       Indirizzo fisico. . . . . . . . . . . : 08-00-27-00-D4-9C
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
       Indirizzo IPv6 locale rispetto al collegamento . : fe80::89f2:433c:4759:c77f%26(Preferenziale) 
       Indirizzo IPv4. . . . . . . . . . . . : 192.168.56.1(Preferenziale) 
       Subnet mask . . . . . . . . . . . . . : 255.255.255.0
       Gateway predefinito . . . . . . . . . : 
       IAID DHCPv6 . . . . . . . . . . . : 386400295
       DUID Client DHCPv6. . . . . . . . : 00-01-00-01-18-08-A9-DC-10-BF-48-1D-F9-DC
       Server DNS . . . . . . . . . . . . .  : fec0:0:0:ffff::1%1
                                               fec0:0:0:ffff::2%1
                                               fec0:0:0:ffff::3%1
       NetBIOS su TCP/IP . . . . . . . . . . : Attivato
    
    Scheda Tunnel isatap.{00F38D98-4B9A-43AE-9D16-127C60320A79}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{9D164E71-1EC2-4698-903B-413CCB4BD92D}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{16217D7F-96E3-42FF-A7C3-1302DF69B19D}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{71A116F7-A1D1-4F5A-B73E-8488A6784529}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{4028591E-C367-4A36-84C3-E9C41A515F98}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #5
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel Teredo Tunneling Pseudo-Interface:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{DE343537-DCFC-4C60-9FEA-AD8DD34BCCC8}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #6
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    nbtstat -n (DSK):

    Code:
    Connessione alla rete locale (LAN) 2:
    Indirizzo IP nodo: [192.168.0.2] ID ambito: []
    
    
    
                    Tabella nomi locali NetBIOS
    
    
    
           Nome               Tipo         Stato
    
        ---------------------------------------------
    
        PIDGEON-DSK    <00>  UNICO       Registrato 
    
        WORKGROUP      <00>  GRUPPO      Registrato 
    
        PIDGEON-DSK    <20>  UNICO       Registrato 
    
        WORKGROUP      <1E>  GRUPPO      Registrato 
    
        WORKGROUP      <1D>  UNICO       Registrato 
    
        ..__MSBROWSE__.<01>  GRUPPO      Registrato 
    
        
    VirtualBox Host-Only Network:
    Indirizzo IP nodo: [192.168.56.1] ID ambito: []
    
    
    
                    Tabella nomi locali NetBIOS
    
    
    
           Nome               Tipo         Stato
    
        ---------------------------------------------
    
        PIDGEON-DSK    <00>  UNICO       Registrato 
    
        WORKGROUP      <00>  GRUPPO      Registrato 
    
        PIDGEON-DSK    <20>  UNICO       Registrato 
    
        WORKGROUP      <1E>  GRUPPO      Registrato 
    
        WORKGROUP      <1D>  UNICO       Registrato 
    
        ..__MSBROWSE__.<01>  GRUPPO      Registrato
    IPCONFIG /ALL (DSK):

    Code:
    Configurazione IP di Windows
    
    
    
            Nome host . . . . . . . . . . . . . . : Pidgeon-DSK
    
            Suffisso DNS primario  . . . . . . .  : 
    
            Tipo nodo . . . . . . . . .  : Sconosciuto
    
            Routing IP abilitato. . . . . . . . . : No
    
            Proxy WINS abilitato . . . . . . . .  : No
    
    
    
    Scheda Ethernet VirtualBox Host-Only Network:
    
    
    
            Suffisso DNS specifico per connessione: 
    
            Descrizione . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
    
            Indirizzo fisico. . . . . . . . . . . : 08-00-27-00-24-27
    
            DHCP abilitato. . . . . . . . . . . . : No
    
            Indirizzo IP. . . . . . . . . . . . . : 192.168.56.1
    
            Subnet mask . . . . . . . . . . . . . : 255.255.255.0
    
            Gateway predefinito . . . . . . . . . : 
    
    
    
    Scheda Ethernet Connessione alla rete locale (LAN) 2:
    
    
    
            Suffisso DNS specifico per connessione: 
    
            Descrizione . . . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
    
            Indirizzo fisico. . . . . . . . . . . : 00-11-09-06-7A-72
    
            DHCP abilitato. . . . . . . . . . . . : No
    
            Indirizzo IP. . . . . . . . . . . . . : 192.168.0.2
    
            Subnet mask . . . . . . . . . . . . . : 255.255.255.0
    
            Gateway predefinito . . . . . . . . . : 192.168.0.1
    
            Server DNS . . . . . . . . . . . . .  : 213.205.32.70
    
                                                213.205.36.70
    Please note: as you can notice now both NB and DSK are using a static IP configuration, because I've read that it is suggested to do that.

    Anyway, the problem is still there...
     
  9. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    In the hope of being fast enough, here is what happens during the 5 minutes where the access from NB to DSK shared folders works:

    nbtstat -n (NB):

    Code:
    VirtualBox Host-Only Network:
    Indirizzo IP nodo: [192.168.56.1] ID ambito: []
    
                    Tabella nomi locali NetBIOS
    
           Nome               Tipo         Stato
        ---------------------------------------------
        PIDGEON-NB     <00>  UNICO       Registrato 
        WORKGROUP      <00>  GRUPPO      Registrato 
        PIDGEON-NB     <20>  UNICO       Registrato 
        WORKGROUP      <1E>  GRUPPO      Registrato 
        WORKGROUP      <1D>  UNICO       Registrato 
        ..__MSBROWSE__.<01>  GRUPPO      Registrato 
        
    Connessione alla rete locale (LAN):
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione rete wireless:
    Indirizzo IP nodo: [192.168.0.3] ID ambito: []
    
                    Tabella nomi locali NetBIOS
    
           Nome               Tipo         Stato
        ---------------------------------------------
        PIDGEON-NB     <00>  UNICO       Registrato 
        WORKGROUP      <00>  GRUPPO      Registrato 
        PIDGEON-NB     <20>  UNICO       Registrato 
        WORKGROUP      <1E>  GRUPPO      Registrato 
        
    Connessione di rete Bluetooth:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione rete wireless 3:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
        
    Connessione rete wireless 2:
    Indirizzo IP nodo: [0.0.0.0] ID ambito: []
    
        Nessun nome nella cache
    IPCONFIG /ALL (NB):

    Code:
    Configurazione IP di Windows
    
       Nome host . . . . . . . . . . . . . . : Pidgeon-NB
       Suffisso DNS primario . . . . . . . . : 
       Tipo nodo . . . . . . . . . . . . . . : Ibrido
       Routing IP abilitato. . . . . . . . . : No
       Proxy WINS abilitato . . . . . . . .  : No
    
    Scheda LAN wireless Connessione rete wireless 3:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2
       Indirizzo fisico. . . . . . . . . . . : 68-5D-43-82-6F-5A
       DHCP abilitato. . . . . . . . . . . . : Sì
       Configurazione automatica abilitata   : Sì
    
    Scheda LAN wireless Connessione rete wireless 2:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
       Indirizzo fisico. . . . . . . . . . . : 68-5D-43-82-6F-5A
       DHCP abilitato. . . . . . . . . . . . : Sì
       Configurazione automatica abilitata   : Sì
    
    Scheda LAN wireless Connessione rete wireless:
    
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 2230
       Indirizzo fisico. . . . . . . . . . . : 68-5D-43-82-6F-59
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
       Indirizzo IPv6 locale rispetto al collegamento . : fe80::14ee:2cdc:9be1:6c42%15(Preferenziale) 
       Indirizzo IPv4. . . . . . . . . . . . : 192.168.0.3(Preferenziale) 
       Subnet mask . . . . . . . . . . . . . : 255.255.255.0
       Gateway predefinito . . . . . . . . . : 192.168.0.1
       IAID DHCPv6 . . . . . . . . . . . : 359161155
       DUID Client DHCPv6. . . . . . . . : 00-01-00-01-18-08-A9-DC-10-BF-48-1D-F9-DC
       Server DNS . . . . . . . . . . . . .  : 213.205.32.70
                                               213.205.36.70
       NetBIOS su TCP/IP . . . . . . . . . . : Attivato
    
    Scheda Ethernet Connessione alla rete locale (LAN):
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Atheros AR8161/8165 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
       Indirizzo fisico. . . . . . . . . . . : 10-BF-48-1D-F9-DC
       DHCP abilitato. . . . . . . . . . . . : Sì
       Configurazione automatica abilitata   : Sì
    
    Scheda Ethernet Connessione di rete Bluetooth:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Dispositivo Bluetooth (Personal Area Network)
       Indirizzo fisico. . . . . . . . . . . : 68-5D-43-82-6F-5D
       DHCP abilitato. . . . . . . . . . . . : Sì
       Configurazione automatica abilitata   : Sì
    
    Scheda Ethernet VirtualBox Host-Only Network:
    
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
       Indirizzo fisico. . . . . . . . . . . : 08-00-27-00-D4-9C
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
       Indirizzo IPv6 locale rispetto al collegamento . : fe80::89f2:433c:4759:c77f%26(Preferenziale) 
       Indirizzo IPv4. . . . . . . . . . . . : 192.168.56.1(Preferenziale) 
       Subnet mask . . . . . . . . . . . . . : 255.255.255.0
       Gateway predefinito . . . . . . . . . : 
       IAID DHCPv6 . . . . . . . . . . . : 386400295
       DUID Client DHCPv6. . . . . . . . : 00-01-00-01-18-08-A9-DC-10-BF-48-1D-F9-DC
       Server DNS . . . . . . . . . . . . .  : fec0:0:0:ffff::1%1
                                               fec0:0:0:ffff::2%1
                                               fec0:0:0:ffff::3%1
       NetBIOS su TCP/IP . . . . . . . . . . : Attivato
    
    Scheda Tunnel isatap.{00F38D98-4B9A-43AE-9D16-127C60320A79}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{9D164E71-1EC2-4698-903B-413CCB4BD92D}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{16217D7F-96E3-42FF-A7C3-1302DF69B19D}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{71A116F7-A1D1-4F5A-B73E-8488A6784529}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{4028591E-C367-4A36-84C3-E9C41A515F98}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #5
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel Teredo Tunneling Pseudo-Interface:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    
    Scheda Tunnel isatap.{DE343537-DCFC-4C60-9FEA-AD8DD34BCCC8}:
    
       Stato supporto. . . . . . . . . . . . : Supporto disconnesso
       Suffisso DNS specifico per connessione: 
       Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #6
       Indirizzo fisico. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP abilitato. . . . . . . . . . . . : No
       Configurazione automatica abilitata   : Sì
    nbtstat -n (DSK):

    Code:
    Connessione alla rete locale (LAN) 2:
    Indirizzo IP nodo: [192.168.0.2] ID ambito: []
    
    
    
                    Tabella nomi locali NetBIOS
    
    
    
           Nome               Tipo         Stato
    
        ---------------------------------------------
    
        PIDGEON-DSK    <00>  UNICO       Registrato 
    
        WORKGROUP      <00>  GRUPPO      Registrato 
    
        PIDGEON-DSK    <20>  UNICO       Registrato 
    
        WORKGROUP      <1E>  GRUPPO      Registrato 
    
        WORKGROUP      <1D>  UNICO       Registrato 
    
        ..__MSBROWSE__.<01>  GRUPPO      Registrato 
    
        
    VirtualBox Host-Only Network:
    Indirizzo IP nodo: [192.168.56.1] ID ambito: []
    
    
    
                    Tabella nomi locali NetBIOS
    
    
    
           Nome               Tipo         Stato
    
        ---------------------------------------------
    
        PIDGEON-DSK    <00>  UNICO       Registrato 
    
        WORKGROUP      <00>  GRUPPO      Registrato 
    
        PIDGEON-DSK    <20>  UNICO       Registrato 
    
        WORKGROUP      <1E>  GRUPPO      Registrato 
    
        WORKGROUP      <1D>  UNICO       Registrato 
    
        ..__MSBROWSE__.<01>  GRUPPO      Registrato
    IPCONFIG /ALL (DSK):

    Code:
    Configurazione IP di Windows
    
    
    
            Nome host . . . . . . . . . . . . . . : Pidgeon-DSK
    
            Suffisso DNS primario  . . . . . . .  : 
    
            Tipo nodo . . . . . . . . .  : Sconosciuto
    
            Routing IP abilitato. . . . . . . . . : No
    
            Proxy WINS abilitato . . . . . . . .  : No
    
    
    
    Scheda Ethernet VirtualBox Host-Only Network:
    
    
    
            Suffisso DNS specifico per connessione: 
    
            Descrizione . . . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
    
            Indirizzo fisico. . . . . . . . . . . : 08-00-27-00-24-27
    
            DHCP abilitato. . . . . . . . . . . . : No
    
            Indirizzo IP. . . . . . . . . . . . . : 192.168.56.1
    
            Subnet mask . . . . . . . . . . . . . : 255.255.255.0
    
            Gateway predefinito . . . . . . . . . : 
    
    
    
    Scheda Ethernet Connessione alla rete locale (LAN) 2:
    
    
    
            Suffisso DNS specifico per connessione: 
    
            Descrizione . . . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
    
            Indirizzo fisico. . . . . . . . . . . : 00-11-09-06-7A-72
    
            DHCP abilitato. . . . . . . . . . . . : No
    
            Indirizzo IP. . . . . . . . . . . . . : 192.168.0.2
    
            Subnet mask . . . . . . . . . . . . . : 255.255.255.0
    
            Gateway predefinito . . . . . . . . . : 192.168.0.1
    
            Server DNS . . . . . . . . . . . . .  : 213.205.32.70
    
                                                213.205.36.70
     
  10. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    I just compared the results provided by each command for each PC while it was working and not, but there are no differences...

    I confirm that "Sconosciuto" = "Unknown".

    I have no other ideas, I hope to solve this annoying problem...
     
  11. TerryNet

    TerryNet Moderator

    Joined:
    Mar 23, 2005
    Messages:
    77,178
    First Name:
    Terry
    I cannot see anything to suggest why the problem occurs nor why the delay before it occurs.

    I've also looked through my half-forgotten notes on XP problems and found nothing like this.

    So, here is one "dumb" thing to try. Remembering the days when external names were restricted to eight characters (six at one time?) I get nervous when I see longer ones and a problem I cannot explain. So, I suggest that you change one of the computer names (Pidgeon-NB or Pidgeon-DSK) so that they are unique in the first eight characters. Or if you really buy into my phobia change both names to be eight characters or less. You have to reboot the system for a name change to take effect.
     
  12. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    Would something like this be good for a quick test?:

    DSK --> PidgeonD
    NB --> PidgeonN
     
  13. TerryNet

    TerryNet Moderator

    Joined:
    Mar 23, 2005
    Messages:
    77,178
    First Name:
    Terry
  14. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    I changed DSK and NB names, but the problem still persists.

    I can access to DSK shared folders from NB for 5 minutes without authentication window, then after about 5 minutes the authentication window appears. I fill it with my username and password, but they aren't recognized.

    UPDATE: after 3 more minutes there is no more authentication window, instead the following popup appears:

    [​IMG]

    This popup continue to appears even if I disable then enable my WiFi connection again.

    Thus still I can't access to DSK shared folders...
     
  15. pidgeon777

    pidgeon777 Thread Starter

    Joined:
    Jan 6, 2013
    Messages:
    15
    Note: I changed PidgeonD and PidgeonN back to Pidgeon-DSK and Pidgeon-NB.

    Well, after having spent 4 hours/day for 5 days trying to find a solution to this stupid problem, here is what happened:

    1) I executed "ping PIDGEON-DSK" on NB.
    2) I noticed that IP of DSK was 192.168.56.1.
    I thought, strange, DSK was set to a static ip, or 192.168.0.2...
    3) I executed "ipconfig" on NB.
    I noticed that the network card "Scheda Ethernet VirtualBox Host-Only Network" was associated to the same ip of DSK (192.168.56.1).
    4) I remembered that I installed VirtualBox even on DSK.
    5) I noticed that the network card "Scheda Ethernet VirtualBox Host-Only Network" had the same static ip on both DSK and NB (192.168.56.1).
    6) I changed the "Scheda Ethernet VirtualBox Host-Only Network" static ip of DSK to 192.168.57.1.
    7) I tried to access DSK shared folders from NB.
    8) No authentication window appeared.
    9) I was able to browser/modify DSK share folders.
    10) I waited 10 more minutes.
    11) No authentication window appeared.
    12) I was able to browser/modify DSK share folders.

    Problem solved.

    In short, this happened because some months ago I installed VirtualBox on both DSK and NB. When you install VirtualBox, it creates a network card so that you are able to connect to internet when using the guest system. The problem is that the network card has the same ip (192.168.56.1) for every VirtualBox installation, so if you connect 2 PC with VirtualBox installed, there will be network card conflicts unless you change the static IP of one of the cards.
     
  16. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1083942

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice