WRE54G - DHCP Soundbridge not working

I am sure everyone has has had issues getting a WRE54G up and runing at home - not the easiest of products (when using the encryption option).
I have an Organce LiveBox ADSL/Wireless router (Sagem badged Orange) and needed the range extended to get my Soundbridge (Pinnacle badged Roku) working elsewhere in the house.
A couple of problems:
- DHCP does not work via the WRE54G. Solved this by setting a static IP address on the Soundbridge (you telnet to it on port 4444 and use the ipset command line utility)
- The Soundbridge can access Internet radio stations fine, but if connected via the WRE54G then it loses contact with the Firefly media server
- WindowsXP PnP "sees" the Soundbridge the "other side" of the the WRE54G but cannot access it when you double click on the icon. Not an issue as just using the static IP address in the browser gets the configuration screen
I guess that I had expected the WRE53G to act more like a repeater, but is appears to be working as a bridge and the bridging function is somewhat broken.
Anyone have any ideas / fixes for the product? This is highly infuriating.

Try a different wall plug and see if that makes any difference, try a different power cable of the same power specification or a universal power adapter(if possible)...Maybe the Power Adapter is faulty and the unit is still functional...

Similar Messages

DHCP *still* not working.

i posted some of the problems i was having in this post here :
http://discussions.apple.com/thread.jspa?messageID=5706025
after reinstalling 10.5 Server about half a dozen times... DHCP randomly started working just fine and has been working pretty well in the past month or so.
then i got some new computers recently.
none of them get a DHCP address. not a single one. they all get self-assigned numbers.
and the log is once again filled with the familiar :
Feb 11 12:52:33 dropbox bootpd[312]: DHCP DISCOVER [en0]: 1,0:1e:c2:b7:d9:e3 <Air23>
Feb 11 12:52:33 dropbox bootpd[312]: service time 0.000963 seconds
Feb 11 12:52:34 dropbox bootpd[312]: DHCP REQUEST [en1]: 1,0:1e:c2:b7:d9:e3 <Air23>
Feb 11 12:52:34 dropbox bootpd[312]: service time 0.002062 seconds
Feb 11 12:52:34 dropbox bootpd[312]: DHCP REQUEST [en0]: 1,0:1e:c2:b7:d9:e3 <Air23>
Feb 11 12:52:34 dropbox bootpd[312]: service time 0.001575 seconds
Feb 11 12:52:35 dropbox bootpd[312]: DHCP REQUEST [en1]: 1,0:1e:c2:b7:d9:e3 <Air23>
Feb 11 12:52:35 dropbox bootpd[312]: service time 0.001488 seconds
repeat non-stop and for every single new machine i got.
anyone have any ideas?
i tried recreating the subnet from scratch again... no change.
i tried adding the <replythresholdseconds> to 0 again... no change.
where or how is the server keeping track of the "old" machines being viable and able to get an IP vs. the "new" machines which refuse to work at all? there has to be something somewhere where it is keeping track of this.
i also tried converting an old machine that never was on DHCP to DHCP ... it also was unable to get an address.
manually-assigned out-of-range DHCP addresses seem to work fine on the new machines however. my DHCP goes from 192.168.3.2 -.127 ... and addresses manually entered at .200+ all give the machines a network connection. this is a temporary solution however.
any ideas?
thanks.
zeb.

at this point in time... yes. hundreds of times. just near the bottom of the .plist.
tried it in the upper section where the subnet info is as well... made no difference.
let me copy/paste my .plist in here...
<dict>
<key>NetBoot</key>
<dict/>
<key>Subnets</key>
<array>
<dict>
<key>allocate</key>
<true/>
<key>dhcpdomainname</key>
<string>arcus.org</string>
<key>dhcpdomain_nameserver</key>
<array>
<string>209.165.164.3</string>
<string>209.165.164.13</string>
</array>
<key>dhcpnb_over_tcpip_nodetype</key>
<string>1</string>
<key>dhcp_router</key>
<string>192.168.3.1</string>
<key>lease_max</key>
<integer>10800</integer>
<key>lease_min</key>
<integer>10800</integer>
<key>leasetimesecs</key>
<string>3600</string>
<key>name</key>
<string>192.168.3</string>
<key>net_address</key>
<string>192.168.3.0</string>
<key>net_mask</key>
<string>255.255.255.128</string>
<key>net_range</key>
<array>
<string>192.168.3.2</string>
<string>192.168.3.127</string>
</array>
<key>selectedportname</key>
<string>en1</string>
<key>uuid</key>
<string>A604DFA1-6F33-4B7D-8081-1197E1D51D44</string>
</dict>
</array>
<key>dhcp_enabled</key>
<true/>
<key>replythresholdseconds</key>
<integer>0</integer>
<key>timeDatabaseUpdated</key>
<string>2006-04-25 07:20:31 -0800</string>
<key>timeServiceStarted</key>
<string>2008-02-13 16:24:40 -0900</string>
</dict>
i clipped out the header and <plist> tags... they are still there in the real file.
thanks.

IP invalid - DHCP option not working - Moden Motorola SB5120

Hi Apple friends,
My Airport is not being able to get the ip number from my Motorola modem SB5120, I know that the ip should be provided by my modem (DHCP server), but for any reason it is not working. The airport works without any problem if I connect it to my I-LINK router. Does anyone could help me with some information that could help me to solve this issue?

Williamfs wrote:
I turned the modem off for over than 6 hours and then tried to connect again, but the airport is still not being able to get an ip from the modem, should I call the ISP? Would you have any other information that could help me?
I'd verify that your AirPort unit is configured correctly. Launch AirPort Utility, double-click on the icon of your unit on the left to enter "Manual Configuration" mode, the select the "Internet" panel and the "Internet Connection" tab. You should see settings for "Connect Using" of "Ethernet" and for "Configure IPv4" of "Using "DHCP".
If that's all set correctly, then the next step should be to call your ISP. The question you need to ask them is whether they record the "MAC address" of your equipment and whether they need to change their settings if you replace the equipment directly connected to your modem. If so, the value they will need from you will be labeled "Ethernet ID" and will be on the outside (perhaps on the bottom) of your AirPort unit.

DHCP NAP not working as it should

Hello,
I'm trying to get NAT DHCP to work in a test enviroment. Everything appears to be ok, but it's not.
The health policy is checking if Windows Firewall is turned on. The Remediatio Group consist of only one server.
When I turn off the firewall on my test machine, I can see 2 entries in the event viewer on my NPS server:
1) 6272 - Network Policy Server granted access to a user.
2) 6278 - Network Policy Server quarantined a user.
Authentication Details:
Connection Request Policy Name: NAP DHCP
Network Policy Name:  NAP DHCP Noncompliant
Authentication Provider:  Windows
Authentication Server:  WAWRADIUS01.contoso.com
Authentication Type:  Unauthenticated
EAP Type:   -
Account Session Identifier:  3633373838343133
Despite the client being quarantined, it stil has full access to the network.
One thing to note is that the DHCP server is not on the NPS server, although the DHCP server seems to be properly configured to forward the requests to the NPS server. And The NPS and DHCP servers are both on the same subnet.
Please advise where should I look for the source of the problem.
Kind regards,
Wojciech

Hi Wojciech,
Event ID 6272: Network Policy Server granted access to a user. This event occurs when a NAP client computer is successfully authenticated and, depending on its health state, obtains full or restricted access to the network.
Event ID 6278: Network Policy Server granted full access to a user because the host met the defined health policy. This event occurs when the client access request matches a network policy that is configured with a NAP enforcement setting
of Allow full network access.
Based on my understanding, this two events above shows that the NAP client was granted full access because it meet a certain policy indeed. Please double check what policy is being matched.
Event ID 6276: Network Policy Server quarantined a user. This event occurs when the client access request matches a network policy that is configured with a NAP enforcement setting of
Allow limited access. It can also occur if you have configured a setting of
Allow full network access for a limited time and specified date is in the past.
If it is event 6276, you need to check either the NAP client configuration or the health policies.
Check if you have configured the settings which is similar with Allow full network access for a limited time.
Review the health policy you have created for the NAP client. Configure the client according to the restrictions of the health policy.
Also, please refer to the checklist below to check if the policies and other settings were configured properly.
Event ID 6276 — NAP Client Health Status
http://technet.microsoft.com/en-us/library/dd316174(v=WS.10).aspx
Checklist: Configure NAP Enforcement for DHCP
http://technet.microsoft.com/en-us/library/cc772356(v=WS.10).aspx
Best Regards,
Tina

DHCP failover not working

I am attempting to implement DHCP failover using load balancing with an Essentials and a Standard server. I have everything configured and working but I am facing an issue.
If I try to start the DHCP services on the Essentials server and the DHCP services on the Standard server are already started it will not start and I get error 1053 The DHCP/BINL service has encountered another server on this network with IP Address, 192.168.1.3,
belonging to the domain: . in the event log on the Essentials serve.
Any ideas why this is?

In a network of this size there is little need for multiple or failover DHCP servers. With a lease time in the one week category the chances that the server will be off line at the same time that clients need to renew are pretty slim. Should
the server simply be unavailable you can turn the DHCP on the router, or, as you intend, on the second server.
Larry Struckmeyer[SBS-MVP]
Larry, I am not sure I find this to be the case -- that rarely will the server be off at the same time clients need to renew. I volunteer support to a local non profit. Sadly, it's not uncommon for the Essentials server to not come up cleanly
after a Microsoft Update or a power outage. With DHCP not available on the WSE2012 server, employees who come in and fire up their laptops will in some cases hit the lease expiration. I'll get a phone call, and now there will be two frustrated
people. :-)
I *could* return to letting the router handle DHCP, but I've read too many times on technet and social forums the rather forceful recommendations by microsoft people that an Essentials served network should have DHCP running on the server.
I feel I'm stuck between a rock and a hard place. The strong recommendation from microsoft is to always serve BOTH DHCP and DNS from a WSE server. However, there appears to be no DHCP failover option for WSE, which will make my users unhappy
(and strain my volunteerism!).
Thoughts?
I've tried to research whether WSE will allow a router to act as a failover in hot standby mode, but haven't succeeded. (I'll then need to find a router that supports hot standby in a WSE environment.)
(I realize I am quite late to this thread. Hopefully that's not a problem.)
Steve

DHCP client not working on WLAN after boot [Win XP]

Hi.
I've got a problem with a Lenovo T61 with Windows XP SP2.
I've browsed the forums, and I haven't seen anyone else with a similar problem.
The WLAN works on this computer, but I have to turn it off and on before it works.
If I boot the computer with no ethernet cable connected, log in and wait for Windows to connect to a WLAN, I get limited or no connectivity.
The computer is able to connect to the WLAN I have chosen, but when it is supposed to recieve an IP adress from the DHCP Server it doesn't.
I either have to right click the wireless icon at the lower right of the screen and press repair, or I have to turn off and on the wireless radio with the switch on the laptop.
When I do this it works as normal.
If I use Access connections to set up a wireless connection, specify an SSID, encryption and choose to get IP from DHCP it works. I recieve an IP adress without turning the WLAN radio off and on.
The person using this computer is travelling a lot, and he is not very good with computers, so he doesn't want to use Access Connections to manually make a profile for each WLAN he uses.
How can I fix this and use windows to mange WLAN connections without having to using "repair" or turning the WLAN radio off and on?
Thanks in advance.

There is another thread on this problem about not recovering TCPIP addresses on this forum. the thread recommends installing an update. http://forums.lenovo.com/lnv/board/message?board.id=T_Series_Thinkpads&thread.id=1620
Does the laptop have SP3 installed. I found this to be very helpful on my T23.
ThinkPad T23, 2647 HU8, Based on 2647-8RU: PIII-M 1.20GHz (512KB), 512MB RAM, 40.0GB HDD, 14.1 XGA(1024x768) TFT LCD, 8x8x24x/8x CDRW/DVD, Modem(MPCI), Ethernet(CDC), WinXP Home, Linksys Wireless B adapter.

DHCP does not work while connected to TC throuh ethernet

I currently have a WRT54G router and a time Capsule. The WRT is connected to a cable modem, and the Time Capsule is connected to the router through a LAN port. The WRT assigns addresses in the range of 192.168.15.90 to .99 and the TC assigns addresses between 192.168.15.100 to .109. Connecting to the TC's wireless network works, but connecting to the TC or the router through an ethernet cable does not give an address. I have tried doing DHCP just on the router, just on the TC, and on both, and nothing seems to work, except a wireless connection. Is there a way to fix this?

Have you set up Connection Sharing to "Bridge Mode"?

Wrt54g v7 DHCP does not work on *some* winXP machines with WEP key enabled

HI,
I enabled WEP encryption in an existing network yesterday.
Out of the 10 machines on the network, all WinXP & 1 Kubuntu, 3 XP machines can not get an IP address from the DHCP server. They can happily connect with a fixed IP adresss. All machines are of different makes, 2 of them with XPSP3, different wireless hardware cards.
The firmware is 7.001, i read about 7.004 and even 7.2 on other sites than this one. (but can only find 7.2 as a download)
I am in Juba, Sudan, so cant really go to the shop and buy a new one when I upload the wrong firmware.
Does anyone have a clue what I can do, except removing the 'security' from the router that is connected to a 500USD/Month satelite link we dont want to share with the neighbours?
Rgds,
Reinier
Message Edited by reinier on 01-14-2009 10:07 AM

Click Download and save the latest firmware available for WRT54GS ver 7.0 router...Follow these steps to upgrade the firmware on the device: -
Open an Internet Explorer browser page.In the address bar type - 192.168.1.1
Leave the username blank & in password use admin in lower case...
Click on the 'Administration' tab- Then click on the 'Firmware Upgrade' sub tab- Here click on 'Browse' and browse the .bin firmware file and click on "Upgrade"...Wait for few seconds until it shows that "Upgrade is successful" After the firmware upgrade, click on "Reboot" and you will be returned back to the same page...

DHCP suddenly not working

Eh..here's what I see in the logs:
Sep 6 06:24:38 hostname bootpd[17484]: DHCP DISCOVER [en0]: 1,0:16:ec:7a:52:3c <box2>
Sep 6 06:24:38 hostname bootpd[17484]: service time 0.000637 seconds
But no machines get an IP. Any thoughts? Besides a reboot that is

Here's what I get:
---------------- Client Request --------------------
op = BOOTREQUEST
htype = 1
flags = 8000
hlen = 6
hops = 0
xid = 1931990450
secs = 6656
ciaddr = 0.0.0.0
yiaddr = 0.0.0.0
siaddr = 0.0.0.0
giaddr = 0.0.0.0
chaddr = 0:1c:42:c1:3d:5b
sname =
file =
options:
Options count is 9
dhcpmessagetype (uint8): DISCOVER 0x1
auto_configure (uint8): 0x1
client_identifier (uint8_mult): {0x1, 0x0, 0x1c, 0x42, 0xc1, 0x3d, 0x5b}
requestedipaddress (ip): 169.254.78.66
host_name (string): homeboxvirt
vendorclassidentifier (string): MSFT 5.0
parameterrequestlist (uint8_mult): {0x1, 0xf, 0x3, 0x6, 0x2c, 0x2e, 0x2f, 0x1f, 0x21, 0xf9, 0x2b}
vendor_specific (opaque):
0000 dc 00 ..
end (none):
bootpd[927]: service time 0.000280 seconds
I have no idea why it just stopped working...really wierd.

DHCP client not working

Ok here is the scenario:
I have a laptop with an up to date Arch installation, at home I use a static ip with my router which still has dhcp enabled for some other desktops.
Now at work I needed to use DHCP, so i reconfigured rc.conf to say eth0="dhcp". But it never got an ip address, it always fails. When I checked with ethereali could see the outgoing dhcp packet but no response from the server, the cable and server were clean because all was well under Windows. I tried both dhcpcd and dhclient but no luck with either.
I then compared the packets under windows and arch and came to the conclusion that the only noticeable difference is that the DHCP message type is "DHCP Request" under Windows and for some reason is "DHCP Discover" under arch (there's a binary difference in the packet and thats the way ethereal names the types). Now i'm wondering why the hell does it do that? Why can't dhcpcd and dhclient send a normal dhcp request? Am I missing something really obvious here? Because Dhcp is making me look like an idiot :S And I really need to get online under Linux for work.
Any help is appreciated. Thx.
EDIT: I also have Arch on my desktop, and just tried it using dhcp there, and it works fine. It might be worth mentioning that my desktop is rather out-of-date when it comes to packages while my laptop is prettymuch up-to-date. And yup the packet type is also "Dhcp Request" when i try it on my desktop instead of "Dhcp Discover".. weird.

Solved: Was a driver problem, if you have a broadcom wired ethernet chipset, you need the driver from broadcom because the kernel has some kind of reversed driver built in and it doesn't work properly.

ISP DHCP does not work with netcfg

I have an Arch box that's acting as a router for my home network. As I've mentioned elsewhere, I have been using the old network syntax in a new rc.conf to get both my NICs working together - no other method worked when I set the machine up a week or so ago.
Today, I tried again to see if any updates improved on that and discovered that it still doesn't work, but that my problem is different.
Basically, my eth0 config is set up using netcfg to connect via dhcp:
CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='eth0'
IP='dhcp'
DHCP_TIMEOUT=60
Whenever I try and connect - whether through net-profiles or netcfg -u eth0-dhcp - it always fails to get an ip address from the cable modem. I have tried increasing the DHCP_TIMEOUT with no improvements.
Whenever I revert to the old syntax in my rc.conf and use that it is always able to get an ip reasonably quickly.
Any ideas on what the problem could be?

Obviously, it's taken me *ages* to get around to this. Mainly because the old network config worked and also because I couldn't be bothered to crawl around moving monitor cables from one computer to another.
However, I did try this today and it appears to have worked - so, thanks for that! :-)

Sonicwall DHCP relay not working

I recently set up a new vlan and am trying to get the dhcp server on the existing vlan to issue IPs. I have no trouble getting dhcp working with the sonicwall as the server, but I can't get it to pass it along to the actual server. I've set up the IP of the server as a trusted DHCP relay host but I don't see anything in the logs for the relay for the test host on the vlan. I tagged the port the server is connected to for the new vlan so I'm lost as to why it isn't working. DNS also isn't working using that server for the lookup. I am able to ping it by IP though. I'm sure it's something simple I'm missing but vlans are new to me so I'm still learning.
This topic first appeared in the Spiceworks Community

I recently set up a new vlan and am trying to get the dhcp server on the existing vlan to issue IPs. I have no trouble getting dhcp working with the sonicwall as the server, but I can't get it to pass it along to the actual server. I've set up the IP of the server as a trusted DHCP relay host but I don't see anything in the logs for the relay for the test host on the vlan. I tagged the port the server is connected to for the new vlan so I'm lost as to why it isn't working. DNS also isn't working using that server for the lookup. I am able to ping it by IP though. I'm sure it's something simple I'm missing but vlans are new to me so I'm still learning.
This topic first appeared in the Spiceworks Community

DHCP proxy not working

I have two WLC 4402 servicing several SSIDs. Every SSID represents a different VLAN with a different IP subnet.
Now I want to use one DHCP server for all SSIDs. So I configured the server (I disinguish the requests from the different networks by option 82), put him into the VLAN where the ap-manager and the management interfaces are residing in and configured the DHCP server address of the interfaces on the WLC appropriate to the new setup.
Now my problem: No request arrives at the server. I now tried nearly all options but without success.
I found out that relaying works if the DHCP server is on the SAME subnet. Then all requests are relayed (yes, relayed, unicasted by the controller).
DHCP debug of the WLC says:
DHCP received op BOOTREQUEST (1) (len 313, port 1, encap 0xec03)
DHCP selecting relay 1 - control block settings: dhcpServer: 10.22.72.3, dhcpNetmask: 255.255.248.0, dhcpGateway: 10.22.72.33, dhcpRelay: 10.22.72.1 VLAN: 22
DHCP selected relay 1 - 10.22.72.3 (local address 10.22.72.1, gateway 10.22.72.3, VLAN 22, port 1)
DHCP transmitting DHCP REQUEST (3)
If now I enter the DHCP server address of the new server (directly reachable though the ap-amanager and management interfaces) I get the following:
DHCP received op BOOTREQUEST (1) (len 308, port 1, encap 0xec03)
DHCP selecting relay 1 - control block settings: dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0, dhcpGateway: 0.0.0.0, dhcpRelay: 10.6.72.1 VLAN: 640
DHCP selected relay 1 - NONE
It just seems to ignore the entered DHCP server address.
I tried several software versions (v4.2, v5.2), all the same.
DHCP proxy is enabled - as mentioned, if the DHCP server is in the same subnet, it works fine.
Any suggestions?

Here's the debug data as requested. Its shows the complete connection try of a notebook.
As I took a look on it myself I noticed line 77 of the debug output:
DHCP selected relay 1 - 10.44.1.9 (local address 10.6.72.1, gateway 10.6.72.33, VLAN 640, port 1)
It obviously selected the correct ip of the DHCP server (10.44.1.9). But does the rest mean the Controller tries to forward the request via the standard gateway of the VLAN the client resides in? (10.6.72.33 is the standard gateway of the WLAN of the client). This will fail because the network the DHCP server resides in doesn't have a gateway and is therefor unreachable by other networks (by purpose).
Is there a way to make the controller send out the relayed request though its interface in the network of the DHCP server?

DHCP service not working

Hello,
I have airport express base station and I have set it up to give DHCP IP addresses to wireless clients as I don't have any DHCP server in the ethernet LAN.
But the Airport doesn't give out IP addresses at all.
In the Internet tab, I have selected connect using Ethernet and Connection sharing: "Distribute range of IP addresses".
In the TCP/IP tab, I have given a valid manual IP to the base station.
In the DHCP tab, I have specified the DHCP start/end addresses.
Now when the wireless clients try to connect they only get limited connectivity and if I give a manual IP to the client he/she gets the internet connectivity.
Can anybody guide me what could be causing this? I have airport utility 5.5.3.

"Distribute a range of IP addresses" is a rarely used setting, which would only be used if your service provider has furnished you with a specific bank of IP addresses to use.
Try using the "Share a public IP address" setting for Connection Sharing and the AirPort Express will hand out IP addresses automatically to connected clients.

DHCP Relay not working

I have a 3550 doing routing between vlans with two 3548's connected. I've enabled the ip helper address for the specified vlan I'm testing, but the workstation is unable to contact the server. The DHCP server is Windows Server 2003.
What am I missing here?

Rick,
The extended ping fails:
Protocol [ip]:
Target IP address: 192.168.1.100
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: vlan 15
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.100, timeout is 2 seconds:
Success rate is 0 percent (0/5)
Here are the VLAN outputs. The VLAN is question is the Testing VLAN:
3550:
VLAN Name Status Ports
1 default active Gi0/1, Gi0/2, Gi0/3, Gi0/4
Gi0/5, Gi0/6, Gi0/7, Gi0/8
Gi0/9, Gi0/10
2 Accounting active
3 Engineering active
4 Legal active
5 Ops active
6 Purchasing active
7 Executive active
8 Recep active
9 Admin active
15 Testing active
3548:
VLAN Name Status Ports
1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4,
Fa0/5, Fa0/6, Fa0/7, Fa0/8,
Fa0/9, Fa0/10, Fa0/11, Fa0/12,
Fa0/13, Fa0/14, Fa0/15, Fa0/16,
Fa0/17, Fa0/18, Fa0/19, Fa0/20,
Fa0/21, Fa0/22, Fa0/23, Fa0/24,
Fa0/25, Fa0/26, Fa0/27, Fa0/28,
Fa0/30, Fa0/31, Fa0/32, Fa0/33,
Fa0/34, Fa0/35, Fa0/36, Fa0/37,
Fa0/38, Fa0/39, Fa0/40, Fa0/41,
Fa0/42, Fa0/43, Fa0/44, Fa0/45,
Fa0/46, Fa0/47, Fa0/48, Gi0/2
2 Accounting active
3 Engineering active
4 Legal active
5 Ops active
6 Purchasing active
7 Executive active
8 Recep active
9 Admin active
15 Testing active
2950:
VLAN Name Status Ports
1 default active Fa0/2, Fa0/3, Fa0/4, Fa0/5
Fa0/6, Fa0/7, Fa0/8, Fa0/10
Fa0/11, Fa0/12
2 Accounting active
3 Engineering active
4 Legal active
5 Ops active
6 Purchasing active
7 Executive active
8 Recep active
9 Admin active
15 Testing active Fa0/9

WRE54G - DHCP Soundbridge not working

Similar Messages

Maybe you are looking for