Deny listings with tcpwrappers takes precedence over allow entries. Your hosts.deny was disallowing the connections.
On Thu, Sep 24, 2009 at 17:37, Christopher Smith <[email protected]> wrote: > Hi, > > In my searching before coming to the mailing list, I read somewhere (I can't > find the reference now) that remote gdm login wasn't allowed without tcp > wrappers being enabled. Also, if I check the list if services being > controlled by inetadm I don't see anything I recognize as being for gdm > login, which seems odd. Anyways, I commented the "ALL: ALL" line in > hosts.deny and retried the connection, it worked. > > It does seem like something is awry in inetd/tcp wrappers. From my reading > of the man pages, having ALL: 192.168. in hosts.allow should take effect > before the ALL: ALL in hosts.deny. If I try, ALL: ALL EXCEPT 192.168. in > hosts.deny, the connection fails. Its as if inetd/tcp wrappers isn't > recognising the IP address (I tried ALL: ALL EXCEPT > 192.168.0.0/255.255.255.0 too). For now, I've set ALL EXCEPT gdm: ALL and > things keep working. > > Thanks for your help. -- " ' With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.' Those words were uttered by Judge Aaron Satie as wisdom and warning... The first time any man's freedom is trodden on we’re all damaged." - Jean-Luc Picard, quoting Judge Aaron Satie, Star Trek: TNG episode "The Drumhead" - Alex Smith (K4RNT) - Murfreesboro/Nashville, Tennessee USA _______________________________________________ opensolaris-discuss mailing list [email protected]
