Re: Client Machine cannot see Active Directory

I wish there were such an easy explanation.

The box that cannot see the AD services is on 1.0 subnet in the office with
a wired 100Mb connection. Currently there are no PCs on the wireless subnet.


The pix VPN allows all traffic between 1.0 and 0.0

The problem started when we added the NAS box (a dell powervault 745N) to
the network at 192.168.1.90

The pix 515 at the office has an inside address of 192.168.1.254 and
connects to the pix 501 which uses DHCP from our provider on the outside
address. (this setup works flawlessly)

So there arent any crazy circumstances for the problem machine to
overcome... it is hooked up behind the Pix 515 on the 1.0 subnet.

Last I spoke with the user she was able to get to the DFS shares and print,
so the problem for the user has subsided, but these DNS errors seem to be
lingering...

Derek

"Ace Fekay [MVP]" wrote:

> In news:56B66415-5E0F-4C33-976B-1B49A1FF044E@xxxxxxxxxxxxx,
> Derek Schauland <DerekSchauland@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post,
> which I then commented about below:
> > We have multiple subnets 192.168.1.0, 192.168.0.0, and 192.168.3.0
> >
> > 3.0 uses a netgear wireless router to allow wireless access for some
> > devices
> >
> > 1.0 is the subnet for the majority of our users and servers
> >
> > 0.0 is the subnet for our remote location. This subnet is connected
> > by a hardware vpn between a Cisco Pix 515 and a Cisco Pix 501. The
> > pix 515 has 3 interfaces the 501 has 2
> >
> > I will make sure to disable the non-used NICs and remove the
> > 169.254.148.31 entry.
> >
> > I have some web applications being sent out to the internet using NAT
> > on the Pix 515 other than that just the VPN from the remote site is
> > coming in between subnets.
> >
> >
> > Derek
>
> Cool, I'm getting a better idea now of your infrastructure. You sure did
> inherit a headache.
>
> Ok, is the client having problems accessing AD on the wireless 3.x subnet?
> Does the PIX box connect the 1.0 and the 0.0 subnet?
>
> Is PIX allowing ALL traffic between subnets?
>
> Going back to your original post, you said:
> > I have one client that is unable to see Active
> > Directory or access shares via
> > \\servername for our new NAS
>
> What is the NAS box? The PIX box? Is the client connected thru a VPN from
> home or something when it can't access AD services? If so, what IP address
> does the client machine have at home? Does it match the IP address range at
> the office? (0.0 or 1.0)?
>
>
>
> Ace
>
>
>
.

Relevant Pages

  • Re: Someone can explain this to me?
    ... > Cisco3640 core router as dgw of the network, ... > Eigrp protocol running on all the devices except the pix. ... > 3640 (remember, this is the dgw of the subnet), all seems ok. ... It sounds like the 1712 is advertising a route to 172.16.1.107 to the ...
    (comp.dcom.sys.cisco)
  • Cisco PIX SSH/telnet dDOS vulnerability CSCdy51810
    ... Cisco PIX SSH/telnet DOS vulnerability CSCdy51810 ... will answer to connection request sent to the subnet ... BindView's RAZOR team) show the free memory counter ...
    (Bugtraq)
  • Someone can explain this to me?
    ... Class B subnet 172.16.0.0/16 with about 500 hosts. ... Cisco Pix506 vpn gateway, address 172.16.1.107 ... Eigrp protocol running on all the devices except the pix. ...
    (comp.dcom.sys.cisco)
  • Changed Inside IP subnet on PIX 501, cant VPN to PIX 515
    ... So I have a PIX 501 that I configured to use the 10.14.0.0/16 subnet. ... Outside Interface is DHCP, ComCast Internet ... Outside interface it DHCP/PPPoE, AT&T DSL Internet ...
    (comp.dcom.sys.cisco)
  • Re: Client Machine cannot see Active Directory
    ... > 3.0 uses a netgear wireless router to allow wireless access for some ... > 0.0 is the subnet for our remote location. ... > by a hardware vpn between a Cisco Pix 515 and a Cisco Pix 501. ... is the client having problems accessing AD on the wireless 3.x subnet? ...
    (microsoft.public.win2000.active_directory)
Quantcast