NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
thom1
Sep 18, 2009Aspirant
afp connection rejected: (bad user/pass) afp log: "too many"
I just solved my own problem, but not without a lot of frustration and head-banging. Here was the post I was writing (eg in the *present* tense) to describe the situation: On my macbook pro, ru...
mikefort
Jul 22, 2011Aspirant
I am having issues with 4.2.18 on an Ultra 4.
I found this thread because it had "too many connections" in it.
I found in my afp.log:
Jul 22 12:17:00.529703 afpd[3130] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 172.28.15.8:60588
Jul 22 12:17:00.531937 afpd[2737] {main.c:185} (I:AFPDaemon): child[3130]: done
Jul 22 12:17:04.379595 afpd[3134] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 172.28.15.8:60589
Jul 22 12:17:04.379739 afpd[3134] {dsi_getsess.c:85} (I:DSI): dsi_getsess: too many connections
Jul 22 12:17:04.380824 afpd[2737] {main.c:183} (I:AFPDaemon): child[3134]: exited 1
I followed this advice and found my /etc/afpd.conf had the same stuff.
In looking at /etc/default/netatalk, the contents were nothing close to correct.
They look like DNS state.
I suspect there is a latent software bug that writes other configuration over this configuration file.
It might even be a problem in updating firmware, because I have been through a few of those too.
Does anyone know of a way to fix this file through normal Frontview actions?
I got the configuration from Frontview -> System -> Config Backup -> Backup.
I don't want to edit the file, then Restore without Tech Support blessing that.
Is there a way such as disabling AFP, then reenabling it? That didn't work :-)
BTW, I also have issues with SMB, so is there a similar configuration file for that?
I found this thread because it had "too many connections" in it.
I found in my afp.log:
Jul 22 12:17:00.529703 afpd[3130] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 172.28.15.8:60588
Jul 22 12:17:00.531937 afpd[2737] {main.c:185} (I:AFPDaemon): child[3130]: done
Jul 22 12:17:04.379595 afpd[3134] {dsi_tcp.c:212} (I:DSI): AFP/TCP session from 172.28.15.8:60589
Jul 22 12:17:04.379739 afpd[3134] {dsi_getsess.c:85} (I:DSI): dsi_getsess: too many connections
Jul 22 12:17:04.380824 afpd[2737] {main.c:183} (I:AFPDaemon): child[3134]: exited 1
I followed this advice and found my /etc/afpd.conf had the same stuff.
In looking at /etc/default/netatalk, the contents were nothing close to correct.
They look like DNS state.
search hsd1.my_isp.net.
nameserver 64.128.77.114
nameserver 64.128.72.114
I suspect there is a latent software bug that writes other configuration over this configuration file.
It might even be a problem in updating firmware, because I have been through a few of those too.
Does anyone know of a way to fix this file through normal Frontview actions?
I got the configuration from Frontview -> System -> Config Backup -> Backup.
I don't want to edit the file, then Restore without Tech Support blessing that.
Is there a way such as disabling AFP, then reenabling it? That didn't work :-)
BTW, I also have issues with SMB, so is there a similar configuration file for that?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!