Toggle sidebar Toggle sidebar

Miglior Modem Router Sotto I 100€

Stato
Discussione chiusa ad ulteriori risposte.
E

emanu37429

Ospite
Michelemmike ha detto:
In lan, infatti da log si legge lan1 down e dopo qualche secondo lan1 up. Ho gia provato le altre porte e un altro cavo, ma il problema persiste. Il firmware è gia lultimo disponibile.
Clicca per espandere...
Vedi se impostando IP statico sia da PC che da router risolvi qualcosa.
 
M

Michelemmike

Nuovo Utente
90
6
CPU
AMD FX-6300
Scheda Madre
Gigabyte GA-970A-UD3P rev 2.0
HDD
WD Caviar Blue 1.0Tb
RAM
Kingston HyperX Fury 2X4Gb
GPU
Sapphire Radeon r7 250X
PSU
JOUJYE BW-B520JL 520W
Case
Thermaltake Versa H23
OS
Windows 7 pro x64
emanu37429 ha detto:
Vedi se impostando IP statico sia da PC che da router risolvi qualcosa.
Clicca per espandere...
Non so come farlo, pero nel frattempo ho disabilitato il risparmio energetico della scheda di rete e la lan non e caduta neanche una volta in 7 ore. Voglio fare altre ore di test per accertarmi di aver risolto. La cosa strana è che col vecchio router non si disconnetteva con il risparmio energetico della scheda di rete attivo.
 
E

emanu37429

Ospite
Michelemmike ha detto:
Non so come farlo, pero nel frattempo ho disabilitato il risparmio energetico della scheda di rete e la lan non e caduta neanche una volta in 7 ore. Voglio fare altre ore di test per accertarmi di aver risolto. La cosa strana è che col vecchio router non si disconnetteva con il risparmio energetico della scheda di rete attivo.
Clicca per espandere...
OK. Penso che già così hai risolto.
Per il fatto che col vecchio router non lo faceva non so che dirti.
 
M

Michelemmike

Nuovo Utente
90
6
CPU
AMD FX-6300
Scheda Madre
Gigabyte GA-970A-UD3P rev 2.0
HDD
WD Caviar Blue 1.0Tb
RAM
Kingston HyperX Fury 2X4Gb
GPU
Sapphire Radeon r7 250X
PSU
JOUJYE BW-B520JL 520W
Case
Thermaltake Versa H23
OS
Windows 7 pro x64
emanu37429 ha detto:
OK. Penso che già così hai risolto.
Per il fatto che col vecchio router non lo faceva non so che dirti.
Clicca per espandere...
Sì, ho risolto, ma tutti questi errori cosa sono?

2017-01-31 07:43:12 kernel:
2017-01-31 07:43:12 kernel: #### wan_primary: [185.105.107.154]
2017-01-31 07:43:12 WAN Connection: WAN was restored.
2017-01-31 07:43:12 start_nat_rules: apply the nat_rules(/tmp/nat_rules)!
2017-01-31 07:43:13 ddns update: ez-ipupdate: starting...
2017-01-31 07:43:14 ddns update: connected to ns1.asuscomm.com (103.10.4.108) on port 80.
2017-01-31 07:43:15 ddns update: asusddns_update: 0
2017-01-31 07:43:15 ddns: ddns update ok
2017-01-31 07:43:42 crond[2495]: time disparity of 3200082 minutes detected
2017-01-31 07:43:54 nmbd[2648]: [2017/01/31 07:43:54, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
2017-01-31 07:43:54 nmbd[2648]: *****
2017-01-31 07:43:54 nmbd[2648]:
2017-01-31 07:43:54 nmbd[2648]: Samba name server DSL-AC56U is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.1
2017-01-31 07:43:54 nmbd[2648]:
2017-01-31 07:43:54 nmbd[2648]: *****
2017-01-31 07:44:18 kernel: AP SETKEYS WPA2 MAC=1C:B7:2C:E2:AD:79
2017-01-31 07:48:48 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 07:52:42 kernel: AP SETKEYS WPA2 MAC=5C:51:88:A7:AB:6E
2017-01-31 07:53:48 smbd[16190]: [2017/01/31 07:53:48, 0] lib/util_sock.c:read_data(540)
2017-01-31 07:53:48 smbd[16190]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 08:22:07 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 08:25:32 smbd[2657]: [2017/01/31 08:25:32, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:25:32 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:25:32 smbd[2657]: [2017/01/31 08:25:32, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:25:32 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:25:53 smbd[24188]: [2017/01/31 08:25:53, 0] lib/util_sock.c:read_data(540)
2017-01-31 08:25:53 smbd[24188]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 08:57:36 smbd[2657]: [2017/01/31 08:57:36, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:57:36 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:57:36 smbd[2657]: [2017/01/31 08:57:36, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:57:36 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:57:57 smbd[32049]: [2017/01/31 08:57:57, 0] lib/util_sock.c:read_data(540)
2017-01-31 08:57:57 smbd[32049]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 09:29:40 smbd[2657]: [2017/01/31 09:29:40, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 09:29:40 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 09:29:40 smbd[2657]: [2017/01/31 09:29:40, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 09:29:40 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 09:30:01 smbd[7416]: [2017/01/31 09:30:01, 0] lib/util_sock.c:read_data(540)
2017-01-31 09:30:01 smbd[7416]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 10:01:44 smbd[2657]: [2017/01/31 10:01:44, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 10:01:44 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 10:01:44 smbd[2657]: [2017/01/31 10:01:44, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 10:01:44 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 10:02:05 smbd[15021]: [2017/01/31 10:02:05, 0] lib/util_sock.c:read_data(540)
2017-01-31 10:02:05 smbd[15021]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 10:33:48 smbd[2657]: [2017/01/31 10:33:48, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 10:33:48 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 10:33:48 smbd[2657]: [2017/01/31 10:33:48, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 10:33:48 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 10:34:09 smbd[22717]: [2017/01/31 10:34:09, 0] lib/util_sock.c:read_data(540)
2017-01-31 10:34:09 smbd[22717]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 11:05:53 smbd[2657]: [2017/01/31 11:05:53, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 11:05:53 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 11:05:53 smbd[2657]: [2017/01/31 11:05:53, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 11:05:53 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 11:06:14 smbd[30410]: [2017/01/31 11:06:14, 0] lib/util_sock.c:read_data(540)
2017-01-31 11:06:14 smbd[30410]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 11:37:57 smbd[2657]: [2017/01/31 11:37:57, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 11:37:57 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 11:37:57 smbd[2657]: [2017/01/31 11:37:57, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 11:37:57 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 11:38:18 smbd[5835]: [2017/01/31 11:38:18, 0] lib/util_sock.c:read_data(540)
2017-01-31 11:38:18 smbd[5835]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 12:10:02 smbd[2657]: [2017/01/31 12:10:02, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 12:10:02 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 12:10:02 smbd[2657]: [2017/01/31 12:10:02, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 12:10:02 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 12:10:22 smbd[13614]: [2017/01/31 12:10:22, 0] lib/util_sock.c:read_data(540)
2017-01-31 12:10:22 smbd[13614]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 12:42:06 smbd[2657]: [2017/01/31 12:42:06, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 12:42:06 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 12:42:06 smbd[2657]: [2017/01/31 12:42:06, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 12:42:06 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 12:42:26 smbd[21312]: [2017/01/31 12:42:26, 0] lib/util_sock.c:read_data(540)
2017-01-31 12:42:26 smbd[21312]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 12:56:39 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 13:06:42 kernel: warning: `vsftpd' uses 32-bit capabilities (legacy support in use)
2017-01-31 13:14:10 smbd[2657]: [2017/01/31 13:14:10, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 13:14:10 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 13:14:10 smbd[2657]: [2017/01/31 13:14:10, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 13:14:10 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 13:14:30 smbd[28949]: [2017/01/31 13:14:30, 0] lib/util_sock.c:read_data(540)
2017-01-31 13:14:30 smbd[28949]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 13:29:15 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 13:31:14 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 13:32:25 kernel: AP SETKEYS WPA2 MAC=5C:51:88:A7:AB:6E
2017-01-31 13:32:59 WEB: User [admin] logged in from [192.168.1.3] via WEB
 
E

emanu37429

Ospite
Michelemmike ha detto:
Sì, ho risolto, ma tutti questi errori cosa sono?

2017-01-31 07:43:12 kernel:
2017-01-31 07:43:12 kernel: #### wan_primary: [185.105.107.154]
2017-01-31 07:43:12 WAN Connection: WAN was restored.
2017-01-31 07:43:12 start_nat_rules: apply the nat_rules(/tmp/nat_rules)!
2017-01-31 07:43:13 ddns update: ez-ipupdate: starting...
2017-01-31 07:43:14 ddns update: connected to ns1.asuscomm.com (103.10.4.108) on port 80.
2017-01-31 07:43:15 ddns update: asusddns_update: 0
2017-01-31 07:43:15 ddns: ddns update ok
2017-01-31 07:43:42 crond[2495]: time disparity of 3200082 minutes detected
2017-01-31 07:43:54 nmbd[2648]: [2017/01/31 07:43:54, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
2017-01-31 07:43:54 nmbd[2648]: *****
2017-01-31 07:43:54 nmbd[2648]:
2017-01-31 07:43:54 nmbd[2648]: Samba name server DSL-AC56U is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.1
2017-01-31 07:43:54 nmbd[2648]:
2017-01-31 07:43:54 nmbd[2648]: *****
2017-01-31 07:44:18 kernel: AP SETKEYS WPA2 MAC=1C:B7:2C:E2:AD:79
2017-01-31 07:48:48 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 07:52:42 kernel: AP SETKEYS WPA2 MAC=5C:51:88:A7:AB:6E
2017-01-31 07:53:48 smbd[16190]: [2017/01/31 07:53:48, 0] lib/util_sock.c:read_data(540)
2017-01-31 07:53:48 smbd[16190]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 08:22:07 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 08:25:32 smbd[2657]: [2017/01/31 08:25:32, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:25:32 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:25:32 smbd[2657]: [2017/01/31 08:25:32, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:25:32 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:25:53 smbd[24188]: [2017/01/31 08:25:53, 0] lib/util_sock.c:read_data(540)
2017-01-31 08:25:53 smbd[24188]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 08:57:36 smbd[2657]: [2017/01/31 08:57:36, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:57:36 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:57:36 smbd[2657]: [2017/01/31 08:57:36, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:57:36 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:57:57 smbd[32049]: [2017/01/31 08:57:57, 0] lib/util_sock.c:read_data(540)
2017-01-31 08:57:57 smbd[32049]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 09:29:40 smbd[2657]: [2017/01/31 09:29:40, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 09:29:40 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 09:29:40 smbd[2657]: [2017/01/31 09:29:40, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 09:29:40 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 09:30:01 smbd[7416]: [2017/01/31 09:30:01, 0] lib/util_sock.c:read_data(540)
2017-01-31 09:30:01 smbd[7416]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 10:01:44 smbd[2657]: [2017/01/31 10:01:44, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 10:01:44 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 10:01:44 smbd[2657]: [2017/01/31 10:01:44, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 10:01:44 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 10:02:05 smbd[15021]: [2017/01/31 10:02:05, 0] lib/util_sock.c:read_data(540)
2017-01-31 10:02:05 smbd[15021]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 10:33:48 smbd[2657]: [2017/01/31 10:33:48, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 10:33:48 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 10:33:48 smbd[2657]: [2017/01/31 10:33:48, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 10:33:48 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 10:34:09 smbd[22717]: [2017/01/31 10:34:09, 0] lib/util_sock.c:read_data(540)
2017-01-31 10:34:09 smbd[22717]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 11:05:53 smbd[2657]: [2017/01/31 11:05:53, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 11:05:53 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 11:05:53 smbd[2657]: [2017/01/31 11:05:53, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 11:05:53 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 11:06:14 smbd[30410]: [2017/01/31 11:06:14, 0] lib/util_sock.c:read_data(540)
2017-01-31 11:06:14 smbd[30410]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 11:37:57 smbd[2657]: [2017/01/31 11:37:57, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 11:37:57 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 11:37:57 smbd[2657]: [2017/01/31 11:37:57, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 11:37:57 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 11:38:18 smbd[5835]: [2017/01/31 11:38:18, 0] lib/util_sock.c:read_data(540)
2017-01-31 11:38:18 smbd[5835]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 12:10:02 smbd[2657]: [2017/01/31 12:10:02, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 12:10:02 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 12:10:02 smbd[2657]: [2017/01/31 12:10:02, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 12:10:02 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 12:10:22 smbd[13614]: [2017/01/31 12:10:22, 0] lib/util_sock.c:read_data(540)
2017-01-31 12:10:22 smbd[13614]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 12:42:06 smbd[2657]: [2017/01/31 12:42:06, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 12:42:06 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 12:42:06 smbd[2657]: [2017/01/31 12:42:06, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 12:42:06 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 12:42:26 smbd[21312]: [2017/01/31 12:42:26, 0] lib/util_sock.c:read_data(540)
2017-01-31 12:42:26 smbd[21312]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 12:56:39 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 13:06:42 kernel: warning: `vsftpd' uses 32-bit capabilities (legacy support in use)
2017-01-31 13:14:10 smbd[2657]: [2017/01/31 13:14:10, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 13:14:10 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 13:14:10 smbd[2657]: [2017/01/31 13:14:10, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 13:14:10 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 13:14:30 smbd[28949]: [2017/01/31 13:14:30, 0] lib/util_sock.c:read_data(540)
2017-01-31 13:14:30 smbd[28949]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer
2017-01-31 13:29:15 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 13:31:14 kernel: AP SETKEYS WPA2 MAC=34:97:F6:B8:18:CA
2017-01-31 13:32:25 kernel: AP SETKEYS WPA2 MAC=5C:51:88:A7:AB:6E
2017-01-31 13:32:59 WEB: User [admin] logged in from [192.168.1.3] via WEB
Clicca per espandere...
questi intendi?

2017-01-31 08:25:32 smbd[2657]: [2017/01/31 08:25:32, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:25:32 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:25:53 smbd[24188]: [2017/01/31 08:25:53, 0] lib/util_sock.c:read_data(540)
2017-01-31 08:25:53 smbd[24188]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer

solitamente con SMBD ci si riferisce al server samba del router. di solito compaiono quando è attivo un server sul router senza avere nessun dispositivo usb connesso e un dispositivo in rete tenta di accedervi
 
M

Michelemmike

Nuovo Utente
90
6
CPU
AMD FX-6300
Scheda Madre
Gigabyte GA-970A-UD3P rev 2.0
HDD
WD Caviar Blue 1.0Tb
RAM
Kingston HyperX Fury 2X4Gb
GPU
Sapphire Radeon r7 250X
PSU
JOUJYE BW-B520JL 520W
Case
Thermaltake Versa H23
OS
Windows 7 pro x64
emanu37429 ha detto:
questi intendi?

2017-01-31 08:25:32 smbd[2657]: [2017/01/31 08:25:32, 0] printing/pcap.c:pcap_cache_reload(159)
2017-01-31 08:25:32 smbd[2657]: Unable to open printcap file /etc/printcap for read!
2017-01-31 08:25:53 smbd[24188]: [2017/01/31 08:25:53, 0] lib/util_sock.c:read_data(540)
2017-01-31 08:25:53 smbd[24188]: read_data: read failure for 4 bytes to client 192.168.1.3. Error = Connection reset by peer

solitamente con SMBD ci si riferisce al server samba del router. di solito compaiono quando è attivo un server sul router senza avere nessun dispositivo usb connesso e un dispositivo in rete tenta di accedervi
Clicca per espandere...
Ok, grazie per l'informazione
 
M

Michelemmike

Nuovo Utente
90
6
CPU
AMD FX-6300
Scheda Madre
Gigabyte GA-970A-UD3P rev 2.0
HDD
WD Caviar Blue 1.0Tb
RAM
Kingston HyperX Fury 2X4Gb
GPU
Sapphire Radeon r7 250X
PSU
JOUJYE BW-B520JL 520W
Case
Thermaltake Versa H23
OS
Windows 7 pro x64
mi è arrivata la fibra, e ora sto sui 47mbps, ma guardando il grafico segnale/rumore noto una cosa che non vedevo prima: il grafico non è più lineare come lo era con la adsl! è normale?
 

Allegati

  • Immagine.png
    Immagine.png
    254.8 KB · Visualizzazioni: 49
E

emanu37429

Ospite
Michelemmike ha detto:
mi è arrivata la fibra, e ora sto sui 47mbps, ma guardando il grafico segnale/rumore noto una cosa che non vedevo prima: il grafico non è più lineare come lo era con la adsl! è normale?
Clicca per espandere...
Direi che tutto sommato è normale, visto che la vdsl2 copre uno spettro di frequenze molto più ampio, e al salire della frequenza abbiamo attenuazioni più alte e di conseguenza abbiamo un SNR diverso per ogni banda.

P.S. forse in DSL log è più chiaro
 
Stato
Discussione chiusa ad ulteriori risposte.

Ci sono discussioni simili a riguardo, dai un'occhiata!

SS
PROBLEMA Lan/Ethernet cappata a 100 mega
Risposte
5
Visualizzazioni
733
Networking
ßιαςκςοфε
SS

Entra

Hai dimenticato la password?
oppure Accedi utilizzando
Discord Ufficiale Entra ora!

Discussioni Simili