I have successfully configured my DHCP server because I can ping it from the clients PC and my clients PC automatically grabs IP from my DHCP. How my clients can have access to internet. Here is my hardware setup: 1. I connect clients PC and one DHCP server in one unmanaged switch2. I have my Bell DSL Modem but not connected yet to one of these machines. I do not know how I can configure it yet to work with my machines.The IP I assigned started at 10.10.200.10 to 10.10.200.90How do I connect the DSL and configure so that it may give everyone access to internet?
Working on Windows desktops and cannot map drives to unix servers without undoing a particular windows update. network policy pushes this update out again. Cannot change that policy....Active Directory Bridge solution needed to map drive letters from windows users to Unix (SUN) systems?
We have 30 remote workers which we have recently acquired which are being set up with the AnyConnect client to connect to our head end ASA 5510. For security purposes, we have to allow them access to only 3 of our local internal servers, all on our 10.10.X.X/16 subnet. The remotes are being issued a 10.10.50.X/24 address via DHCP on the ASA when connecting. I thought this would be as simple as creating an access list but have not had any luck doing so. In addition, we need to allow them full access to servers in a datacenter connected to our same head end ASA via a site-to-site VPN while they are connected to us using AnyConnect.
We have 30 remote workers which we have recently acquired which are being set up with the AnyConnect client to connect to our head end ASA 5510. For security purposes, we have to allow them access to only 3 of our local internal servers, all on our 10.10.X.X/16 subnet. The remotes are being issued a 10.10.50.X/24 address via DHCP on the ASA when connecting. I thought this would be as simple as creating an access list but have not had any luck doing so. In addition, we need to allow them full access to servers in a datacenter connected to our same head end ASA via a site-to-site VPN while they are connected to us using AnyConnect.
Basically i got a belkin(on a tight bufdget) wireless n modem(f548633) last week. and when i first set it up it was fine except it disconnectiong everytime ia setting was changed on it and taking ages to reconnect to it.
anyway in the last 2 days its started dropping connections to anyone using the wireless. thing is it doesn't completely disconnect it just goes down to around 5kb transfer but when trying to acces the router through IP it doesn't load unless i disconnect and reconnect. i could deal with this at first as it was once every few hours but now its happening every 5 minutes. i plan on sending it back but thought i'd have one last ditch effort at working this out. my security log shows alot of ACK sends to my IP.
02/07/2011 23:26:08 sending ACK to 192.168.2.4 02/07/2011 23:26:08 sending ACK to 192.168.2.8 02/07/2011 23:10:15 sending ACK to 192.168.2.8
I'm having a problem with my clients dropping the network connection constantly throughout the campus. I am using a Cisco 5508 controller and the APs are LAP1141N. At first I thought it was a roaming issue but I tested with only 1 AP and the problem persisted, I can tell you that we don't have interference problems and that our old linksys APs used to work without flaws.
I'm trying to get a couple clients to talk to my Active Directory servers. I've created sub-interfaces on my ASA. So, my clients are on Gi0/1.139 and my two Active Directory servers are on Gi0/1.132. I've enabled traffic on TCP 53-5000 port range according to Microsoft. My clients still can't join the domain. What ports I need to open up? My AD servers are Windows 2003.
I have a WPA2/AES network with PEAP MsChapv2 authentication. I have 2 ACS servers for authentication. The problem I have is dropped clients. Both ACS servers are setup identical. The database replcation has been preformed.A series of 10 clients connects wirelessly and they are all successful. ACS server 1 is the primary and ACS server 2 is the backup. We verified that the 10 users authenticated to the primary ACS. My time out to reauth is 30 minutes on the WiSM. 10 minutes into the test we took down the Primary server. This should have had no impact on the clients. 5 minutes later the clients lost thier authentication and were dropped from the network. They were able to reconnect by shutting down thier wireless client and reconnecting. The authentications were seen on the Backup ACS server.on a test of falling back to the primary the same thing happened again to the clients.
Does the Host file allow connections to your computer?Although I have placed some server names into the host file, Wallwatcher 5.0 is indicating that those servers have made connections. This didn't seem to be a problem before I took some online advice to add servers to my host file. I use iptables on a WNDR3700 router with DD-WRT firmware. In the iptable rules I've also blocked these servers. One example is cnbc7.net and a couple of U.S. Akamai servers.
I am on version 8.2(1) of ASA Code.When accessing a SQL server on a secure internal interface,(Traffic is sourcing from DMZ) i'm getting some timeouts on the initial connection on port 1433. All subsequent connections work fine. Packet tracer shows the connection builds properly, and shouldn't have a connectivity issue. The problem server is a webserver that connects back through the firewall to access the SQL server on port 1433. We also have many other webservers in the DMZ which access the same SQL server, but do not have the same timeout issues. Here are my timeouts, from the config
how to get my servers to run with 2gbs connections on the network. Is it all the same thing just different ways to do it? Some server side, some switch side, some both?In terms of my equipment, I have an Asus RT-N16 router [URL] D-Link DGS-1024D [URL] And (Not hooked up, but i have). Dell 2708 managed switch. [URL]This MOBO (790FX-GD70_[URL] With these NIC's Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) As i said before, id like to trunk/bridge/ w/e you want to call it, so i can get more bandwidth too and from the server.
When I go into the Network Settings, and the end of the page I find a list named "Number of Dynamic DHCP clients: 7". As far as I know, I should only see 4, all 4 laptops; however, I see 2 UNKNOWN entries in this list, and one name "Macondo". Each of these entries have an option (a link) saying "Revoke" and other "Reserve". I am just wonder if these entries are intruders in my home network. What should I do? I am afraid to break my internet connection. By the way, I set up every single one of my family 4 laptops at home with a WPA-PSK using a very long key.
I've just discovered this thing in Windows Event log. The DHCP-Client log is full with this: the client received a NAK from the DHCP Server. Strangely, they still get the desired IP address. (Which are reserved adresses for the MAC adresses.)So I've looked at the logs in the DIR-615 (rev.D, FW: 4.13), and found this:
I'm monkeying around with an 881-W. Clients can associate and authenticate to ssid 'test', but they cannot get a DHCP address. Clients plugged into f 0 - 3 get DHCP addresses just fine.
I've looked at a lot of different guides, ran debugs etc. When wifi clients make DHCP requests the server never gets them. So there must be some IRB thing going on.
I'm trying to understand my options for assigning addresses to VPN clients on an ASA 5510. Under the ASDM, I have a field for DHCP servers, radio buttons: none, dhcp link, dhcp subnet, and field: client address pools. Cisco's VPN examples demonstrate setting up a client address pool, which I did, but the VPN client isn't assigned a gateway in the process so it can't connect to anything; I really don't understand the point of this. I'd like to create a DHCP pool on the ASA for VPN clients as this seems to be the standard configuration. However, I don't know where in the ASDM to configure this and how it's applied. The only DHCP options I found involved creating a DHCP server on an interface, which I don't want to do since VPN users aren't on a physical interface, right?
I have new 2504 WLC + 1041LAP. I configured the first DHCP scope on WLC and the first WLAN. Then I set WLC DHCP server in WLAN properties and tried to connect to WLAN with wireless clients.
My wireless clients are able to authenticate on WLAN, but not able to get IPs from DHCP. The only lease that DHCP shows is for 1041LAP.
If I set permanent IPs on my wireless clients, they can connect and ping WLC.
When on the management interface the clients can't get dhcp but the AP's can on the same vlan. I've tried enabling and disabling dhcp proxy, and using a remote dhcp server as well as the internal server. This same config works on the 4402 we're replacing with version 5.2.193 on it.
I've got a 2106 that I'm installing for a customer and having issues with it assigning DHCP to WiFI clients. What's odd is that this was working at one point at home during testing. Only difference at this point is LAN hardware at the customer location.
Simple config- single flat vlan on Cat2960G switch, ASA5505 serving up DHCP for the network. Wired clients are receiving DHCP fine.
Mgmt IP192.168.0.10/24Mgmt Gateway192.168.0.1Mgmt VLAN0Mgmt Int port1Mgmt DHCP server192.168.0.1AP Mgr Int IP192.168.0.11Virtual GW IP1.1.1.1RF group namerfgrp1SSIDxxxxClient Static IP?noCountry Code802.11a/b/g statusenabledRadio resource mgmt statusenabled I've run dhcpd debug on both the controller and the ASA and I see the DHCPD requests on the controller, but I never see them hitting the ASA.
I don't have the specific version of code it's running, but I know it's 6.0. One of my local Cisco account engineers found some Cisco CSC bugs referencing this issue. One TAC cas even referenced stripping all security off the WiFi, connecting the client and then reimplementing the security again.
My company AP 1231G is not passing the DHCP address to the client from the DHCP server, my config listed below basicly the AP is on its own VLAN 10.1.123.1 and the DHCP server is 10.1.10.2 -- trying to use iphelper to pass DHCP to clients and the AP is on static IP 10.1.123.2--
! ! Last configuration change at 13:15:56 +0800 Fri May 25 2012 by root ! NVRAM config last updated at 13:15:56 +0800 Fri May 25 2012 by root !
I recently upgraded a clients WLC and they keep saying they are unable to get an IP address from the DHCP server. It's a simple, flat network and here is what the logs are showing.
*apfReceiveTask: Apr 11 13:37:25.477: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'management'. Marking interface dirty. *apfReceiveTask: Apr 11 13:37:17.278: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'management'. Marking interface dirty. *apfReceiveTask: Apr 11 13:37:05.880: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'management'. Marking interface dirty. *apfReceiveTask: Apr 11 13:13:47.397: %SIM-3-DHCP_SERVER_NO_REPLY: sim_interface.c:1039 Failed to get DHCP response on interface 'management'. Marking interface dirty.
I would like to share one problem with WLC 5508 . we added a new virtual interface on the WLC. One new SSID is associated with this interface.
We created a ACL for this interface to restrict the access via WIFI to certian services. It´s not correct that everything works fine because the change were not applied. [code]
The changes of the ACL are applied on the fly, but for reason we don´t know, the clients don´t get a DHCP IP-Address (after changing the ACL) until the Controller is rebooted.
I know this question was asked many times, but I'm still not able to finalize my configuration on 871w. LAN part works fine, but wireless clients do not get DHCP IP. here is the config:
Building configuration... Current configuration : 2092 bytes ! version 12.4 no service pad service timestamps debug date time m sec service timestamps log date time m sec no service password-encryption ! [ code ].....
I'd like to have LAN and WLAN clients in same 192.168.1.0 sub net.
I have a LAN running on a 10.60.1.* scope and I am running out of IP addresses. My windows server 2003 IP is 10.60.1.3 router is 10.60.1.4, If I create a superscope with 10.60.1.* and 10.60.2.* scopes within it and add an IP address from the 10.60.2.* range to both the servers and routers network configurations would this allow the clients on both scopes to see the network? The router links our office to other offices as well would the new IP range cause all kinds of routing issues?I know with the resubnetting option changing to a 255.255.254.0 from the current 255.255.255.0 would allow the use of 10.60.0.1-10.60.1.254 in a single subnet but I suspect this would cause problems with seeing the other offices unless all routers were reconfigured to recognise our offices new subnet mask.
I am trying to set up a small domain for my business. I just purchased a Windows 2008 server and would like to use it as my domain controller.Also, I just had a new ATT DSL line put in. It came with a 2Wire modem/4-port router/wireless router device, therefore the modem can handle DHCP. The line has a static IP address as well so that I can eventually use my own exchange server and web server.I have tried 2 different configurations and couldn't get either to work) I tried to put the router into Bridged Mode and use DHCP server on my server using a PPPoe connection to connect to the Internet. I was confused as to what my static IP address and default gateway of my server should be.2) Then I tried to turn DHCP server off on the server and routing back on the modem/router. This didn't work either.What method would you recommend and why? Also I have some additional questions on each method.
Method 1)
* What is the static IP address of the server. Is it in the 192.168.1.x address or the static IP assigned to my account?
* Do I need a second Nic Card And Router to connect to the rest of my network or can I use the router provide
* What would the Static IP addresses of the additional PC be. Do I need more than 1 static IP from AT&T Method 2)
* Will this allow me to use all internal IP addresses on my machines and use port forwarding if I want a specific box to be a web server or exchange server.
I recently noticed my 'Number of Dynamic DHCP Clients' on Network Settings is always empty. Before, it always registered a list since there are several devices that are connected to our wireless network (laptops, mobile phones, desktops).
I have a 4402 (version 7.0.235) working with 10 units of 1121 APs connected to it. The WLC is not configured to work in LAG mode. Physical portt #1 is connected to the Main Switch (trunk). I have 3 WLAN mapped to 3 Different VLAN and Everything (security and internal, external DHCP) is working swell...Now- I have connected Physical port #2 directly to an ADSL Router (giga port), Configured Port 2 as untaggedwith the proper IP details.I have configured this interface to receive DHCP from the ADSL Router and for some reason, Clients are not getting addresses.When I assign a Static address to my laptop I get internet access and all is nice. I tried configuring The WLC internal DHCP server (instead of the ADSL router) and that didn't work. It seems like a DHCP problem but I dont understand the source of the problem of think of the solution.When turning off the proxy settings I noticed that it worked. Is there anything to do with that? The problem was that after a while the other WLANs starting causing DHCP issues as well.
I have 19 locations, each with 1 or more LAP1142N AP's in FlexConnect mode, AP's are primed using CAPWAP to my 5508 WLC at the datacenter. The AP's join the WLC without issue every time. I have two WLAN's, one guest and one staff, the guest network is open and obtains DHCP from a WatchGuard XTM33 firewall at each of the remote locations. The staff side is WPA2/RADIUS and DHCP is assigned from the WLC. Each AP is assigned a static IP that is not in the DHCP scope. For example: DHCP scope on the branch firewall is 192.168.1.10-250 the AP will be assigned static IP of 192.168.1.1.. The AP's are connected to a HP procurve switch that has a untagged VLAN, the firewall is using the native vlan 1 and so is the AP.
I have been running this network for over a year and it has not had a single issue until the last two weeks. Nothing on the network has changed or has been upgraded.The issue I am seeing is that clients are no longer able to connect to the AP and do not get DHCP assigned to them. I am able to get it working, if I remove the static IP from the AP, the AP will reboot, join the controller, then begin working, users can connect and DHCP is assigned from the firewall as it should. However, If the AP then reboots, the AP will join back to the controller but no clients can connect nor do they get a DHCP address. So, I then reassign a static IP to the AP again and it reboots, connects to the controller and clients then can connect and get DHCP.i've found several posts on this topic, in fact the patch of unassigning or reassigning static IP is one that I found. I am also waiting on my SmartNet to start up and will be contacting Cisco support as well.
