Window 2003 Server - NSLOOKUP not working

I setup a local development network consisting of three machines all members
of the same domain. Machine one is running DNS, DCHP, & WINS. I am able to
setup and access shared drives and do a nslookup by machiine name using the
cmd line. However If I plug a different PC into this network (a fourth -
non domain member) it is unable to do a nslookup. It can access shared
drives and ping the other PC on the network.
--
Thanks

Gulfstream

does it get a dhcp lease ? Does you lease provide machine one as primary dns
server ?

It may be the dns suffix. Try with fqdn like zzz.domain.com



--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr


"Gulfstream" <(E-Mail Removed)> wrote in message
news:24E920C2-F1DA-4DC9-BEDE-(E-Mail Removed)...
>I setup a local development network consisting of three machines all
>members
> of the same domain. Machine one is running DNS, DCHP, & WINS. I am able
> to
> setup and access shared drives and do a nslookup by machiine name using
> the
> cmd line. However If I plug a different PC into this network (a fourth -
> non domain member) it is unable to do a nslookup. It can access shared
> drives and ping the other PC on the network.
> --
> Thanks
>
> Gulfstream

Your using WINS!?!? Are you freaking kidding me?

Please unplug your cable and turn in your networking badge immediately.

--
"There's no place like 127.0.0.1"

@==)=======---


"Gulfstream" wrote:

> I setup a local development network consisting of three machines all members
> of the same domain. Machine one is running DNS, DCHP, & WINS. I am able to
> setup and access shared drives and do a nslookup by machiine name using the
> cmd line. However If I plug a different PC into this network (a fourth -
> non domain member) it is unable to do a nslookup. It can access shared
> drives and ping the other PC on the network.
> --
> Thanks
>
> Gulfstream

Going this way won't help him so much...

--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr


"double-edged sword" <(E-Mail Removed)> wrote in
message news:CDE0978A-1E31-434C-8536-(E-Mail Removed)...
> Your using WINS!?!? Are you freaking kidding me?
>
> Please unplug your cable and turn in your networking badge immediately.
>
> --
> "There's no place like 127.0.0.1"
>
> @==)=======---
>
>
> "Gulfstream" wrote:
>
>> I setup a local development network consisting of three machines all
>> members
>> of the same domain. Machine one is running DNS, DCHP, & WINS. I am able
>> to
>> setup and access shared drives and do a nslookup by machiine name using
>> the
>> cmd line. However If I plug a different PC into this network (a
>> fourth -
>> non domain member) it is unable to do a nslookup. It can access shared
>> drives and ping the other PC on the network.
>> --
>> Thanks
>>
>> Gulfstream

double-edged sword,
i look forward to the day you venture out of your mom basement and I get the
opportunity to smack you so hard that your head spins - kind of like
highschool -
--
Mathieu Chateau,

Thanks for your help. It did lead me down the right direction. BTW - I'm
not using WINS anymore.

Thanks

Gulfstream


"double-edged sword" wrote:

> Your using WINS!?!? Are you freaking kidding me?
>
> Please unplug your cable and turn in your networking badge immediately.
>
> --
> "There's no place like 127.0.0.1"
>
> @==)=======---
>
>
> "Gulfstream" wrote:
>
> > I setup a local development network consisting of three machines all members
> > of the same domain. Machine one is running DNS, DCHP, & WINS. I am able to
> > setup and access shared drives and do a nslookup by machiine name using the
> > cmd line. However If I plug a different PC into this network (a fourth -
> > non domain member) it is unable to do a nslookup. It can access shared
> > drives and ping the other PC on the network.
> > --
> > Thanks
> >
> > Gulfstream