Networking Forums

Networking Forums > Computer Networking > Windows Networking > Adding a DHCP Scope to Windows 2003 Server

Reply
Thread Tools Display Modes

Adding a DHCP Scope to Windows 2003 Server

 
 
Dave
Guest
Posts: n/a

 
      11-27-2006, 07:07 PM
We just had to install some AdTran NetVanta's to our network to bridge to a
remote location.

Once I did the install of the AdTran equipment, they told me I needed to add
another ip scope to our DHCP server. The DHCP is running off the Windows 2003
server.

The current range is 192.168.1.0. I need to add 192.168.2.0 for the remote
side. The AdTran tech support tells me it cannot have the same range as the
host side because the NetVanta would not know where to send the packets.

Can someone help me set up a second scope for DHCP on the server?
 
Reply With Quote
 
 
 
 
James McIllece [MS]
Guest
Posts: n/a

 
      11-27-2006, 09:23 PM
Hi there --

To set up a second scope, all you do is open the DHCP console, then right-
click the DHCP server and click New Scope.

The New Scope wizard launches, and you should configure it with these
values:

IP address range: 192.168.2.1 through 192.168.2.254
Exclusion range: 192.168.2.1 through 192.168.2.10

The exclusion range means that the DHCP server will not lease these
addresses to clients, which frees them up in case you need to
statically/manually configure something with an IP address. For example,
the AdTran equipment has a static IP address (I am just guessing that they
used the IP 192.168.2.1, but you should check on and verify this, as you
will be typing this address into the New Scope wizard as the Default
Gateway setting).

Also while running the wizard you should type in the IP addresses of your
DNS and WINS servers -- so find these out before you run the wizard. Also
type in your domain name when the wizard prompts you, such as (for example)
"microsoft.com" (without the quotation marks).

For the Default Gateway setting, use the AdTran's IP (as mentioned above)
that leads to the rest of the network so that clients on the new subnet can
communicate with the old subnet.




=?Utf-8?B?RGF2ZQ==?= <(E-Mail Removed)> wrote in
news:8E24FF02-DFDF-4DF4-A7B6-(E-Mail Removed):

> We just had to install some AdTran NetVanta's to our network to bridge
> to a remote location.
>
> Once I did the install of the AdTran equipment, they told me I needed
> to add another ip scope to our DHCP server. The DHCP is running off
> the Windows 2003 server.
>
> The current range is 192.168.1.0. I need to add 192.168.2.0 for the
> remote side. The AdTran tech support tells me it cannot have the same
> range as the host side because the NetVanta would not know where to
> send the packets.
>
> Can someone help me set up a second scope for DHCP on the server?
>




--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Reply With Quote
 
Dave
Guest
Posts: n/a

 
      11-28-2006, 01:24 PM
Thank you James. I did what you said and the DHCP appears to be working
correctly - with one hitch. I can see the two AdTrans, I can see the gateway,
I can see the server on the 192.168.1.0 network and I can get on the
internet...but I cannot see any of the computers/printers on the 192.168.1.0
network.

Do you think this is an issue with routing through the AdTran or did I
possibly do something wrong when I set up the new scope?

"James McIllece [MS]" wrote:

> Hi there --
>
> To set up a second scope, all you do is open the DHCP console, then right-
> click the DHCP server and click New Scope.
>
> The New Scope wizard launches, and you should configure it with these
> values:
>
> IP address range: 192.168.2.1 through 192.168.2.254
> Exclusion range: 192.168.2.1 through 192.168.2.10
>
> The exclusion range means that the DHCP server will not lease these
> addresses to clients, which frees them up in case you need to
> statically/manually configure something with an IP address. For example,
> the AdTran equipment has a static IP address (I am just guessing that they
> used the IP 192.168.2.1, but you should check on and verify this, as you
> will be typing this address into the New Scope wizard as the Default
> Gateway setting).
>
> Also while running the wizard you should type in the IP addresses of your
> DNS and WINS servers -- so find these out before you run the wizard. Also
> type in your domain name when the wizard prompts you, such as (for example)
> "microsoft.com" (without the quotation marks).
>
> For the Default Gateway setting, use the AdTran's IP (as mentioned above)
> that leads to the rest of the network so that clients on the new subnet can
> communicate with the old subnet.
>
>
>
>
> =?Utf-8?B?RGF2ZQ==?= <(E-Mail Removed)> wrote in
> news:8E24FF02-DFDF-4DF4-A7B6-(E-Mail Removed):
>
> > We just had to install some AdTran NetVanta's to our network to bridge
> > to a remote location.
> >
> > Once I did the install of the AdTran equipment, they told me I needed
> > to add another ip scope to our DHCP server. The DHCP is running off
> > the Windows 2003 server.
> >
> > The current range is 192.168.1.0. I need to add 192.168.2.0 for the
> > remote side. The AdTran tech support tells me it cannot have the same
> > range as the host side because the NetVanta would not know where to
> > send the packets.
> >
> > Can someone help me set up a second scope for DHCP on the server?
> >

>
>
>
> --
> James McIllece, Microsoft
>
> Please do not send email directly to this alias. This is my online account
> name for newsgroup participation only.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>

 
Reply With Quote
 
James McIllece [MS]
Guest
Posts: n/a

 
      11-28-2006, 10:46 PM
Hi there --

Because the clients on the new subnet are receiving IP address leases from
the DHCP server, the problem does not lie with DHCP -- you set that up
successfully, which is good.

I'm not sure what the problem might be -- perhaps the firewall software on
one or both client computers is blocking connectivity, you might make sure
file sharing is enabled on the firewall.

Perhaps somebody else has more expertise in this area and can lend a hand.
:-)


=?Utf-8?B?RGF2ZQ==?= <(E-Mail Removed)> wrote in
news:F371D396-4D04-473B-9AC9-(E-Mail Removed):

> Thank you James. I did what you said and the DHCP appears to be
> working correctly - with one hitch. I can see the two AdTrans, I can
> see the gateway, I can see the server on the 192.168.1.0 network and I
> can get on the internet...but I cannot see any of the
> computers/printers on the 192.168.1.0 network.
>
> Do you think this is an issue with routing through the AdTran or did I
> possibly do something wrong when I set up the new scope?
>
> "James McIllece [MS]" wrote:
>
>> Hi there --
>>
>> To set up a second scope, all you do is open the DHCP console, then
>> right- click the DHCP server and click New Scope.
>>
>> The New Scope wizard launches, and you should configure it with these
>> values:
>>
>> IP address range: 192.168.2.1 through 192.168.2.254
>> Exclusion range: 192.168.2.1 through 192.168.2.10
>>
>> The exclusion range means that the DHCP server will not lease these
>> addresses to clients, which frees them up in case you need to
>> statically/manually configure something with an IP address. For
>> example, the AdTran equipment has a static IP address (I am just
>> guessing that they used the IP 192.168.2.1, but you should check on
>> and verify this, as you will be typing this address into the New
>> Scope wizard as the Default Gateway setting).
>>
>> Also while running the wizard you should type in the IP addresses of
>> your DNS and WINS servers -- so find these out before you run the
>> wizard. Also type in your domain name when the wizard prompts you,
>> such as (for example) "microsoft.com" (without the quotation marks).
>>
>> For the Default Gateway setting, use the AdTran's IP (as mentioned
>> above) that leads to the rest of the network so that clients on the
>> new subnet can communicate with the old subnet.
>>
>>
>>
>>
>> =?Utf-8?B?RGF2ZQ==?= <(E-Mail Removed)> wrote in
>> news:8E24FF02-DFDF-4DF4-A7B6-(E-Mail Removed):
>>
>> > We just had to install some AdTran NetVanta's to our network to
>> > bridge to a remote location.
>> >
>> > Once I did the install of the AdTran equipment, they told me I
>> > needed to add another ip scope to our DHCP server. The DHCP is
>> > running off the Windows 2003 server.
>> >
>> > The current range is 192.168.1.0. I need to add 192.168.2.0 for the
>> > remote side. The AdTran tech support tells me it cannot have the
>> > same range as the host side because the NetVanta would not know
>> > where to send the packets.
>> >
>> > Can someone help me set up a second scope for DHCP on the server?
>> >

>>
>>
>>
>> --
>> James McIllece, Microsoft
>>
>> Please do not send email directly to this alias. This is my online
>> account name for newsgroup participation only.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>

>




--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Adding Windows XP Client to Windows Server 2003 Domain Varga Windows Networking 1 09-08-2006 11:20 AM
Adding Windows XP Client to Windows Server 2003 Domain Varga Windows Networking 1 09-07-2006 10:49 PM
Adding DHCP Scope Option 81 Ben Windows Networking 8 06-23-2006 10:41 PM
Adding a DNS suffix to my DHCP Scope =?Utf-8?B?c3BlcGk=?= Windows Networking 4 04-19-2005 08:43 PM
Adding a Windows 2003 Server to NT4 Domain Barry Plewa Windows Networking 1 12-05-2003 07:16 AM



1 2 3 4 5 6 7 8 9 10 11