DHCP Question about server options

Hi,

I just set up the first machine of a new W2K3 network. The roles of this
machine are the typical ones -- DC, AD, DNS, DHCP. Out of the box, DHCP is
just giving out IP address and subnet info. What other server options should
I select? I had an issue before on another network -- a W2K network -- where
people who VPN into the system can only locate network objects using their
IPs. Nobody could locate anything using names. I think this was due to not
having any DNS server data being provided by the DHCP server. What do you
think? I want to set up this network 100% by the book. So I'd appreciate
some pointers about the perfect DHCP server setup. Thanks.

Thanks,

Sam

"Sam" <(E-Mail Removed)> wrote in message
news:ujXDFG%(E-Mail Removed)...
> just giving out IP address and subnet info. What other server options
should
> I select? ...............................
> think? I want to set up this network 100% by the book. So I'd appreciate
> some pointers about the perfect DHCP server setup. Thanks.

The "keep it simple" method works everytime it is tried. Always stay in the
broundaries of what you know understand and can troubleshoot. There's always
time to get more complicated later.

You can include all the "basic" network settings. I would include them at
the Scope level as "Scope Options" instead of at the Server level (Server
Options) so that you can use different settings in different scopes if the
need ever arises. You use one scope per subnet so the "Scope Options" are a
way to give each subnet its own settings that pertain to it.

In addition to the IP# and mask, there is the Default Gateway ("Router" in
DHCP), the WINS servers IP# and the DNS IP#s. Here is a list with the option
numbers that are your "core" settings:

003 Router = Your Default Gateway for the client
006 DNS Servers = Your AD/DNS Server's IP#
015 DNS Domain Name = Your Active Directory Domain Name
044 WINS/NBNS Servers = Your WINS Server IP#
046 WIN/NBT Node Type = I usually use 0x8, ...the choice is yours.

In creating the scope you should use the entire full address range of that
particular subnet and then use "Exclusions" to prevent certain addresses
from being given out by DHCP that you may need to use for static adddresses
on certain devices/hosts. You can also use Reservations to simulate the
same effect as a static address, however this still leaves the host
dependent on a functioning DHCP which may not always be desireable because
some things need to run even if the DHCP server goes down.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

this may help. quoted from http://www.ChicagoTech.net
Unable to browse through PPTP/VPN connection
Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN
server, and you attempt to connect to a computer using a PPTP/VPN client,
you may experience following problem: 1) The NetBIOS name of the computer to
which you are attempting to connect is not resolved. 2) You may receive an
error message similar to the following error message: "System error 53 has
occurred. The network path was not found" when using net view or opening
Network Knighthood.
2. If the WINS server is not on the same computer as the PPTP server and you
attempt to connect to a computer using a PPTP client, you may be able to
connect to computers on your local area network (LAN), but you may be unable
to connect to network shares or resources on the PPTP server.
Resolutions: Inability to browse often means the client can't resolve
NetBIOS names.
1. If this is a workgroup network, enable NetBIOS over TCP/IP on the server
and clients.
2. If this is domain network and the WINS server is on the same computer as
the PPTP/VPN server, move the WINS server to a different computer.
3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in addition
to, TCP/IP.
4. By default, most routers and firewalls prevent the transmission of
NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139. Try
to enable UDP ports 137 and 138 and TCP port 139 across all routers and
firewalls between the PPTP/VPN client and PPTP/VPN server.
5. Make sure the client has correct DNS, WINS and Master Browser settings.
6. Make sure the default gateway points to the remote network rather than to
the ISP.
7. Some ISP might block ports required for NetBIOS name broadcasts.
8. If WINS address is not distributed upon connection to VPN, LMHOSTS should
be configured to enable Domain to be located.
9. If you try these techniques and the client still can't browse, try to use
UNC to connect to the remote resources by ip, for example, use the net use
h: \\serverip\sharename command.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Sam" <(E-Mail Removed)> wrote in message
news:ujXDFG%(E-Mail Removed)...
> Hi,
>
> I just set up the first machine of a new W2K3 network. The roles of this
> machine are the typical ones -- DC, AD, DNS, DHCP. Out of the box, DHCP is
> just giving out IP address and subnet info. What other server options
> should
> I select? I had an issue before on another network -- a W2K network --
> where
> people who VPN into the system can only locate network objects using their
> IPs. Nobody could locate anything using names. I think this was due to not
> having any DNS server data being provided by the DHCP server. What do you
> think? I want to set up this network 100% by the book. So I'd appreciate
> some pointers about the perfect DHCP server setup. Thanks.
>
> Thanks,
>
> Sam
>
>

Phillip,

I really appreciate your response. This is a new W2K3 network and I didn't
setup a WINS server as all clients are WinXP Pro clients. Do I need to set
up a WINS server in this situation?

Thanks,

Sam

"Phillip Windell" <@.> wrote in message
news:%2399Dpj%(E-Mail Removed)...
> "Sam" <(E-Mail Removed)> wrote in message
> news:ujXDFG%(E-Mail Removed)...
> > just giving out IP address and subnet info. What other server options
> should
> > I select? ...............................
> > think? I want to set up this network 100% by the book. So I'd appreciate
> > some pointers about the perfect DHCP server setup. Thanks.
>
> The "keep it simple" method works everytime it is tried. Always stay in
the
> broundaries of what you know understand and can troubleshoot. There's
always
> time to get more complicated later.
>
> You can include all the "basic" network settings. I would include them at
> the Scope level as "Scope Options" instead of at the Server level (Server
> Options) so that you can use different settings in different scopes if the
> need ever arises. You use one scope per subnet so the "Scope Options" are
a
> way to give each subnet its own settings that pertain to it.
>
> In addition to the IP# and mask, there is the Default Gateway ("Router" in
> DHCP), the WINS servers IP# and the DNS IP#s. Here is a list with the
option
> numbers that are your "core" settings:
>
> 003 Router = Your Default Gateway for the client
> 006 DNS Servers = Your AD/DNS Server's IP#
> 015 DNS Domain Name = Your Active Directory Domain Name
> 044 WINS/NBNS Servers = Your WINS Server IP#
> 046 WIN/NBT Node Type = I usually use 0x8, ...the choice is yours.
>
> In creating the scope you should use the entire full address range of that
> particular subnet and then use "Exclusions" to prevent certain addresses
> from being given out by DHCP that you may need to use for static
adddresses
> on certain devices/hosts. You can also use Reservations to simulate the
> same effect as a static address, however this still leaves the host
> dependent on a functioning DHCP which may not always be desireable because
> some things need to run even if the DHCP server goes down.
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>

Thanks Robert. Much appreciated.

Sam

"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message
news:u1lJAk%(E-Mail Removed)...
> this may help. quoted from http://www.ChicagoTech.net
> Unable to browse through PPTP/VPN connection
> Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN
> server, and you attempt to connect to a computer using a PPTP/VPN client,
> you may experience following problem: 1) The NetBIOS name of the computer
to
> which you are attempting to connect is not resolved. 2) You may receive an
> error message similar to the following error message: "System error 53 has
> occurred. The network path was not found" when using net view or opening
> Network Knighthood.
> 2. If the WINS server is not on the same computer as the PPTP server and
you
> attempt to connect to a computer using a PPTP client, you may be able to
> connect to computers on your local area network (LAN), but you may be
unable
> to connect to network shares or resources on the PPTP server.
> Resolutions: Inability to browse often means the client can't resolve
> NetBIOS names.
> 1. If this is a workgroup network, enable NetBIOS over TCP/IP on the
server
> and clients.
> 2. If this is domain network and the WINS server is on the same computer
as
> the PPTP/VPN server, move the WINS server to a different computer.
> 3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in
addition
> to, TCP/IP.
> 4. By default, most routers and firewalls prevent the transmission of
> NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139.
Try
> to enable UDP ports 137 and 138 and TCP port 139 across all routers and
> firewalls between the PPTP/VPN client and PPTP/VPN server.
> 5. Make sure the client has correct DNS, WINS and Master Browser settings.
> 6. Make sure the default gateway points to the remote network rather than
to
> the ISP.
> 7. Some ISP might block ports required for NetBIOS name broadcasts.
> 8. If WINS address is not distributed upon connection to VPN, LMHOSTS
should
> be configured to enable Domain to be located.
> 9. If you try these techniques and the client still can't browse, try to
use
> UNC to connect to the remote resources by ip, for example, use the net use
> h: \\serverip\sharename command.
>
> --
> For more and other information, go to http://www.ChicagoTech.net
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more
help.
>
> Robert Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
> http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
>
> "Sam" <(E-Mail Removed)> wrote in message
> news:ujXDFG%(E-Mail Removed)...
> > Hi,
> >
> > I just set up the first machine of a new W2K3 network. The roles of
this
> > machine are the typical ones -- DC, AD, DNS, DHCP. Out of the box, DHCP
is
> > just giving out IP address and subnet info. What other server options
> > should
> > I select? I had an issue before on another network -- a W2K network --
> > where
> > people who VPN into the system can only locate network objects using
their
> > IPs. Nobody could locate anything using names. I think this was due to
not
> > having any DNS server data being provided by the DHCP server. What do
you
> > think? I want to set up this network 100% by the book. So I'd appreciate
> > some pointers about the perfect DHCP server setup. Thanks.
> >
> > Thanks,
> >
> > Sam
> >
> >
>
>

They need WINS or DNS (usually both) to get good resolution.

See my other post for the rest.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Sam" <(E-Mail Removed)> wrote in message
news:ujXDFG%(E-Mail Removed)...
> Hi,
>
> I just set up the first machine of a new W2K3 network. The roles of this
> machine are the typical ones -- DC, AD, DNS, DHCP. Out of the box, DHCP is
> just giving out IP address and subnet info. What other server options
should
> I select? I had an issue before on another network -- a W2K network --
where
> people who VPN into the system can only locate network objects using their
> IPs. Nobody could locate anything using names. I think this was due to not
> having any DNS server data being provided by the DHCP server. What do you
> think? I want to set up this network 100% by the book. So I'd appreciate
> some pointers about the perfect DHCP server setup. Thanks.
>
> Thanks,
>
> Sam
>
>

"Sam" <(E-Mail Removed)> wrote in message
news:O8Jmss%(E-Mail Removed)...
> I really appreciate your response. This is a new W2K3 network and I didn't
> setup a WINS server as all clients are WinXP Pro clients. Do I need to set
> up a WINS server in this situation?

The newer OS's dont' need, but some Applications still do. You can wait and
go without it, but if some Apps start having trouble then you may have to
add a WINS server. Outlook with Exchange is one such example.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com