Connection reinitialised, DA not available

[Solden]

All of a sudden (although "all of a sudden" never happens in computers, but I cannot pinpoint the source of the problem ) DA refuses to respond.

It is showing up in the process list, so I assume it is running (even did a restart of DA and reboot of server). But when going to server:2222 I get a (translated from Dutch) "connection reinitialised" error.

I cannot get into DA anymore. I'm a little out of options. Does anyone recognize this problem?

 

[Shark]

Ditto

Sitting here waiting for the big game and I needed to refresh IE/DA page. It never came back. Rebooted the server, no DA. SSH works, ftp works, http is serving sites, exim is good, named no problem. netstat -tupan:

tcp 0 0.0.0.0:2222 0.0.0.0:* LISTEN 23679/directadmin

Firewall:

Feb 05 13:33:46 apf(2211): opening inbound tcp port 2222 on 0/0

# service directadmin status
directadmin (pid 25843 25842 25548...) is running...
[root@ chkrootkit-0.45]# service directadmin restart
Stopping DirectAdmin: [ OK ]
Starting DirectAdmin: [ OK ]
[root@ chkrootkit-0.45]#

I'm going through /var/log/directadmin...

I see nothing in the logs. I'm uptodate on the DA 1.26 ish. I'm logging on http://xxx.xxx.xxx.xxx:2222/ as usual. Any thoughts?

Thanks,

Dave~

 

[Solden]

I'm glad someone recognizes it, you have indeed the same problem as I have. Same description.

Now I hope someone else might know the solution...

Edit: really all of a sudden DA is alive again. I left the server allone for a few days, so it wasn't me.
But now I still have no idea what caused this and I don't want ot to happen again...

 

[Shark]

Huh? lol

As it turns out for me. My problem is the VOIP router from Linksys. Put a computer in DMZ, Linksys port scanned and port 2222 wasn't available- nothing below 8000 was. They said that sometimes the protection/security is so strong the port just won't stay open???? Port triggering and forwarding don't work.

No changes made, just stopped working. Been through every reset in the book. DA works fine if I connect directly to the cable modem. Linksys concluded bad router, return it. It was 28 days old...

Thanks,

Dave~

 

[Solden]

Maybe that's the same with me: when at my work I can easily log in, but at home I cannot.
I'm using an Airport Express (Apple) as a router. However, I've never had problems before with this configuration...

 

[nobaloney]

Any router can suffer early death <smile>.

I've had a Linksys VoIP router fail the first month; Vonage replaced it.

I also have a D-Link router lose track of my print server when I have a GrandStream BudgeTone-101 SIP phone on my network.

That all said, no router should block an outbound request to any port unless so configured, nor should it block any inbound response to any outbound request, also unless so configured.

Solden, your ISP may be blocking port 2222; search these forums for 2222 and you'll find some threads and possible solutions.

Jeff

 

[Shark]

FWIW

Also, if you have *Blacklist IPs for excessive login attempts* checked in Administrator Settings, you may want to look at:

/usr/local/directadmin/data/admin/ip_blacklist

Dave~

 

[Solden]

Shark, you're my hero. My IP (my own!) was indeed in that file. I don't know why, as I haven't entered my passwords wrongly ever. But ok. It works again...
Thanks!