|
Home > Archive > 70-216 > March 2003 > DHCP Classes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| me? I dunno... 2003-03-22, 1:30 pm |
| This From Knowledge base article 240247 regarding the assigning of custom dhcp user classes.
"In the New Class dialog box, type a descriptive identifying name for the new option in the Display name box. You may also add additional information to the Description box.
Type in the data to be used by the DHCP Server service for matching the class ID provided by DHCP clients under ID or ASCII. To enter the data as hexadecimal byte numeric values, click the left side of the text box. To enter data as American Standard Code for Information Interchange (ASCII) text character values, click the right side of the text box."
How do I determine what number to assign, and what does this number relate to in active directory? | |
| jeff_j_black 2003-03-22, 6:24 pm |
| I think you can just make the class id up as long as you have clients assigned the same value class, they will get those properties of that class. | |
| cm2gj 2003-03-22, 10:20 pm |
| quote:
Originally posted by me? I dunno...
This From Knowledge base article 240247 regarding the assigning of custom dhcp user classes.
"In the New Class dialog box, type a descriptive identifying name for the new option in the Display name box. You may also add additional information to the Description box.
Type in the data to be used by the DHCP Server service for matching the class ID provided by DHCP clients under ID or ASCII. To enter the data as hexadecimal byte numeric values, click the left side of the text box. To enter data as American Standard Code for Information Interchange (ASCII) text character values, click the right side of the text box."
How do I determine what number to assign, and what does this number relate to in active directory?
this don`t have any relation with the AD. I use class on my work enviroment in the past. Is a simple implementation, and very usefull.
For example: the Standard class assign the gateway 192.168.0.1 and dns 192.168.0.2 to certain users. The custom made class "DSL" i add, put different parameters on the TCP IP configuration on this clients: gateway 192.168.0.4 and dns 192.168.0.3. on this same subnet i had 2 differents companies who use different gateways and servers. | |
| me? I dunno... 2003-03-23, 12:52 am |
| progress every day, I think I should be ready in another month or so.
any other suggestions for must_do practice labs? | |
| jeff_j_black 2003-03-23, 10:19 am |
| So you've done DNS, NAT, RAS, VPN, DHCP. Anything with IPSec or Certificates? | |
|
| quote:
Originally posted by me? I dunno...
progress every day, I think I should be ready in another month or so.
any other suggestions for must_do practice labs?
labs for 216? mmmm....
dhcp... classes ... dns, srv, ad integrated, wins, wins/dns integration... dhcp lease times testing, rras, vpn, l2tp, pptp, etc, dhcp 80/20 70/30 rules on scopes , reverse lookup zone creation on dns, ptr creation, dinamic update checking with clients on the dns, etc | |
| me? I dunno... 2003-03-23, 4:56 pm |
| Today's problem is multiple address' being handed out to clients, including static configurations.
I have one static assigned member server that was handed out 1 address at 2:09:18PM
followed by seven more adress' handed out between 2:09:23PM and 2:09:34PM
the scope range is 192.168.1.10-192.168.1.50, and the static ip is 192.168.1.4
I will look at dhcp server bootp, and nat server dhcp relay configurations first.
My isp is providing dhcp from the same server as dns for the outside nic, but I boot the nat server with that card disabled, then disable the internal card, enable the outside card, then once the outside nic has been set, I reenable the lan card.
The multiple address' are not restricted to the nat server, they also include a member server and xp client. The member server had a radius server installed and then removed from it earlier on in the process. | |
|
| quote:
Originally posted by me? I dunno...
Today's problem is multiple address' being handed out to clients, including static configurations.
I have one static assigned member server that was handed out 1 address at 2:09:18PM
followed by seven more adress' handed out between 2:09:23PM and 2:09:34PM
the scope range is 192.168.1.10-192.168.1.50, and the static ip is 192.168.1.4
I will look at dhcp server bootp, and nat server dhcp relay configurations first.
My isp is providing dhcp from the same server as dns for the outside nic, but I boot the nat server with that card disabled, then disable the internal card, enable the outside card, then once the outside nic has been set, I reenable the lan card.
The multiple address' are not restricted to the nat server, they also include a member server and xp client. The member server had a radius server installed and then removed from it earlier on in the process.
why you need to disable the NICs on the restart? | |
| jeff_j_black 2003-03-23, 10:12 pm |
| Can you sort this out a bit, I'm not quite getting the specifics, are you saying that clients with fixed IP are getting DHCP addresses up to several times an hour? | |
| me? I dunno... 2003-03-23, 11:24 pm |
| d'oh! my mistake, I think booting every machine on the lan at the same time does this. It has been happening quite often, as I get up in the morning and head straight for the network, I see now my boot order requires more care. I just restarted dhcp, and then rebooted dc and no change in assignment information, it must have got that during startup, I'll see for sure tomorrow.
re; the nic cards, I get dynamic assignment from cable isp, 1 static address costs around $160.00 per month. Cable is the only high speed option where I live.
ISP has dhcp on same server as dns, so I cannot circumvent that particular box. If I configure static ip, even using the same information that it picks up during dynamic assignment, it will not connect. I can change over to static configuration after connecting but it doesnt seem to be neccessary.
If I do not disable internal nic, I think the outside card tries to get dhcp from lan instead of ISP, I have tried repeatedly and must have internal card disabled and external assigning dynamic for this to work. btw, this is my NAT and RRAS box, and once connected, everything seems to work fine. | |
|
| quote:
Originally posted by me? I dunno...
d'oh! my mistake, I think booting every machine on the lan at the same time does this. It has been happening quite often, as I get up in the morning and head straight for the network, I see now my boot order requires more care. I just restarted dhcp, and then rebooted dc and no change in assignment information, it must have got that during startup, I'll see for sure tomorrow.
re; the nic cards, I get dynamic assignment from cable isp, 1 static address costs around $160.00 per month. Cable is the only high speed option where I live.
ISP has dhcp on same server as dns, so I cannot circumvent that particular box. If I configure static ip, even using the same information that it picks up during dynamic assignment, it will not connect. I can change over to static configuration after connecting but it doesnt seem to be neccessary.
If I do not disable internal nic, I think the outside card tries to get dhcp from lan instead of ISP, I have tried repeatedly and must have internal card disabled and external assigning dynamic for this to work. btw, this is my NAT and RRAS box, and once connected, everything seems to work fine.
you have something missconfigured on your enviroment. The internal hosts don`t reach the ISP dhcp service.
The Cable NIC must be isolated from the internal network. Regarding the DHCP behavior, is normal if the server have too bad hardware resources. DHCP service can provide service to a lot of clients but you must optimize TCP IP traffic. Maybe a monitor of your network reflect too much Netbios traffic or some TCP inconsistence. Your cabling need to be checking too, to see if you are adding delays onto the network due to bad cabling termination. this is critical to DHCP funcionality. Remember DHCp client use UDP 67 and 68 to reach DHCP server and a TTL is applied, if the Server is not reached on the specific time, an APIPA or DHCP problem appear.
You can activate the extended log on the DHCP and specify the folder to see the behavior of the DHCP.
good luck. | |
| me? I dunno... 2003-03-24, 1:45 am |
| I have NetBios disabled, udp traffic on those ports is also allowed.
I will see tomorrow when I boot the dc/dhcp/dns server first and allow it to come up fully before initializing any other machines. | |
| cm2gj 2003-03-24, 10:01 am |
| quote:
Originally posted by me? I dunno...
I have NetBios disabled, udp traffic on those ports is also allowed.
I will see tomorrow when I boot the dc/dhcp/dns server first and allow it to come up fully before initializing any other machines.
enable the audit login on the DHCP!!! | |
| me? I dunno... 2003-03-24, 12:35 pm |
| quote:
enable the audit login on the DHCP!!!
ah yes... the old rogue server thing
I guess I'll have to be very particular about shutdown and startup routine from now on, thanks.
One other thing... my dial up connection gets a static ip with a 255.255.255.255 subnet mask and ipconfig will not supply any information about gateway or dns, why is this? | |
| jeff_j_black 2003-03-24, 1:52 pm |
| Do you have a DHCP relay configured? This is needed to correct this. Sometimes you need to lengthen the threshold on this service as well. | |
| me? I dunno... 2003-03-24, 2:30 pm |
| quote:
One other thing... my dial up connection gets a static ip with a 255.255.255.255 subnet mask and ipconfig will not supply any information about gateway or dns, why is this?
Actually, I misspoke here. The above numbers are from the remote computer that I use to vpn to the lan, the configuration comes from the isp I dial up to.
I had the relay agent configured on the nat/rras server but disabled it as part of attempt to eliminate multiple address assignments. Now that I look to reconfigure it I am wondering... I think it should point to the lan dhcp to service the vpn client, but how would that affect the external nic when it initializes and goes looking for an address, I'll try it both ways and see.
Also, just got three new textbooks in the mail, 221, 222, and ISA server and beyond... think I'll tackle 221 first as a compliment to, and review of the 216 material. | |
| me? I dunno... 2003-03-24, 4:01 pm |
| I cant believe it took me that long to realize therer was a scroll bar at the bottom of the dchp console...
Oh well, better late than never... btw problem solved. | |
|
| quote:
Originally posted by me? I dunno...
I cant believe it took me that long to realize therer was a scroll bar at the bottom of the dchp console...
Oh well, better late than never... btw problem solved.
so... the problem resolution was: ?? | |
| me? I dunno... 2003-03-25, 12:47 am |
| One problem was that a member server I had initially configured for Radius server still had RRAS functioning, I disabled it and that problem went away. Upon further investigation, the problem still exists on the RRAS/NAT server I am using. I have increased the boot threshold on the lan side nic to 15 seconds but that still hasnt had any effect.
The RAS server will accept remote connections, and the address at the client is shown as one in the scope range configured on the dhcp server but the subnet mask is shown as 255.255.255.255 and ipconfig at the client shows that dhcp is not enabled.
I can see the remote connection in the status window of the remote access clients area and it is also showing an appropriate ip address in the network registration box, but there is no indication on the dhcp server of any connection matching the remote access assigned address.
I can browse the lan from remote connection but I'm thinking something is still not right because of the odd subnet mask, the lease not showing on the dhcp server, and the multiple address' still being picked up on boot by the ras server.
Ipconfig on RRAS/NAT server shows
ppp adapter RAS server (dial in) interface:
dhcp enabled :no
ip address :192.168.1.21
The static ip for the lan side nic is 192.168.1.9
neither the ras server dial in interface 192.168.1.21 or the remoted client vpn 192.168.1.18 are shown on the dhcp server.
So I guess the was justified after all. | |
| jeff_j_black 2003-03-25, 8:33 am |
| RRAS checks out addresses from DHCP for a number of each port type that it is configured to respond to.
Make sure all of your servers are using fixed addresses, including RRAS.
Another issue you need to examine is to make sure you are not trying to bridge accross RRAS. The public interface should route to the private interface, such that your remote clients aren't on the same subnet as the private interface. |
|
|
|
|