Re: Problem with Siemens IP Telephony and DHCP Vendor Option 43


"Robert Riegler" <RobertRiegler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D22C355E-C301-47CD-B10F-28EEE0540A17@xxxxxxxxxxxxxxxx
The article you told me, tells about to use option 60,..
Thats no good because if you set these RIS isn´t any more supported by
microsoft (wont work) , there is a KB article to this:
http://support.microsoft.com/kb/259670/en-us

So its of no use, because we need RIS installation server in our
environment

If you put your phones in their own subnet, WITHOUT any computers in that
subnet, you do not need RIS in that subnet any more...

However, I wasn't suggesting you use options 60. Options 60 is what the
other poster was using. The same theory applies to both problems, however.

Thanks,
Oliver


"Oliver O'Boyle" wrote:

I just finished working through a similar problem with a poster below.
you
should read through that thread first, just in case something pops up
that
useful to you.

Re: dhcp vendor classes option

Also, pay special attention to the suggestion of keeping the phones in a
separate VLAN, which would solve your problem automatically. It's a best
practice, and is more managemable and secure than keeping the phones in
the
same subnet as your workstations.

Oliver

"Robert Riegler" <RobertRiegler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:268BEEA1-6E93-4285-8BE9-0BA30AABEF74@xxxxxxxxxxxxxxxx
There is following problem:

We have a new Siemens VOIP telephony system.
Therefore we need to include following vendorspecific DHCP option (43)
in
our normal dhcp scope, to move the telephony clients to a seperate
telephony
scope.
01 0A 53 69 65 6D 65 6E 73 00 00 00 02 04 00 00 00 03 00 00 00 00
00
FF
option 43 set in DHCP User Class

There are now 2 large problems:
1) like in request
http://groups.google.at/group/microsoft.public.windows.server.networking/browse_thread/thread/9a032e7924033590/880d207abb52711b?lnk=st&q=DHCP+vendor+option+43+XP+clients+do+not&rnum=5&hl=en#880d207abb52711b
is there a solution to above problem (IP release)? What can be done

2) we also have PXE (INTEL) clients on this scope and we have seperate
RIS
and DHCP servers. PXE Booting isnt working now on all Intel Network
cards,
after the option 43 has been set to Siemens.
Is there a way to provide more than one Vendor specified option via
DHCP
Option 43. Please give us an example.







.

Relevant Pages

  • Re: DHCP on two different subnets with a Virtual additional IP
    ... 1- Added an additional ip address on my dc (in the tcp/ip protocol properties) ... 2- added a dhcp scope on the x.x.10.0 subnet ... subnet everything functions...May be it's not possible for my dhcp server to ...
    (microsoft.public.windows.server.active_directory)
  • Re: DHCP on Primary IPs subnet only?
    ... "Try assigning the DHCP server's NIC a second static IP address from ... It should see the requests comming in from ... w.x.y.0/24 scope so it would not be confused. ... >> its primary IP is on that subnet. ...
    (microsoft.public.win2000.networking)
  • Re: 3 New Sites / New Company
    ... DHCP scopes to use per site. ... the question was do I need to only use the scope (subnet) for that site I ... DHCP Server and it has a correct Scope to "answer" the Query with. ...
    (microsoft.public.windows.server.active_directory)
  • Re: RIS cant resolve IP address
    ... Tap the enter key every second once the first dot after DHCP appears. ... then eventually it should get one with the RIS disk. ... It works fine when I am on the same subnet as the DHCP and RIS ... may cause the client to not be able to reach the RIS server when the RIS ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Running out of IP addresses
    ... Create a new scope embracing the full subnet 1 thru 254 and assign the ... Range of a Scope,...you just can't change the mask (like making the subnet ... I understand that I will need to introduce a DHCP server on the ... Rather than introduce a hardware LAN router, ...
    (microsoft.public.windows.server.networking)