He is right. You can pass DNS and WINS information,
but subnet mask and stuff won't be in there. I don't
believe there is even a field in the IPCP packet for
that. Don't worry about what ipconfig says. It works
right? :)

Michael Le, CCIE #6811

--- nrf  wrote:
> Strange, I was able to pass information like DNS and
> WINS to the client just
> fine on my access-server, using async-bootp.
> 
> Note, you generally don't need to pass things like
> subnet mask or GW to the
> client anyway.  If you are using normal IPCP
> negotiations, then the address
> of the access-server gets passed to the client as a
> host route.  And
> whatever address the access-server hands to the
> client,  Windows
> automatically gives it a /32 mask, even if you try
> to negotiate some other
> mask (I'm sure this behavior can be changed
> somewhere in the registry, I
> just don't know how, and besides, I don't know why
> you would want to).   And
> by default in Windows, once a dial PPP session has
> been negotiated, Windows
> uses that PPP session as a default gateway
> automatically, so your
> access-server doesn't need to hand default gateway
> information to the
> client.  You can turn this behavior off, if you
> want.
> 
> 
> 
> 
> 
> 
> >
> > NetEng wrote:
> >
> > > I have a 2600 w/ NM16AM, I have it configured
> and it works like a champ
> > > except for one thing. How do I pass network
> parameters to the client? I
> > need
> > > to specify the subnet mask, default gw, dns,
> etc. I tried the
> async-bootp
> > > command from global config, but that didnt work.
> I created the ip pool
> just
> > > fine, but I cant find where to set the rest of
> the info. TIA.
[EMAIL PROTECTED]


__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=24245&t=23910
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to