• October 22, 2020, 08:33:26 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 [2]

Author Topic: Repeated ConnectToServer failure in logs  (Read 4157 times)

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #15 on: April 15, 2020, 02:45:16 PM »

Link>Welcome!

  • What region are you located?

What ISP Modem Mfr. and model # do you have?


Did anyone resolve this issue? Seeing the same thing with my new 2680. Have both wired and wireless devices. Have tried using both V1.03 & V1.04 firmware and these errors still fill up the logs.

Andy
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

amurray1522

  • Level 1 Member
  • *
  • Posts: 2
Re: Repeated ConnectToServer failure in logs
« Reply #16 on: April 15, 2020, 04:13:53 PM »

In the Northeast, using Xfinity gig speed. Moden is a netgear CM1150V

Thanks
Andy
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #17 on: April 16, 2020, 05:57:28 AM »

Have you been noticing any problems with the router other than this logging?
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

daack

  • Level 1 Member
  • *
  • Posts: 1
Re: Repeated ConnectToServer failure in logs
« Reply #18 on: April 23, 2020, 01:47:43 AM »

I'm also experiencing the same issue with my new D-Link DIR-2680 (firmware 1.04).

I'm based in Sydney, Australia (ISP: Aussie Broadband).

I'm intermittently seeing issues on my MacBook Pro, specifically on google.com and www.google.com not being able to resolve. I've tried setting Cloudflare DNS (1.1.1.1 / 1.0.0.1) and Google DNS (8.8.8.8 / 8.8.4.4) on the router and separately also on the MacBook. This did not help at all. It's not browser related; it happens when I ping said domains, and same result from Chrome / Safari.

I've not had issues on my phone (Google Pixel), except for occasionally reporting that my Wi-Fi doesn't have internet, while the connection seems just fine.

I've restarted the router an hour ago, so far no issues (although the log entries immediately showed up again).

In general, the issues seems to only be around google.com and www.google.com not being able to resolve. Otherwise it works well.

I've registered for a D-Link cloud account and downlaoded the D-Fend / McAfee app. However I already had these issues before I registered.
« Last Edit: April 23, 2020, 01:51:44 AM by daack »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #19 on: April 23, 2020, 05:57:03 AM »

I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this.
Link> Tech Support Contact Information
We find that phone contact has better immediate results over using email.
Let us know how it goes please.

I'm also experiencing the same issue with my new D-Link DIR-2680 (firmware 1.04).

I'm based in Sydney, Australia (ISP: Aussie Broadband).

I'm intermittently seeing issues on my MacBook Pro, specifically on google.com and www.google.com not being able to resolve. I've tried setting Cloudflare DNS (1.1.1.1 / 1.0.0.1) and Google DNS (8.8.8.8 / 8.8.4.4) on the router and separately also on the MacBook. This did not help at all. It's not browser related; it happens when I ping said domains, and same result from Chrome / Safari.

I've not had issues on my phone (Google Pixel), except for occasionally reporting that my Wi-Fi doesn't have internet, while the connection seems just fine.

I've restarted the router an hour ago, so far no issues (although the log entries immediately showed up again).

In general, the issues seems to only be around google.com and www.google.com not being able to resolve. Otherwise it works well.

I've registered for a D-Link cloud account and downlaoded the D-Fend / McAfee app. However I already had these issues before I registered.
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

gablinux

  • Level 1 Member
  • *
  • Posts: 2
Re: Repeated ConnectToServer failure in logs
« Reply #20 on: April 25, 2020, 11:27:39 PM »

The issue of the ConnectToServer in the log files coninue in the log, with any device to connect to de Wlan and Lan.
Model Name: DIR-2660   Hardware Version: A1   Firmware Version: 1.04            ISP: Pepephone/Movistar
and the log file:


2020-04-26 06:18:03 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-04-26 06:18:04 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-04-26 06:18:05 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-04-26 06:18:06 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:27 Err:-1 Errno:0 Success
2020-04-26 06:18:06 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-04-26 06:18:54 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:27 Err:-1 Errno:0 Success
2020-04-26 06:18:54 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-04-26 06:18:57 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-04-26 06:18:57 syslog: server6_recv: received solicit from fe80::42b0:34ff:fe80:46bd
2020-04-26 06:18:57 syslog: dhcp6_get_options: get DHCP option elapsed time, len 2
2020-04-26 06:18:57 syslog:   elapsed time: 65535
2020-04-26 06:18:57 syslog: dhcp6_get_options: get DHCP option client ID, len 10
2020-04-26 06:18:57 syslog:   DUID: 00:03:00:01:40:b0:34:80:46:be
2020-04-26 06:18:57 syslog: dhcp6_get_options: get DHCP option identity association, len 12
2020-04-26 06:18:57 syslog:   IA_NA: ID=3, T1=0, T2=0
2020-04-26 06:18:57 syslog: dhcp6_get_options: get DHCP option option request, len 12
2020-04-26 06:18:57 syslog:   requested option: status code
2020-04-26 06:18:57 syslog:   requested option: server unicast
2020-04-26 06:18:57 syslog:   requested option: DNS
2020-04-26 06:18:57 syslog:   requested option: domain search list
2020-04-26 06:18:57 syslog:   requested option: client FQDN
2020-04-26 06:18:57 syslog:   requested option: preference
2020-04-26 06:18:57 syslog: dhcp6_get_options: get DHCP option client FQDN, len 8
2020-04-26 06:18:57 syslog: react_solicit: client ID 00:03:00:01:40:b0:34:80:46:be
2020-04-26 06:18:57 syslog: make_iana_from_pool: called
2020-04-26 06:18:57 syslog: get_free_address_from_pool: called (pool=dhcpv6pool)
2020-04-26 06:18:57 syslog: get_free_address_from_pool: no available address
2020-04-26 06:18:57 syslog: copy_option: set server ID (len 10)
2020-04-26 06:18:57 syslog: copy_option: set status code (len 2)
2020-04-26 06:18:57 syslog: server6_send: transmit advertise to fe80::42b0:34ff:fe80:46bd
2020-04-26 06:18:58 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-04-26 06:18:59 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-04-26 06:19:00 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:27 Err:-1 Errno:0 Success
2020-04-26 06:19:00 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef2020-04-26 07:48:48 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-04-26 07:48:49 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-04-26 07:48:50 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:27 Err:-1 Errno:0 Success
2020-04-26 07:48:50 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-04-26 07:48:53 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-04-26 07:48:54 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-04-26 07:48:55 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
2020-04-26 07:48:56 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:27 Err:-1 Errno:0 Success
2020-04-26 07:48:56 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-04-26 07:48:59 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-04-26 07:49:00 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-04-26 07:49:01 syslogd exiting
2020-04-26 07:49:01 [SYSLOG]: start BusyBox v1.22.1
2020-04-26 07:49:01 crond[5979]: crond: crond (busybox 1.22.1) started, log level 8
2020-04-26 07:49:02 syslog: dnssd_clientstub ConnectToServer: connect() failed path:/var/run/mdnsd Socket:27 Err:-1 Errno:0 Success
2020-04-26 07:49:02 syslog: dnssd_clientstub DNSServiceRefDeallocate called with NULL DNSServiceRef
2020-04-26 07:49:05 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
2020-04-26 07:49:06 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
2020-04-26 07:49:07 syslog: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
             total         used         free       shared      buffers
Mem:        250560       141720       108840            0         7508
-/+ buffers:             134212       116348
Swap:            0            0            0
  PID USER       VSZ STAT COMMAND
    1 admin     1688 S    /sbin/procd
    2 admin        0 SW   [kthreadd]
    3 admin        0 SW   [ksoftirqd/0]
    5 admin        0 SW<  [kworker/0:0H]
    7 admin        0 SW   [migration/0]
    8 admin        0 SW   [rcu_bh]
    9 admin        0 SW   [rcu_sched]
   10 admin        0 SW   [migration/1]
   11 admin        0 SW   [ksoftirqd/1]
   13 admin        0 SW<  [kworker/1:0H]
   14 admin        0 SW   [migration/2]
   15 admin        0 SW   [ksoftirqd/2]
   17 admin        0 SW<  [kworker/2:0H]
   18 admin        0 SW   [migration/3]
   19 admin        0 SW   [ksoftirqd/3]
   21 admin        0 SW<  [kworker/3:0H]
   22 admin        0 SW<  [khelper]
   23 admin        0 SW   [kdevtmpfs]
   24 admin        0 SW<  [netns]
   25 admin        0 SW<  [writeback]
   26 admin        0 SW<  [bioset]
   27 admin        0 SW<  [kblockd]
   28 admin        0 SW   [khubd]
   33 admin        0 SW   [kswapd0]
   34 admin        0 SWN  [ksmd]
   35 admin        0 SW   [fsnotify_mark]
   36 admin        0 SW<  [crypto]
   43 admin        0 SW<  [deferwq]
   44 admin        0 SW   [kworker/u8:1]
  140 admin      928 S    /sbin/askfirst ttyS1 /bin/login
  257 admin     1052 S    /sbin/ubusd
  281 admin     1300 S    /usr/bin/if_monitor
  292 admin     5136 S    /sbin/preinit
  305 admin        0 SWN  [jffs2_gcd_mtd6]
  321 admin     1324 S    /sbin/tw_hotplug
  326 admin        0 SW   [scsi_eh_0]
  327 admin        0 SW   [usb-storage]
  328 admin        0 SW   [scsi_eh_1]
  329 admin        0 SW   [usb-storage]
  341 admin     5692 S    /bin/nvram_daemon
  347 admin        0 SW   [kworker/u8:2]
  374 admin        0 SWN  [jffs2_gcd_mtd8]
  857 admin     4060 S    /sbin/stad 1
  858 admin     4064 S    /sbin/stad 2
  887 admin        0 SW   [ufsd_sda1]
 1055 admin      952 S    nl_server -i br0 -s DIR-2660 -s DIR-26605306 -s DIR-
 1057 admin      940 S    nl_server -i br0 -s DIR-2660 -s DIR-26605306 -s DIR-
 1059 admin     1320 S    mDNSResponder -b -i br0 -f /tmp/mdns_resp.conf -e DI
 1129 admin     4892 S    /bin/lighttpd -f /etc_ro/lighttpd/lighttpd.conf -m /
 1137 admin     7904 S    /etc_ro/lighttpd/www/web/HNAP1/prog.fcgi
 1145 admin     4248 S    /usr/sbin/timer
 1158 admin     7928 S    /etc_ro/lighttpd/www/web/HNAP1/prog.fcgi
 1177 admin     4536 S    /sbin/myinfo.cgi
 1203 admin     5528 S    /sbin/smbd -D -F -s /etc/smb.conf
 1214 admin     5528 S    /sbin/smbd -D -F -s /etc/smb.conf
 1306 admin        0 SW   [RtmpCmdQTask]
 1307 admin        0 SW   [RtmpWscTask]
 1308 admin        0 SW   [HwCtrlTask]
 1309 admin        0 SW   [ser_task]
 1359 admin        0 SW   [RtmpMlmeTask]
 1455 admin        0 SW   [RtmpCmdQTask]
 1456 admin        0 SW   [RtmpWscTask]
 1457 admin        0 SW   [HwCtrlTask]
 1458 admin        0 SW   [ser_task]
 1479 admin        0 SW   [RtmpMlmeTask]
 1539 admin     1472 S    bndstrg2 -i rai0 -i ra0
 1681 admin     4004 S    mosquitto -c /etc/mosquitto/mosquitto.conf -d
 1688 admin     5476 S    sbd
 1692 admin     7200 S    apsond
 1696 admin     7200 S    apsond
 1697 admin     7200 S    apsond
 1698 admin     7200 S    apsond
 1699 admin     7200 S    apsond
 1700 admin     7200 S    apsond
 1701 admin     7200 S    apsond
 1703 admin     4504 S    meshd
 2466 admin        0 SW   [kworker/2:0]
 2841 admin        0 SW   [kworker/3:0]
 2880 admin        0 SW   [kworker/1:2]
 3100 admin      976 S    /sbin/udhcpc -i eth3.20 -p /var/run/udhcpc-wan_wan0.
 3116 admin     2472 S    zebra -u admin -g admin -f /tmp/zebra.conf -d
 3126 admin     2128 S    ripd -u admin -g admin -f /tmp/ripd.conf -d
 3145 admin     1420 S    /sbin/pppoe-relay -S eth3.20 -C br0
 3156 admin     2240 S    /usr/sbin/dhcp6s -c /tmp/dhcp6s.conf -k /tmp/dhcp6sc
 3177 admin     1040 S    /usr/sbin/radvd -m none -C /tmp/radvd.conf -d 5
 3401 admin     1156 S    miniupnpd -f /tmp/miniupnpd/miniupnpd.conf -G
 3413 admin     1276 S    inadyn -f /var/inadyn.conf -P /var/run/inadyn.pid --
 3613 admin        0 Z    [sh]
 3783 admin        0 SW   [kworker/1:0]
 3972 admin     3020 S    /usr/bin/xl2tpd -c /etc/xl2tpd.conf -D
 3986 admin     1276 S    inadyn -f /var/inadyn0.conf -P /var/run/inadyn0.pid
 4036 admin        0 SW   [kworker/2:2]
 4168 admin     1976 S    {_plutorun} /bin/sh /lib/ipsec/_plutorun --debug  --
 4169 admin     1964 S    logger -s -p daemon.error -t ipsec__plutorun
 4170 admin     1984 S    {_plutorun} /bin/sh /lib/ipsec/_plutorun --debug  --
 4171 admin     1980 S    {_plutoload} /bin/sh /lib/ipsec/_plutoload --wait no
 4174 admin     2612 S    /lib/ipsec/pluto --nofork --secretsfile /etc/ipsec.s
 4176 admin     2592 S    {pluto} _pluto_adns -- <idle>
 4178 admin     2604 S N  /lib/ipsec/pluto -- pluto helper  #  0
 4179 admin     2604 S N  /lib/ipsec/pluto -- pluto helper  #  1
 4181 admin     2604 S N  /lib/ipsec/pluto -- pluto helper  #  2
 4484 admin        0 SW   [kworker/3:2]
 4760 admin     1036 S    /usr/sbin/odhcp6c -f -R -p /var/run/udhcpc-wan_wan0.
 4789 admin     4704 S    time_client --action daemon
 4848 admin     1344 S    infocgi
 4866 admin     1984 S    {mydlink_watchdo} /bin/sh /mydlink/mydlink_watchdog.
 4943 admin      988 S    omcproxy -e3 eth3.20 br0 scope=realm
 4976 admin     1436 S    /bin/dnsmasq -C /tmp/dnsmasq.conf -6 /tmp/dnsmasq_dh
 4978 admin     1428 S    /bin/dnsmasq -C /tmp/dnsmasq.conf -6 /tmp/dnsmasq_dh
 5012 admin     5740 S    /mydlink/da_adaptor -s LD_LIBRARY_PATH=/mydlink/lib
 5017 admin     5740 S    /mydlink/da_adaptor -s LD_LIBRARY_PATH=/mydlink/lib
 5018 admin     5740 S    /mydlink/da_adaptor -s LD_LIBRARY_PATH=/mydlink/lib
 5047 admin     5740 S    /mydlink/da_adaptor -s LD_LIBRARY_PATH=/mydlink/lib
 5048 admin     5740 S    /mydlink/da_adaptor -s LD_LIBRARY_PATH=/mydlink/lib
 5049 admin     5740 S    /mydlink/da_adaptor -s LD_LIBRARY_PATH=/mydlink/lib
 5051 admin     5740 S    /mydlink/da_adaptor -s LD_LIBRARY_PATH=/mydlink/lib
 5052 admin     5740 S    /mydlink/da_adaptor -s LD_LIBRARY_PATH=/mydlink/lib
 5532 admin        0 SW   [kworker/2:1]
 5956 admin     1960 S    syslogd -L -R 192.168.1.24
 5979 admin     1972 S    /usr/sbin/crond -c /tmp/schedule/ -f
 5999 admin     1956 S    sleep 5
 6083 admin     1972 S    sh -c arping -I br0 192.168.1.55 -c 1 > /var/arping_
 6084 admin     1968 S    arping -I br0 192.168.1.55 -c 1
 6089 admin     1972 S    sh -c ps >> /etc_ro/lighttpd/www/web/messages
 6090 admin     1964 R    ps
17463 admin        0 SW   [kworker/0:1]
30415 admin        0 SW   [kworker/3:1]
32245 admin        0 SW   [kworker/0:2]
br0       Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:06 
          inet addr:192.168.1.1  Bcast:192.168.1.63  Mask:255.255.255.192
          inet6 addr: fe80::f68c:ebff:fecc:5306/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14277411 errors:0 dropped:39 overruns:0 frame:0
          TX packets:27550854 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6036247574 (5.6 GiB)  TX bytes:34433402883 (32.0 GiB)

br1       Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:0A 
          inet6 addr: fe80::a4ea:2aff:fe61:73f9/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:188 (188.0 B)

br2       Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:0B 
          inet6 addr: fe80::c4b1:c6ff:fef9:bcf/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:188 (188.0 B)

br3       Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:0C 
          inet6 addr: fe80::947a:6eff:fe47:28c0/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:188 (188.0 B)

eth2      Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:06 
          inet6 addr: fe80::f68c:ebff:fecc:5306/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5566927 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14852857 errors:0 dropped:148 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1934746296 (1.8 GiB)  TX bytes:2461071431 (2.2 GiB)
          Interrupt:3

eth2.1    Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:06 
          inet6 addr: fe80::f68c:ebff:fecc:5306/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:262413 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:52947833 (50.4 MiB)

eth2.2    Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:06 
          inet6 addr: fe80::f68c:ebff:fecc:5306/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3307676 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11691569 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:287990629 (274.6 MiB)  TX bytes:16977694140 (15.8 GiB)

eth2.3    Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:06 
          inet6 addr: fe80::f68c:ebff:fecc:5306/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:262413 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:52947833 (50.4 MiB)

eth2.4    Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:06 
          inet6 addr: fe80::f68c:ebff:fecc:5306/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2259251 errors:0 dropped:171 overruns:0 frame:0
          TX packets:2636602 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1546550981 (1.4 GiB)  TX bytes:2498161840 (2.3 GiB)

eth3      Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:09 
          inet6 addr: fe80::f68c:ebff:fecc:5309/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27694674 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13826518 errors:0 dropped:40 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:668847493 (637.8 MiB)  TX bytes:1890621040 (1.7 GiB)

eth3.20   Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:09 
          inet addr:100.102.38.199  Bcast:100.102.255.255  Mask:255.255.0.0
          inet6 addr: fe80::f68c:ebff:fecc:5309/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27694654 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13826553 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:34530080086 (32.1 GiB)  TX bytes:6130284406 (5.7 GiB)

imq0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          UP RUNNING NOARP  MTU:16000  Metric:1
          RX packets:27426632 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27486858 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:11000
          RX bytes:3896594863 (3.6 GiB)  TX bytes:3981526916 (3.7 GiB)

imq1      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          UP RUNNING NOARP  MTU:16000  Metric:1
          RX packets:13750734 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13861241 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:11000
          RX bytes:1627889277 (1.5 GiB)  TX bytes:1660314572 (1.5 GiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1591000 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1591000 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:128446065 (122.4 MiB)  TX bytes:128446065 (122.4 MiB)

mast0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 
          UP RUNNING NOARP  MTU:16260  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ra0       Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:07 
          inet6 addr: fe80::f68c:ebff:fecc:5307/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2629999 errors:1258 dropped:0 overruns:0 frame:0
          TX packets:3539362 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3000
          RX bytes:550088673 (524.6 MiB)  TX bytes:3395270748 (3.1 GiB)
          Interrupt:4

rai0      Link encap:Ethernet  HWaddr F4:8C:EB:CC:53:08 
          inet6 addr: fe80::f68c:ebff:fecc:5308/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12859591 errors:2270 dropped:0 overruns:0 frame:0
          TX packets:15997526 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3000
          RX bytes:1804602445 (1.6 GiB)  TX bytes:1043126619 (994.8 MiB)
          Interrupt:24

Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #21 on: April 26, 2020, 08:55:26 AM »

Please contact your regional D-Link support office and ask for help and information regarding this.
Link> Tech Support Contact Information
We find that phone contact has better immediate results over using email.
Let us know how it goes please.

The issue of the ConnectToServer in the log files coninue in the log, with any device to connect to de Wlan and Lan.
Model Name: DIR-2660   Hardware Version: A1   Firmware Version: 1.04            ISP: Pepephone/Movistar
and the log file:


Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

vkum013

  • Level 1 Member
  • *
  • Posts: 4
Re: Repeated ConnectToServer failure in logs
« Reply #22 on: May 04, 2020, 01:08:58 AM »

Has the solution to this problem found? I have a DIR-2680 with same issue
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #23 on: May 04, 2020, 09:35:15 AM »

Please contact your regional D-Link support office and ask for help and information regarding this.
Link> Tech Support Contact Information
We find that online chat or phone contact has better immediate results over using email.
Let us know how it goes please.

Has the solution to this problem found? I have a DIR-2680 with same issue
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

vkum013

  • Level 1 Member
  • *
  • Posts: 4
Re: Repeated ConnectToServer failure in logs
« Reply #24 on: August 05, 2020, 05:27:45 PM »

I have contacted D-link tech support multiple times, have had my router replaced but the problem persists. So far D-link Support has not been able to provide an explanation on why these Syslog errors are getting logged and what the resolution is. Tried multiple things as requested by them but nothing has worked/resolved the issue.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #25 on: August 06, 2020, 10:11:06 AM »

Is the router exhibiting problems?

I have contacted D-link tech support multiple times, have had my router replaced but the problem persists. So far D-link Support has not been able to provide an explanation on why these Syslog errors are getting logged and what the resolution is. Tried multiple things as requested by them but nothing has worked/resolved the issue.
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #26 on: August 06, 2020, 01:11:36 PM »

Ok, so I took a dive into this with my 2680. I'm seeing the same thing. Just had 1 wired PC and wireless was disabled. Even tried with just 1 browser and tab open to the routers web page. Rebooted and these entries continue soon after the router is back to ready. I got with on online chat support and got a bit more steps to try. I disconnected the router from ISP services and rebooted the router. After giving 3-5 minutes, these log entries are NOT seen. Only 5 lines are seen. One the modem services was re-connected, the log entries began again. Support feels this is a router/FW side issue.

So they would like me and any other users experiencing this, to send support@dlink.com an email with all your information, troubleshooting steps, FW version loaded and anything else you think would help them review this more. Include any other D-Link routers that you may have and tried to compare. Also ISP service and modem mfr and model would be helpful as well. Send this off in a email and let see if we can get D-link to take a look and make a correction regarding this.

Other than this, the router seems to work ok. If users are experiencing other problems that I don't see, please include that as well.

Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

vkum013

  • Level 1 Member
  • *
  • Posts: 4
Re: Repeated ConnectToServer failure in logs
« Reply #27 on: August 09, 2020, 04:23:00 PM »

Thank you for looking into this and confirming its not just an isolated case! I contacted D-link Support again and they have offered me another replacement (3rd one) but I guess there's no point in replacing as they will all behave the same until D-link releases a f/w fix. Generally, it seems to be working fine but there are intermittent moments of internet dropouts and the router rebooting/crashing.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #28 on: August 10, 2020, 08:21:40 AM »

  • What ISP Service do you have? Cable or DSL?
  • What ISP Modem Mfr. and model # do you have?
  • Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner to find out. How many?

What devices do you have connected?

Thank you for looking into this and confirming its not just an isolated case! I contacted D-link Support again and they have offered me another replacement (3rd one) but I guess there's no point in replacing as they will all behave the same until D-link releases a f/w fix. Generally, it seems to be working fine but there are intermittent moments of internet dropouts and the router rebooting/crashing.
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49275
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Repeated ConnectToServer failure in logs
« Reply #29 on: August 11, 2020, 02:15:47 PM »

Here is what I got from D-Link support about these log entries:
"Date of Reply: 8/10/2020 2:54:17 PM

Products: DIR-2680-US

I have been told that it is just some debugging info that is leaked into the syslog that will be removed in the next firmware release. It is nothing to be concerned about. "
Logged
"Nothing Funny about It...." We are not here to Impress anyone! You have a be a COMPETENT user first to under stand COMPETENT help!
Pages: 1 [2]