Wednesday, 2013-06-26

*** nowen (~nowen@99-174-93-102.lightspeed.tukrga.sbcglobal.net) has joined #wikid12:48
*** nowen has quit (Quit: Leaving.)14:58
*** nowen (~nowen@99-174-93-102.lightspeed.tukrga.sbcglobal.net) has joined #wikid15:04
*** testuser1 (48c40b51@gateway/web/freenode/ip.72.196.11.81) has joined #wikid17:34
testuser1trying to get ADRegister.jsp to work, and noticed that making a ldap connection to the ad servers is failing17:48
testuser1./ldapsearch  -h 192.168.68.222 -p 389 -b '' -s base '(objectclass=*)' Connect Error Result Code:  91 (Connect Error)17:49
testuser1i have the ad server as a network client in wiKID as well17:50
testuser1any thoughts - does wikid server require iptables?18:09
nowentestuser1: you are most likely correct - iptalbes18:17
nowenyou can open it yourself or add your AD serer as a network client and restart wikid18:18
testuser1i did add it as a network client and restart18:22
testuser1iptables -L -v18:22
testuser1    0     0 ACCEPT     tcp  --  any    any     192.168.68.222       anywhere             state NEW tcp dpt:ldap18:22
nowenand can you connect?18:24
testuser1i can not18:24
testuser1but can from other hosts on the same network18:24
nowenand you get to port 389 on the WiKID server from .222?18:25
testuser1i dont have ldap install on wikid but i can get to 443 and radius from .222 to the wikid server18:28
testuser1does wikid lock down outgoing ports in iptables?18:29
nowenno, but the response from AD needs to come back from AD18:29
testuser1not sure this is the correct command -  iptables -A OUTPUT -p tcp --sport 389 -j ACCEPT18:29
nowenI usually  cut and paste another line from /etc/sysconfig/iptables ;)18:30
nowenso not my strong suit18:30
nowenyou should be able to run 'tcpdump port 389' on wikid and hit is with any request18:31
nowento see if it is open.18:31
nowenand you're not able to login to ADRegister, I assume?18:36
testuser1correct ADRegister not working18:42
nowenis there an error in the Event viewer?18:42
testuser1will do a tcpdump to see if that shows anything18:42
nowenyeah, it should show the outbound at least18:43
nowenany luck testuser1?19:18
testuser1no not yet19:25
testuser1sorry got side tracked19:25
nowennp19:26
testuser1odd, service iptables status shows a redirect19:41
testuser1tcp dpt:389 redir ports 138919:41
nowenahh crap.  delete that line19:41
testuser1does wikid have to restarted after iptable changes?19:46
nowenno19:46
testuser1hmm tcpdump still shows ldap requests going to 138919:58
testuser1 192.168.68.222.iclpv-dm:19:58
nowenyou restarted iptables?19:58
nowenhmm19:58
testuser1yeah19:59
nowenhuh19:59
nowendid wikid put the rule back in?19:59
testuser1will check20:09
testuser1yes20:10
nowenhmm20:12
nowenbut it seems like others have had this working recently, not just testing20:13
testuser1any idea why wikid would put those redirect rules in?20:16
nowenwe used to use that port.  I'm not sure why it would still be in there or why it gets put back in.20:17
testuser1or how i could remove them20:17
nowenwhat version of WiKID is this?20:20
testuser13.5.0-b140320:22
nowenhmm. ok. I'll have to open a ticket to get rid of it20:23
testuser1ok20:24
nowenhmm20:24
nowenis this server in production?20:24
nowenb/c you could test without iptables20:27
nowenjira created.20:28
testuser1in test20:30
testuser1how do i use it with out iptables, just stop iptables?20:30
nowenyes  - 'service iptables stop'20:35
testuser1ok, tcpdump shows the correct port but still got "Authentication to the directory failed for" in ADRegister20:48
testuser1will go through those settings again20:48
nowenok - check the event log in windows too20:48
nowenand you see the AD response via tcpdump?20:54
testuser1sorry have to step away, will be back in a few, thanks for all your help21:11
nowennp21:12
*** testuser1 has quit (K-Lined)22:12
*** nowen has quit (Quit: Leaving.)23:00
*** coolacid has quit (Quit: +++ OK ATH OK)23:03
*** coolacid (~CoolAcid@unaffiliated/coolacid) has joined #wikid23:03

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!