Access to news and readers conf

[Wilson, Sue LCC]

Any ideas???
I have a user at this who keeps getting ... caught as a no permission =
client
when he should be fine

155.78.94.90=20
nslookup on the news server resolves this ip just fine and fast.
nslookup 155.78.94.90
Server:  ns1.usace.army.mil
Address:  140.194.20.7

Name:    nae-wk-xx-35648.nae.ds.usace.army.mil
Address:  155.78.94.90

the only anamoly I see is his ip does not show up as resolved in the =
reports
and logs ....
it reports the ip while others the succeed show the resolved address....
  =20

 from daily report.....
NNRP no permission clients:
System
Conn
155.78.94.90
14
ip54500cbe.adsl-surfen.hetnet.nl
1

also in the daily other there are these addresses reported


from readers conf
/USAC
...skipping
#}

##               USACE

auth "local" {
        hosts: "*.army.mil, army.mil"
        default: "<local>@army.mil"
}
#auth "local" {
#        hosts: "*.usace.army.mil, usace.army.mil"
        #default: "<local>@usace.army.mil"
#}


# This auth group matches a subset of machines and assigns connections
# from there an identity of "<read>@example.com"; these systems should
# only have read access, no posting privileges.

#auth "read-only" {
#    hosts: "*.newuser.example.com"
#    default: "<read>@example.com"
#}

# This auth group matches the systems at a guest institution that should
# be allowed to read the example.events.* hierarchy but nothing else.

#auth "events-only" {
#    hosts: "*.example.org"
#    default: "<events-only>@example.org"
#}

# Finally, this auth group matches some particular systems which have =
been
# abusing the server.  Note that it doesn't assign them an identity at
# all; the "empty" identity created in this fashion won't match any =
users:
# parameters.  Note also that it's last, so anything matching this entry
# will take precedent over everything above it.

#auth "abusers" {
#    hosts: "badguy-dsl.example.com, kiosk.public-access.example.com"
#}


# Now for the access groups.  All of our access groups should have =
users:
# parameters so there are no access groups that match connections =
without
# an identity (such as are generated by the "abusers" entry above).
# First, the default case of local users, who get to read and post to
# everything.

#access "local" {
#    users: "<local>@example.com"
#    newsgroups: "*"
#}

##    USACE

access "local" {
        users: "<local>@army.mil"
        newsgroups: "*"
        access: RP
}


#access "local" {
#        users: "<local>@usace.army.mil"
#        newsgroups: "*"
#       access: RP
#}


# Now, the read-only folks, who only get to read everything.

#access "read-only" {
#    users: "<read>@example.com"
#    read: "*"
#}

# Finally, the events-only people who get to read and post but only to a
# specific hierarchy.

#access "events-only" {
#    users: "<events-only>@example.org"
#    newsgroups: "example.events.*"
#}
[nntp: /news/etc]=20