Intel4965 | Association/DHCP | Status Issue

I can't reliably connect to any network. I have tried just iwconfig, wpa_supplicant, and netcfg with archassistant, and I can't figure out what the problem is.
Generally, to connect I have to run these commands, and this will "usually", but NOT always get me connected to a WEP network.
iwconfig wlan0 essid APNAME
iwconfig wlan0 key 1234567890
dhcpcd wlan0 <times out everytime>
iwlist wlan0 scan <always shows results, although for 2 kernel revisions it didn't>
rm /var/run/dhcpcd-wlan0.pid
dhcpcd wlan0<finally works>
Information/things I have tried.
The 4965 module is in my modules array.
ifconfig wlan0 up
doesn't help.
Putting 'wlan0' in the interfaces array in rc.conf doesn't help.
I was able to connect with wpa_supplicant a few minutes ago. I still had to do that dhcpcd and iwlist stuff, but it worked.
Then I put
wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B
in my rc.local(command I used to get it working the first time, except the -B) and restarted. Starting up wpa_gui showed that I was associated, but I could not get an IP address. I disconnected, reconnected, did the dhcpcd stuff, and nothing
Netcfg also didn't work. On launching archassistant, and then trying to connect to one of the profiles I set up through archassistant, I get this;
wireless device set in config :
wireless device used : wlan0
profile started : npnwap 1
error issuing netcfg command.
Double clicking the archassistant icon in the tray, or trying to scan in archassistant, I get this error;
error ifconfigUpProcess
Dmesg;
[zack@boxxy ~]$ dmesg | grep 4965
iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.23k
iwl4965: Copyright(c) 2003-2007 Intel Corporation
iwl4965: Detected Intel Wireless WiFi Link 4965AGN
iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels
phy0: Selected rate control algorithm 'iwl-4965-rs'
I appreciate any suggestions.
Zack
Last edited by Sjoden (2008-07-07 21:03:21)

Sorry I didn't post last night, we went to my sister in laws house.
I started up my laptop at work today. Wicd took two tries to connect to my works WAP(s, we have 3 of them, all the same name, for roaming). I do a 'pacman -Syu'. It runs smoothly, only warning I get is about a font-config change. I only have 1 extra font pkg installed so I didn't worry about it.
I reboot, and wicd fails. I can associate, but I can't get an IP address. I try all 3 WAPs, none work. I try different things for about 30 minutes, rebooting, retyping key, restarting the service and the tray.py for wicd, nothing.
Plug in my network cable, Add the testing repo, re sync, and 'pacman -S testing/netcfg'. All runs fine. I make a profile from the default wep.example;
[zack@boxxy ~]$ cat /etc/network.d/???wap
CONNECTION="wireless"
DESCRIPTION="???'s external wireless network."
INTERFACE=wlan0
SCAN="yes"
SECURITY="wep"
ESSID="???WAP"
KEY="1234567890"
IP="dhcp"
I run 'netcfg2 ???wap'. It fails. I run it again, it finishes. I unplug the networking cable. No go. I remove the pid for dhcpcd on eth0, nothing. I kill dhcpcd and dhclient. Retry, nothing. I reboot, retry netcfg2, nothing again. I'm about to try and figure out how to use the quirks.
From /var/log/messages.log;
Jul 7 15:12:16 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:12:16 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:12:16 boxxy dhclient: All rights reserved.
Jul 7 15:12:16 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:12:16 boxxy dhclient:
Jul 7 15:12:17 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:12:17 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:12:17 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:12:19 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:12:27 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:12:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
Jul 7 15:12:51 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
Jul 7 15:13:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jul 7 15:13:12 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:13:20 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jul 7 15:13:35 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul 7 15:13:48 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:13:48 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:13:51 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:13:54 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:14:26 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:14:26 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:14:29 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:14:29 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:14:29 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 3963
Jul 7 15:14:29 boxxy dhclient: removed stale PID file
Jul 7 15:14:29 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:14:29 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:14:29 boxxy dhclient: All rights reserved.
Jul 7 15:14:29 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:14:29 boxxy dhclient:
Jul 7 15:14:30 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:14:30 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:14:30 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:14:31 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:14:39 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:14:55 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:15:02 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul 7 15:15:15 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul 7 15:15:25 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
Jul 7 15:15:44 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jul 7 15:15:56 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:15:56 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:15:59 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:16:02 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:17:31 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:17:31 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:17:33 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:17:33 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:17:33 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 5007
Jul 7 15:17:33 boxxy dhclient: removed stale PID file
Jul 7 15:17:33 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:17:33 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:17:33 boxxy dhclient: All rights reserved.
Jul 7 15:17:33 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:17:33 boxxy dhclient:
Jul 7 15:17:34 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:17:34 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:17:34 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:17:35 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:17:40 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:17:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul 7 15:17:52 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:18:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Jul 7 15:18:14 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
Jul 7 15:18:30 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul 7 15:18:48 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:18:48 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:18:51 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:18:54 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:21:39 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:21:40 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:21:59 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:21:59 boxxy r8169: eth0: link down
Jul 7 15:21:59 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:22:01 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:22:01 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:22:02 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 6427
Jul 7 15:22:02 boxxy dhclient: removed stale PID file
Jul 7 15:22:02 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:22:02 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:22:02 boxxy dhclient: All rights reserved.
Jul 7 15:22:02 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:22:02 boxxy dhclient:
Jul 7 15:22:03 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:22:03 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:22:03 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:22:04 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:22:12 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:22:31 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jul 7 15:22:37 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul 7 15:22:48 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jul 7 15:23:09 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul 7 15:23:27 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Jul 7 15:23:32 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:23:32 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:23:35 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:23:38 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:24:58 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:24:58 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:25:00 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:25:00 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:25:01 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 8688
Jul 7 15:25:01 boxxy dhclient: removed stale PID file
Jul 7 15:25:01 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:25:01 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:25:01 boxxy dhclient: All rights reserved.
Jul 7 15:25:01 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:25:01 boxxy dhclient:
Jul 7 15:25:02 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:25:02 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:25:02 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:25:03 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:25:11 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:25:20 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jul 7 15:25:26 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul 7 15:25:37 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul 7 15:25:47 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:25:54 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:26:01 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul 7 15:26:14 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:26:21 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:26:21 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:26:24 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:26:27 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:29:35 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:29:35 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:29:37 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:29:37 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:29:38 boxxy dhclient: There is already a pid file /var/run/dhclient.pid with pid 9688
Jul 7 15:29:38 boxxy dhclient: removed stale PID file
Jul 7 15:29:38 boxxy dhclient: Internet Systems Consortium DHCP Client V3.0.6
Jul 7 15:29:38 boxxy dhclient: Copyright 2004-2007 Internet Systems Consortium.
Jul 7 15:29:38 boxxy dhclient: All rights reserved.
Jul 7 15:29:38 boxxy dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jul 7 15:29:38 boxxy dhclient:
Jul 7 15:29:39 boxxy dhclient: Listening on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:29:39 boxxy dhclient: Sending on LPF/wlan0/00:13:e8:2e:83:15
Jul 7 15:29:39 boxxy dhclient: Sending on Socket/fallback
Jul 7 15:29:42 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:29:49 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:30:03 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:30:10 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul 7 15:30:28 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jul 7 15:30:38 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul 7 15:30:49 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jul 7 15:31:04 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:31:04 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:31:07 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:31:10 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:31:55 boxxy r8169: eth0: link up
Jul 7 15:31:56 boxxy r8169: eth0: link down
Jul 7 15:31:57 boxxy r8169: eth0: link up
Jul 7 15:32:00 boxxy r8169: eth0: link down
Jul 7 15:32:02 boxxy r8169: eth0: link up
Jul 7 15:32:32 boxxy NET: Registered protocol family 10
Jul 7 15:32:32 boxxy lo: Disabled Privacy Extensions
Jul 7 15:32:38 boxxy ACPI: PCI interrupt for device 0000:02:00.0 disabled
Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: dhcpcd 3.2.1 starting
Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: hardware address = 00:13:a9:f1:a0:b7
Jul 7 15:33:27 boxxy dhcpcd[12617]: eth0: broadcasting for a lease
Jul 7 15:33:30 boxxy dhcpcd[12617]: eth0: offered 10.0.1.106 from 10.0.1.200
Jul 7 15:33:30 boxxy dhcpcd[12617]: eth0: checking 10.0.1.106 is available on attached networks
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: leased 10.0.1.106 for 86400 seconds
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding IP address 10.0.1.106/16
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding default route via 10.0.1.1 metric 0
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: adding route to 169.254.0.0/16 metric 0
Jul 7 15:33:31 boxxy dhcpcd[12617]: eth0: exiting
Jul 7 15:54:29 boxxy ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Jul 7 15:54:29 boxxy ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 7 15:55:39 boxxy ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jul 7 15:55:42 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:55:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jul 7 15:55:42 boxxy dhclient: DHCPOFFER from 10.0.1.200
Jul 7 15:55:42 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 7 15:55:42 boxxy dhclient: DHCPACK from 10.0.1.200
Jul 7 15:55:42 boxxy dhclient: bound to 10.0.1.106 -- renewal in 32528 seconds.
Jul 7 15:55:43 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul 7 15:55:45 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:55:48 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul 7 15:55:50 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:55:53 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
Jul 7 15:55:59 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 7
Jul 7 15:56:00 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jul 7 15:56:00 boxxy r8169: eth0: link down
Jul 7 15:56:06 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 13
Jul 7 15:56:07 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
Jul 7 15:56:19 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
Jul 7 15:56:27 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Jul 7 15:56:29 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 10
Jul 7 15:56:39 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
Jul 7 15:56:44 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:56:44 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:56:48 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
Jul 7 15:57:01 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:57:01 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: received SIGTERM, stopping
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing default route via 10.0.1.1 metric 0
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing route to 169.254.0.0/16 metric 0
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: removing IP address 10.0.1.106/16
Jul 7 15:57:05 boxxy dhcpcd[12618]: eth0: exiting
Jul 7 15:57:19 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:57:19 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 6
Jul 7 15:57:20 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 7 15:57:23 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:57:24 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 7 15:57:25 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 15
Jul 7 15:57:27 boxxy dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 7 15:57:30 boxxy dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jul 7 15:57:35 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jul 7 15:57:38 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Jul 7 15:57:40 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 21
Jul 7 15:57:41 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:57:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jul 7 15:57:45 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jul 7 15:57:48 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Jul 7 15:57:49 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Jul 7 15:57:53 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Jul 7 15:58:01 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 16
Jul 7 15:58:01 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
Jul 7 15:58:07 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:58:15 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Jul 7 15:58:17 boxxy dhclient: DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
Jul 7 15:58:20 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:58:20 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:58:22 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Jul 7 15:58:26 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jul 7 15:58:34 boxxy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
Jul 7 15:58:36 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:58:36 boxxy dhclient: Trying recorded lease 192.168.5.24
Jul 7 15:58:39 boxxy dhclient: Trying recorded lease 192.168.2.196
Jul 7 15:58:42 boxxy dhclient: No working leases in persistent database - sleeping.
Jul 7 15:58:42 boxxy dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
Jul 7 15:58:43 boxxy dhclient: No DHCPOFFERS received.
Jul 7 15:58:43 boxxy dhclient: Trying recorded lease 10.0.1.106
Jul 7 15:58:46 boxxy dhclient: No working leases in persistent database - sleeping.
[root@boxxy examples]#
From /var/log/pacman.log;
[2008-07-07 13:25] synchronizing package lists
[2008-07-07 13:26] starting full system upgrade
[2008-07-07 14:42] upgraded freetype2 (2.3.6-1 -> 2.3.7-1)
[2008-07-07 14:42] Symlinking new configuration files... done.
[2008-07-07 14:42]
[2008-07-07 14:42] ===> Important Fontconfig configuration change <===
[2008-07-07 14:42]
[2008-07-07 14:42] The way fontconfig is configured has been changed.
[2008-07-07 14:42] Configuration is done via /etc/fonts/conf.avail and conf.d.
[2008-07-07 14:42] Read /etc/fonts/conf.avail/README for more information.
[2008-07-07 14:42]
[2008-07-07 14:42] Configuration via /etc/fonts/local.conf is still possible,
[2008-07-07 14:42] but is no longer recommended for options available in conf.avail.
[2008-07-07 14:42]
[2008-07-07 14:42] Adding missing configuration files... done.
[2008-07-07 14:42] Removing outdated configuration files... done.
[2008-07-07 14:43] updating font cache... done.
[2008-07-07 14:43] upgraded fontconfig (2.5.0-1 -> 2.6.0-2)
[2008-07-07 14:43] upgraded gcc-libs (4.3.1-1 -> 4.3.1-2)
[2008-07-07 14:43] upgraded gcc (4.3.1-1 -> 4.3.1-2)
[2008-07-07 14:43] upgraded glibmm (2.16.2-1 -> 2.16.4-1)
[2008-07-07 14:43] >>> Updating module dependencies. Please wait ...
[2008-07-07 14:43] >>> MKINITCPIO SETUP
[2008-07-07 14:43] >>> ----------------
[2008-07-07 14:43] >>> If you use LVM2, Encrypted root or software RAID,
[2008-07-07 14:43] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2008-07-07 14:43] >>> More information about mkinitcpio setup can be found here:
[2008-07-07 14:43] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2008-07-07 14:43]
[2008-07-07 14:43] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2008-07-07 14:43] ==> Building image "default"
[2008-07-07 14:43] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2008-07-07 14:43] :: Begin build
[2008-07-07 14:43] :: Parsing hook [base]
[2008-07-07 14:43] :: Parsing hook [udev]
[2008-07-07 14:43] :: Parsing hook [autodetect]
[2008-07-07 14:43] :: Parsing hook [pata]
[2008-07-07 14:43] :: Parsing hook [scsi]
[2008-07-07 14:43] :: Parsing hook [sata]
[2008-07-07 14:43] :: Parsing hook [keymap]
[2008-07-07 14:43] :: Parsing hook [filesystems]
[2008-07-07 14:43] :: Generating module dependencies
[2008-07-07 14:43] :: Generating image '/boot/kernel26.img'...SUCCESS
[2008-07-07 14:43] ==> SUCCESS
[2008-07-07 14:43] ==> Building image "fallback"
[2008-07-07 14:43] ==> Running command: /sbin/mkinitcpio -k 2.6.25-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2008-07-07 14:43] :: Begin build
[2008-07-07 14:43] :: Parsing hook [base]
[2008-07-07 14:43] :: Parsing hook [udev]
[2008-07-07 14:43] :: Parsing hook [pata]
[2008-07-07 14:43] :: Parsing hook [scsi]
[2008-07-07 14:43] :: Parsing hook [sata]
[2008-07-07 14:44] :: Parsing hook [keymap]
[2008-07-07 14:44] :: Parsing hook [filesystems]
[2008-07-07 14:44] :: Generating module dependencies
[2008-07-07 14:44] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2008-07-07 14:44] ==> SUCCESS
[2008-07-07 14:44] upgraded kernel26 (2.6.25.6-1 -> 2.6.25.10-1)
[2008-07-07 14:44] upgraded lame (3.97-1 -> 3.98-1)
[2008-07-07 14:44] upgraded libpng (1.2.28-1 -> 1.2.29-1)
[2008-07-07 14:44] upgraded libsm (1.0.3-1 -> 1.1.0-1)
[2008-07-07 14:44] upgraded libxfont (1.3.2-1 -> 1.3.3-1)
[2008-07-07 14:44] upgraded libxft (2.1.12-1 -> 2.1.13-1)
[2008-07-07 14:44] upgraded libxp (1.0.0-1 -> 1.0.0-2)
[2008-07-07 14:44] upgraded randrproto (1.2.1-1 -> 1.2.2-1)
[2008-07-07 14:44] upgraded libxrandr (1.2.2-1 -> 1.2.3-1)
[2008-07-07 14:44] upgraded libxtrap (1.0.0-1 -> 1.0.0-2)
[2008-07-07 14:44] upgraded libxxf86vm (1.0.1-1 -> 1.0.2-1)
[2008-07-07 14:44] upgraded nss (3.12rc4-1 -> 3.12-1)
[2008-07-07 14:44] upgraded xf86-input-mouse (1.2.3-1 -> 1.3.0-1)
[2008-07-07 14:44] upgraded xorg-xauth (1.0.2-1 -> 1.0.3-1)
[2008-07-07 14:44] upgraded xorg-xkb-utils (1.0.2-2 -> 7.3-1)
[2008-07-07 14:44] upgraded xtrans (1.2-1 -> 1.2.1-1)
[2008-07-07 15:33] synchronizing package lists
[2008-07-07 15:33] starting full system upgrade
[2008-07-07 15:34] upgraded pcre (7.7-1 -> 7.7-2)
[2008-07-07 15:35] synchronizing package lists
[2008-07-07 15:47] installed netcfg (2.1.0_B2-1)
This is rediculous.
Zack
/edit
I was able to load the google homepage after adding the preessid quirk, and using the 'netcfg' command instead of 'netcfg2'. I restarted, and it doesn't work(I'm pretty sure my eth cable was unplugged when loaded, could be wrong);
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Wireless association failed. [FAIL]
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# netcfg2 npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# killall wicd
wicd: no process killed
[root@boxxy zack]# /etc/rc.d/wicd stop
:: Stopping wicd Daemon [DONE]
[root@boxxy zack]# killall dhcpcd
dhcpcd: no process killed
[root@boxxy zack]# killall dhclient
dhclient: no process killed
[root@boxxy zack]# netcfg npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# netcfg2 npnwap
:: npnwap up - Network unavailable [FAIL]
[root@boxxy zack]# nano /etc/network.d/npnwap
[root@boxxy zack]# netcfg npnwap
:: npnwap up [DONE]
[root@boxxy zack]# nano /etc/network.d/npnwap
[root@boxxy zack]# /etc/rc.d/wicd stop
:: Stopping wicd Daemon [DONE]
[root@boxxy zack]# netcfg npnwap
> npnwap already connected
[root@boxxy zack]#
Last edited by Sjoden (2008-07-07 21:36:17)

Similar Messages

Internet DHCP/DNS issues with WRT1900ac

I've had a WRT1900ac now for about 2 weeks and the problems seem to be escalating. Need help. And yes, I've already read dozens of threads about these issues and nothing seems to be working.
Most of the problems seem to be centered around this DHCP/DNS issue that so many have been reporting.
First, the symptoms:
Galaxy S4 phones when connected via wifi have some apps that don't update (facebook and google play)
Some computers (both Win 7) will connect to the network just fine, both wired and wireless - but won't be able to get to the internet
I've spent the last 2-3 days of my life reading forums and trying all sorts of things to get this to work properly (like my old router) and I'm still stuck. Some things I've tried:
Firmware is up-to-date (latest version: 1.1.8.164461)
Manually assigned static DNS in router config settings (connectivity -> local network) to various combinations including the router address, 8.8.8.8, 8.8.4.4, 75.75.75.75, 75.75.76.76 (I have comcast), OpenDNS addresses, etc. I read that the router address is not needed, so I stopped including it.
I manually assigned IPs and DNS on the Galaxy S4 phones and that seemed to work... but also seems unnecessary.
I've reserved DHCP addresses on the computers in question, that didn't seem to work, I also manually set DNS on one of the comupters (can't on the other... long story/not my computer) and that worked for a while and then stopped working.
The only way to get one of the computers on the internet now is to turn on the guest network (even though the computer is hard wired to the router), connect, and then the wired network works. No clue why this is, but my guess is that it needs the guest network for DNS, then it fails back over to the wired network. Once that happens, I can actually turn off the wifi on the computer and everything works great... until I reboot. Key point: I can't change any settings on that box other than entering in SSID/passphrase info for the wireless connection. I can connect to the regular (non-Guest) wifi just fine - I just can't ever get to the internet.
I've tried massaging DHCP settings on the router until I'm blue in the face - Static DNS, reserving DHCP addresses, hell I even put one of the computers in the DMZ to see if that would work and it still can't connect to the internet (it's worth noting that with my old router, Linksys WRT310N, the setup was literally plug-and-play - no hassle with any of this).
I've tried countless router reboots, factory resets, turning off my modem and router for 2+ minutes, and nothing is working.
I even read somewhere that if you modify your DHCP settings at all that the WRT1900ac stops doing DNS properly and breaks, so I even tried several "hard" factory resets and used all the default DHCP/DNS settings. And it worked... for a few hours.
Seriously, I'm at my wit's end. I'm out a lot of money on this thing and it's been one headache after another. Please help.

I think for most people its a bad idea to hold out that hope, lol. It seems like a great piece of hardware but if you really need a router and don't want to have to 'play' with it, its probably not a good choice. I have an EA6900 that I am very happy with but it has the same restrictions as far as DNS and I really hate the idea that I am forced to use the smartwifi portal. I would really like for them to give me a choice of the old gui or the new one and let ME decide. Lots of routers to choose from out there now and new ones seem to be coming out all the time so do some reading and see if something suits you better. Good luck!

Vlans dhcp status are not received

Hello,
I am configuring vlan on sg300-20 in dhcp mode.
One vlan that is directed connected to the adsl router get ip address and when I connect host to the ports in this vlan they also receive ip address and can go on internet.
The other four vlans dhcp status are not received.
Kindly help me check this. Thanks
Below is the config log:
switch4ba497#sh running-config
config-file-header
switch4ba497
v1.2.9.44 / R750_NIK_1_2_584_002
CLI v1.0
file SSD indicator encrypted
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
vlan database
vlan 5,10,20,30,40
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
ip dhcp relay address 192.168.3.1
ip dhcp information option
no boot host auto-config
bonjour interface range vlan 1
hostname switch4ba497
line telnet
exec-timeout 0
exit
no passwords complexity enable
username cisco password encrypted 7af78c911d5b48bea1dc2449d9d89513abeb4be5 privilege
15
ip http timeout-policy 0 http-only
ip name-server 192.168.1.1 192.168.3.1
ip telnet server
interface vlan 1
ip address 192.168.2.254 255.255.255.0
no ip address dhcp
interface vlan 5
name WAN
ip address dhcp
interface vlan 10
name Studio
ip address dhcp
interface vlan 20
name Service
ip address dhcp
interface vlan 30
name Admin
ip address dhcp
interface vlan 40
name Data
ip address dhcp
interface gigabitethernet1
switchport mode access
interface gigabitethernet2
switchport mode access
switchport access vlan 10
interface gigabitethernet3
switchport mode access
switchport access vlan 10
interface gigabitethernet4
switchport mode access
switchport access vlan 10
interface gigabitethernet5
switchport mode access
switchport access vlan 10
interface gigabitethernet6
switchport mode access
switchport access vlan 10
interface gigabitethernet7
switchport mode access
switchport access vlan 10
interface gigabitethernet8
switchport mode access
interface gigabitethernet9
switchport mode access
switchport access vlan 20
interface gigabitethernet10
switchport mode access
switchport access vlan 20
interface gigabitethernet11
switchport mode access
switchport access vlan 20
interface gigabitethernet12
switchport mode access
switchport access vlan 20
interface gigabitethernet13
switchport mode access
switchport access vlan 30
interface gigabitethernet14
switchport mode access
switchport access vlan 30
interface gigabitethernet15
switchport mode access
switchport access vlan 30
interface gigabitethernet16
switchport mode access
switchport access vlan 30
interface gigabitethernet17
switchport mode access
interface gigabitethernet18
switchport trunk native vlan 40
interface gigabitethernet19
switchport mode access
switchport access vlan 5
interface gigabitethernet20
switchport trunk native vlan 5
switch4ba497#sh ip int
    IP Address         I/F       Type     Directed   Precedence   Status
                                          Broadcast
0.0.0.0/32          vlan 10   DHCP        disable    No         Not
                                                                received
0.0.0.0/32          vlan 20   DHCP        disable    No         Not
                                                                received
0.0.0.0/32          vlan 30   DHCP        disable    No         Not
                                                                received
0.0.0.0/32          vlan 40   DHCP        disable    No         Not
                                                                received
192.168.2.254/24    vlan 1    Static      disable    No         Valid
192.168.3.102/24    vlan 5    DHCP        disable    No         Valid
switch4ba497#
Also i do not understand why the ip address is 0.0.0.0/32 because the dhcp server ip address is 192.168.3.1

Dear Customer,
Thank you for reaching Small Business Support Community.
In Layer 2 system mode, only the management VLAN can be configured with a static or dynamic IP address. In Layer 3 system mode, all the interface types (ports,LAGs, and/or VLANs) on the device can be configured with a static or dynamic IP. Configuring the device to work in either mode is performed in the Administration >System Settings page
When a DCHP Client starts a discovery process, it assigns a dummy IP address 0.0.0.0 before the real address is obtained. This dummy address has the status of “Not Received”.
Pretty much your problem should be solved by changing to Layer3 system mode. Please let me know if anything comes up and/or if there is any further assistance I may help you with.
Kind regards,
Jeffrey Rodriguez S. .:|:.:|:.
Cisco Customer Support Engineer
*Please rate the Post so other will know when an answer has been found.

Dhcp status are not received on sg300-20

Hello,
I am configuring vlan on sg300-20 in dhcp mode.
One vlan (5) that is directed connected to the adsl router get ip address and when I connect host to the ports in this vlan they also receive ip address and can go on internet.
The other four vlans dhcp status are not received
Kindly help me check this. Thanks
switch4ba497#sh running-config
config-file-header
switch4ba497
v1.2.9.44 / R750_NIK_1_2_584_002
CLI v1.0
file SSD indicator encrypted
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
vlan database
vlan 5,10,20,30,40
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
ip dhcp relay address 192.168.3.1
ip dhcp information option
no boot host auto-config
bonjour interface range vlan 1
hostname switch4ba497
line telnet
exec-timeout 0
exit
no passwords complexity enable
username cisco password encrypted 7af78c911d5b48bea1dc2449d9d89513abeb4be5 privilege
15
ip http timeout-policy 0 http-only
ip name-server 192.168.1.1 192.168.3.1
ip telnet server
interface vlan 1
ip address 192.168.2.254 255.255.255.0
no ip address dhcp
interface vlan 5
name WAN
ip address dhcp
interface vlan 10
name Studio
ip address dhcp
interface vlan 20
name Service
ip address dhcp
interface vlan 30
name Admin
ip address dhcp
interface vlan 40
name Data
ip address dhcp
interface gigabitethernet1
switchport mode access
interface gigabitethernet2
switchport mode access
switchport access vlan 10
interface gigabitethernet3
switchport mode access
switchport access vlan 10
interface gigabitethernet4
switchport mode access
switchport access vlan 10
interface gigabitethernet5
switchport mode access
switchport access vlan 10
interface gigabitethernet6
switchport mode access
switchport access vlan 10
interface gigabitethernet7
switchport mode access
switchport access vlan 10
interface gigabitethernet8
switchport mode access
interface gigabitethernet9
switchport mode access
switchport access vlan 20
interface gigabitethernet10
switchport mode access
switchport access vlan 20
interface gigabitethernet11
switchport mode access
switchport access vlan 20
interface gigabitethernet12
switchport mode access
switchport access vlan 20
interface gigabitethernet13
switchport mode access
switchport access vlan 30
interface gigabitethernet14
switchport mode access
switchport access vlan 30
interface gigabitethernet15
switchport mode access
switchport access vlan 30
interface gigabitethernet16
switchport mode access
switchport access vlan 30
interface gigabitethernet17
switchport mode access
interface gigabitethernet18
switchport trunk native vlan 40
interface gigabitethernet19
switchport mode access
switchport access vlan 5
interface gigabitethernet20
switchport trunk native vlan 5
switch4ba497#sh ip int
    IP Address         I/F       Type     Directed   Precedence   Status
                                          Broadcast
0.0.0.0/32          vlan 10   DHCP        disable    No         Not
                                                                received
0.0.0.0/32          vlan 20   DHCP        disable    No         Not
                                                                received
0.0.0.0/32          vlan 30   DHCP        disable    No         Not
                                                                received
0.0.0.0/32          vlan 40   DHCP        disable    No         Not
                                                                received
192.168.2.254/24    vlan 1    Static      disable    No         Valid
192.168.3.102/24    vlan 5    DHCP        disable    No         Valid
switch4ba497#
I also do not understand why the ip address is 0.0.0.0/32.
Becuase the dhcp address 192.168.3.1/24
Thanks.

Hello Tom,
Yes i can feel you taking me toward the solution.
Actually I have an ADSL router that has DHCP capability and my vlan interfaces are to receive ip address from it.
The adsl router Ip address is 192.168.3.1
Vlan 5 WAN which is directly connected to the adsl router get Ip address while the other vlan do not.
When I assign port from other vlan to vlan 5 and I attach host to the port they get ip address and go on internet. The strange thing is that the other vlan do not get ip address. Thanks.

Status issues across multiple devices

Hi. I seem to be having the opposite problem to most people reporting status issues. I have friends telling me I'm always away or offline in the evenings, even tho I have 5 devices I can use Skype on. My main 3 clients are my win7 work PC (which I quiet often leave on over night), my xbox one which is on most evenings, and my iPhone. I also have an iPad and win8 laptop But I only occasionally use these for Skype.
Do I have to sign in to the Skype app every time I switch on my xbox one to get it to show me as online? Is there something else I need to do? Do you think it's because I have too many clients?

When I try to go to iTunes music match on her phone it asks me to sign into match, which I am assuming is the same as her Apple ID name and password. This is a different name and password than my account. So, it seems that she cannot access my "cloud" from her phone in order to download music that I have purchased. I guess since she has her own iClud account, she needs to sign up for iTunes match through that account and pay the fee. I was hoping we could access the same 'Cloud" to have the same library of music? Hope that made sense.
Thanks for the help.

Bundle Status Issues

Hello,
Several of our bundles are reporting their effective statuses incorrectly. For example, one bundle that makes a bunch of registry changes has been installed successfully on every device I've checked, yet it only reports as being effective on 34 devices, with 253 pending. This is definitely incorrect. Any ideas? How does Zenworks determine if all a bundles actions (ie. registry edits) have been completed successfully?

hi
i have this status issue also. i have 22 device succeeded, but when i click on it, it list's me no device.
i really need this function, to control where it has installed and where not.
i have ZCM 10.3.3. on SLES 10.
have the debug activated, look at the zmd-messages.log but really dont know for what to search !!!!
i opened a ticket, but they dont have a really fast solution....(no solution till yet).
Sascha
>>> Anders Gustafsson<[email protected]> 22.11.2010 09:50 >>>
Chewmanfoo,
> Thanks. 10.3.1 and I'll check the logs.
>
Note that you will need debug logging to see anything useful.
Check zmd-messages, but make sure a zac emp wakeup
is done first. See:
http://www.novell.com/support/viewCo...rnalId=3418069
- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)
Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

Hi, I finally got lucky and past the "other" memory status issues when syncing. Now I'm "waiting for changes to be applied" sync stuck all night (itunes yesomite iPhone 6 plus). is this a bug? I have not had a single successful sync with yesomite.

hi, I finally got lucky and past the "other" memory status issues when syncing. Now I'm "waiting for changes to be applied" sync stuck all night (itunes yesomite iPhone 6 plus). is this a bug? I have not had a single successful sync with yesomite.
please help. this issue prevents music from syncing. I have set the sync setting to convert songs to 192kbps AAC to save space, I figure that could slow the sync
down, but it's hanging indefinitely (I've left it for 24 hours with out it completing.)
the the only music that appears on the phone are songs purchased from the iTunes Store. 95% of my collection are rips from my CDs.
thank you for any help!

Yeah it's pretty sad that $1000 phone they put out you such cheap memory It causes issues, I have iPhone 6+128 GB actually this is the second brand-new one they gave me because they keep affording it trying to act like that's not the issue because they're too stupid to know how to check what memory is in each one before they give it to me when I have told them multiple times my back up runs perfectly fine on two 5s phones and a 6 64GB of course running MLC memory.
I told them it's because just like the write ups say I have 809 apps but I have not even put all my music on the phone so I'm still running 50 to 60 gigs free and it crashes and reboots itself sometimes in multitasking and more often than it does that in between multitasking I get a black screen for 1 to 2 seconds in between apps and upon start up the Apple logo screen will flicker and do weird things, One of the genius idiots asked me if I could just delete some of my apps, really that's the answer to fix the phone the customer needs to limit the amount to apps they put on their phone, why the **** get a 128 gig if you can't put on anything you want to it guess they need to start selling them saying you can only put a limited number of apps on them, it's really is a **** joke, I have over $20,000 of Apple merchandise easily and always get the new phone every year but I'm starting to reconsider my decisions in the future because this company is starting to go downhill, The reason water not recalling the phones is because they're dealing with their top-of-the-line thousand dollar phones in this case and most people don't have over two or 300 apps so they're not having as many issues, so basically they have messed up phones they just don't know it in their hands and Apple is just too **** greedy to recall the phones, they'd rather sell customer spends that only work half ***.
Stuff like this will be the downfall of their company, all the people that stay with them because as long as you don't jailbreak their stuff it normally just works without issue will be soon jumping ship if stuff like this keeps up, because I can guarantee they got me thinking now.
not that I wanted to know or should I be expected to but I even offered for them to open up my brand-new phone and just replace the memory to MLC memory which is something I shouldn't have to do with a brand-new **** phone, they should just make one with the right memory and give me a new phone, actually just don't sell customers that buy the top-of-the-line phone from you trash ones in the first place that would be a great option.
what burns me up the most is when you talk to AppleCare and Genius Bar they try to act like the issue isn't there and they're unaware of it, they say that Apple hasn't come out with any information about it, yeah that's because they don't want to recall the trash.
Apple has became nothing better than your run-of-the-mill company, android is becoming just as good as they are sad to say this since I have been an Apple fan for so long but there is no excuse for BS like this they have been looking for options to fix my phone for a month now this is not the way you should treat loyal customers, I would've been better off keeping my 5S and in the future just switching to android.
it's pretty sad that the company has no idea how to check which memory is in their **** phone and even after I offered to let them just replace the memory in my new phone by opening up my brand-new phone to replace it they have no idea how to do that either, yeah Genius Bar sure, I think that should change the name to idiot bar and Apple don't care instead of Apple care.

WLC 5508 Internal DHCP server issues

Hi,
I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. I have tried to explain the setup and the problems below and would appreciate it if anyone can suggest a solution for the problems I am facing:
The setup is as follows:
- I have a WLC 5508 which has been configured with 4 SSIDs, out of which 2 are using Central Authentication and Switching.
- I have an LWAP connected to the WLC in HREAP mode.
- WLC is configured as the DHCP server for clients connecting to the SSID 'Guest'. For the rest, I am using external dhcp server.
- Only one scope for Guest Interface is setup on the WLC.
Problems:
1. As far as I know, for WLC to act as internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to SSID 'Internet' are
unable to get an ip address from the external dhcp server, if dhcp proxy is enabled on the WLC. If i disable the proxy, it all works fine.
2. DHCP does not release the ip addresses assigned to clients even after they are logged out.
3. If a machine which was earlier connected to 'Guest' SSID connects to the 'Internet' SSID, it requests the same ip it was assigned by the WLC which it was assigned under 'Guest', but gets tagged with the Vlan configured on the management interface.
************Output from the Controller********************
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS + LDPE
(Cisco Controller) >show interface summary
Interface Name                   Port Vlan Id IP Address         Type        Ap Mgr        Gu
est
guest                                        1    301      10.255.255.30    Dynamic   No              No
management                          1    100      172.17.1.30        Static          Yes            No
service-port                              N/A N/A      192.168.0.1       Static         No               No
virtual                                        N/A   N/A      10.0.0.1              Static         No               No
(Cisco Controller) >show wlan summary
Number of WLANs.................................. 4
WLAN ID WLAN Profile Name / SSID               Status    Interface Name
1        LAN                                    Enabled   management
2        Internet                               Enabled   management
3        Managment Assets          Enabled   management
4        Guest                                  Enabled   guest
(Cisco Controller) >show dhcp detailed guest
Scope: guest
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 10.255.255.31
Pool End......................................... 10.255.255.254
Network.......................................... 10.255.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 10.255.255.1 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 8.8.8.8 8.8.4.4 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... e8:b7:48:9b:84:20
IP Address....................................... 172.17.1.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.17.1.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 100
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 172.30.50.1
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show interface detailed guest
Interface Name................................... guest
MAC Address...................................... e8:b7:48:9b:84:24
IP Address....................................... 10.255.255.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.255.255.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 301
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. Unconfigured
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show dhcp leases
       MAC                IP         Lease Time Remaining
00:21:6a:9c:03:04    10.255.255.46    23 hours 52 minutes 42 seconds        <<<<<<< lease remains even when the client is disconnected.
*********Example of Client connected to the right Vlan with an ip address from the incorrect interface. *************
(Cisco Controller) >show client detail 00:21:6a:9c:03:04
Client MAC Address............................... 00:21:6a:9c:03:04
Client Username ................................. N/A
AP MAC Address................................... a0:cf:5b:00:49:c0
AP Name.......................................... mel
Client State..................................... Associated
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 2                 <<<<<<<<   'Internet' SSID
BSSID............................................ a0:cf:5b:00:49:ce
Connected For ................................... 319 secs
Channel.......................................... 36
IP Address....................................... 10.255.255.46      <<<<<<< IP address assigned from the 'Guest' Interface or dhcp scope on the WLC
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Status Code...................................... 0
Session Timeout.................................. 1800
Client CCX version............................... 4
Client E2E version............................... 1
QoS Level........................................ Silver
802.1P Priority Tag.............................. disabled
WMM Support...................................... Enabled
Power Save....................................... OFF
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ Yes
Policy Manager State............................. RUN
Policy Manager Rule Created...................... Yes
ACL Name......................................... none
ACL Applied Status............................... Unavailable
Policy Type...................................... N/A
Encryption Cipher................................ None
Management Frame Protection...................... No
EAP Type......................................... Unknown
H-REAP Data Switching............................ Central       <<<<<<<<<
H-REAP Authentication............................ Central       <<<<<<<<<<
Interface........................................ management
VLAN............................................. 100           <<<<<<<<<<< right Vlan
Quarantine VLAN.................................. 0
Access VLAN...................................... 100

Hi All,
I have a similar issue where Wireless clients are not receiving automatic addressing from an internal DHCP server. I have multiple interfaces configured on the WLC which are connected to separate VLANS. The manually specified DHCP primary server entry is the same on all interfaces. Some clients are able to authenticate and receive automatic IP configuration but some clients are failing the address assignment process. I have checked connectivity between the WLC and DHCP server, this is confirmed as working. When I carry out a "debug dhcp packet enable", I get the following outputs which seems as if the DHCP discover request from the client is skipped. Your thoughts and inputs on this are appreciated.
DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 116 (len 1) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: requested ip = 169.254.223.5
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 12 (len 13) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 55 (len 11) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 43 (len 2) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP options end, len 76, actual 68
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP Forwarding DHCP packet (332 octets) packet DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
Thanks,
Raj Sandhu

ChARM - Change Request status issue

We are currently testing our ChaRM processes. The biggest issue we have with the ChARM system is that transports associated with a Change Request are being imported into subsequent systems regardless of the status of the change request.
For instance...
If I have 5 transports (each having their own change request) in which all 5 have been released from development and have been imported into the quality system. It seems that from this point on, if 3 of the 5 change requests have their status changed to "testing completed", the production import should only import 3 of the 5 tranports. We assumed that if the other two did not have a status of testing completed, they would not be allowed to be imported into production. This causes an issue because all 5 tranports will move to quality and subsequently move to production regardless of the status of the change request. All 5 of these tranports are also on the same maintenance cycle.
Is this the way the system is supposed to work? If so, how do we utilize ChARM in a continuous maintenance production environment?
Your response is appreciated, Thank You for your help.

Thanks for the update.
So, I guess my next question would be if Change requests and their associated tranports can be moved from one maintenance cycle to another after they have been submitted and released from Dev. My concern is that in our normal production release environment has tranports that pass testing requirements at different times.
For example, Lets say that we release transports into our production system, or "set to go live" for a scheduled import on Tuesday and Thursdays at 5PM.
On Monday, I have 5 transports from 5 different Change Requests that I develop and release the DEV environment. On Tuesday, 3 of the 5 transports have been successfully tested and are cleared to go to Production, however 2 of the Change Requests did not have testing completed.
Is it possible to move the 2 transports to a subsequent maintenance cycle so that the first 3 that successfully passed testing can proceed to go live and import on Tuesday at 5PM?
My concern is that we do not always know upon development release when the Change Request and associated transport will be permitted to go to production.
Thanks much for your help.

DHCP Migration Issue - NW to OES11 SP1

I was able to migrate DHCP from NetWare 6.5 to OES 11 SP1. I can now see the new OES 11 SP1 DHCP server via the DNS/DHCP Java Console. However, I am unable to start/stop the DHCP server from the console. I can start/stop dhcp from the OES 11 SP1 server. But, the correct status is not visible via the Java Console.
I need to export/import dhcp config to configure option 43 for a WiFi configuration. Since Java Console sees DHCP as always down, I cannot export dhcp database to make corrections. Any ideas why Java Console does not see the status of DHCP or how to get this fixed? Thank you for any info.

kkumara,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

EA6350 DHCP/DNS Issues

Just got this router, overall not bad, but a couple of serious problems. When using the built in DHCP there's no way to force serving only the static DNS addresses. I have been using OpenDNS as part of a multi-layer parental control solution... but because this router always serves itself up as a DNS proxy, and bypasses the static DNS configuration, I no longer get the behavior I was able to get with my old wrt54g. It would be great if there were options to :1) Exclude DNS Proxy from the served DHCP list of DNS addresses2) Disable DNS Proxy Somewhat less serious, if you disable the built in DHCP, there's no way to turn it back on, short of resetting the router to factory default settings. All the DHCP configuration is blanked when turned off, and there's no way to restore the configuration to allow it to be re-enabled. I hope to see these issues fixed in the next firmware update!

Thanks.Believe it or not, have configured only 1 open DNS server, also tried disabling IPv6 L3 interfaces on WAN.Neither made any difference. Internet Connection (IPv4) Connection Type:Automatic Configuration - DHCPLogin Status: ConnectDisconnectInternet Address:*************************Subnet Mask:*************************Default Gateway:*************************DNS1:75.75.75.75DNS2:75.75.76.76DNS3: MTU:AutoDHCP Lease Time:5569 Minutes Local Network DHCP Server Local MAC Address:48:F8:B3:BD:21:0FIPv4 Address:10.230.84.229IPv4 Subnet Mask:255.255.255.0IPv6 Link-Local Address:fe80:0000:0000:0000:4af8:b3ff:febd:210fPrefix Address: DHCP Server:EnabledStart IP Address:10.230.84.100End IP Address:10.230.84.149Client lease time:10080 MinutesStatic DNS 1:208.67.222.222Static DNS 2: Static DNS 3: WINS:

Ip dhcp snooping issue

   Hi all,
I am having trouble getting the dhcp snooping to work on a stacked 3750 when a rogue DHCP server is plugged in to the network. I have configured dhcp snooping on one of our user switches with the following commands.
ip dhcp snooping
ip dhcp snooping vlan 11
no ip dhcp snooping information option
int range fa1/0/1 - 48
ip dhcp snooping limit rate 100
VLAN Name                             Status    Ports
11   JKT_Net_DHCP_1
interface FastEthernet1/0/43
description DHCP Subnet 1
switchport access vlan 11
switchport mode access
switchport port-security maximum 3
switchport port-security aging time 1440
switchport port-security violation restrict
switchport port-security aging type inactivity
no logging event link-status
no snmp trap link-status
spanning-tree portfast
spanning-tree bpduguard enable
ip dhcp snooping limit rate 100
end
The configuration works in ther fact that users are still getting their IP address info from the DHCP server and i can see all the dhcp snooping bindings on the switch. But I'm having issues where when a rogue dhcp device is plugged in to one of the user ports i.e fa1/0/43 on the user subnet, and do an ipconfig /release /renew on a machine on the same VLAN, i am still getting a DHCPOFFER from the rogue device and the machine ends up with the wrong IP address.
Currrently the real DHCP server sits off a network behind the firewall, with a layer 3 link (running OSPF) between the user switch to the distribution switch. I have enabled the dhcp snooping on the link from the distribution switch to the real DHCP server (shown below).
DHCP snooping trusted interface
interface GigabitEthernet1/0/9
description JKTADC01 - LAC 1
switchport access vlan 21
switchport mode access
no snmp trap link-status
ip dhcp snooping trust
end
I have also attached a network diagram of the network setup.
I would like to stop the rogue server from being able to give out ip addresses.
Can someone shed some light on this topic please?
Kind regards,
Philip

Pawan,
Based on the error messages it looks like you have a mis-configuration. Looks like
one of the trunks/ports does not have DHCP trust configured on it. Can you
track mac address 34dc.fde5.2c40 to what port it's connected to and verify
that it has DHCP trust enabled?.
Haihua

E3000 DHCP server issues?

I recently purchased an E3000 and immediately upgraded to the latest firmware version,1.0.03 build 2 Sep 7, 2010 . I've noticed a few issues with the DHCP server.
First, some entries appear to drop out of the DHCP client table before their DHCP lease expires. This has happened with several Windows 7 clients and with a pair of Linksys WRT54GS routers that obtain their IP addresses from the DHCP server in the E3000.
Second, I have two Netgear GS108Tv2 switches attached to the E3000. When these switches are running firmware version 5.0.0.8 they can obtain IP addresses from the E3000, but I can't access them using a web server. When these switches are running firmware version 5.0.1.11 they fail to obtain IP addresses from the E3000. I suspect the DHCP client in these two devices has a problem and I have reported this behavior to Netgear, but I believe the DHCP server in the E3000 may also be part of the problem. Why? Because I connected the switches to one of the WRT54GS routers mentioned above and they were able to obtain IP addresses from the DHCP server in the WRT54GS, which is a model 7.0 running firmware versionv7.50.8 build 001, Oct. 5, 2009 .
Finally, a question regarding DHCP reservations with the E3000. When creating a DHCP reservation, does the assigned IP address have to come from the scope of addresses assigned to the DHCP server? For example, I have configured the start IP address for the DHCP server in the E3000 to be 192.168.1.64 and the maximum number of users to be 64. However, I have created reservations for IP addresses 192.168.1.10 and 192.168.1.20 for the two WRT54GS routers mentioned above. I have also created a reservation for two clients within the assigned range as well. All assignments appear to be working correctly, but I would like to confirm that both approaches are kosher.
Thanks in advance.

On 04/27/2011, I opened a case with LinkSys/Cisco support concerning lost DHCP Client Table entries on both my new E3000 V1.0 router (running firmware upgrade 1.0.4) and it's WRT54G V8.0 predecessor. After several days of using WireShark capture traces, I was able to determine the entries were being dropped when an application on one of my four WinXP/SP3 systems sends a "DHCP Inform" packet to the router. The E3000 (and WRT54G V8.0) responds with correct IP Lease information but deletes the client's entry from it's DHCP Client Table in the process. My problem was supposedly referred to the support team in Irvine, CA about a week ago, after I discovered what was causing the table drop, but I have not heard from the Irvine team yet. I will follow up on Monday for a status update.
Oddly enough, the "triggering application" is MicroSoft's AutoUpdate process. Once I configured MS AutoUpdate from "Check but do not download updates" to "Turn Off Automatic Updates", the AutoUpdate process ceased generating "DHCP Inform" packets and my system has not been deleted from the router's DHCP Client Table since then. I have a total of four WinXP/SP3 systems behind the E3000, one is direct connected to an Ethernet port on the router and the other three are connected to the EG008W switch which is connected to a port on the E3000. One of those three systems is occasionally connected wirelessly to the E3000 for long periods with no connection problems. My NVidia nForce 730i tower is one of the systems on the EG008W switch and is the one that was being dropped from the DHCP Client Table (whether it was on the switch or direct connected to the E3000). The system that is always direct connected to the E3000 is an identical NVidia nForce 730i tower and has never been dropped from the DHCP Client Table.
Please note that the client that was being dropped from the router's DHCP Client Table did NOT lose access to the Internet. Repeated checks using Command Prompt "ipconfig /all" indicated the client still had it's IP Address lease. Issuing a "ipconfig /renew" command resulted in the client being shown in the router's DHCP Client Table until the next "DHCP Inform" packet was sent and responded to by the E3000 (and WRT54G) router.
Concerning switch connection issues with the E3000 and some newer WRT54G wireless routers, I had a similar issue in March 2011 with a LinkSys SD2005 Gb switch newly connected to a WRT54G V8 and later my new E3000 wireless routers. The SD2005 had no issues connecting to an older WRT54G V6 router. A call to the Support line transferred me to the Cisco Engineering support team which confirmed connection compatibility issues with older switches and new LinkSys Wireless routers due to firmware changes in switch connection support. I replaced my SD2005 with an EG008W Gb switch and have no problems with it on either the E3000 or the WRT54G V8 backup router.
Concerning the randomly assigned dynamic IP addresses from the E3000, from my perspective this appears to have started after the WRT54G V8.0 Wireless-G router firmware. Not only does the E3000 definitely prefer the upper 10 IP addresses of the dynamic range but it ignores a client's request to renew a previously assigned IP address during the client's "half-life" IP Lease renewal process and usually assigns a different IP address. This may part of undocumented identity protection policies. I have chosen to use the E3000's DHCP Reservation function for my home based systems, both wired and wireless. I do not use the DHCP reservation function for the new E3000 "Guest" wireless network. Please note my use of DHCP reservation went into effect about halfway through my DHCP Client Table diagnosis process and had no affect on the issue except that I had reliable client IP addresses to use in ShareWare capture filters.
I apologize for the long dissertation, but after 40+ years in various mainframe/open-system positions, I have a well known penchant for documenting problems for future reference.

Purchase order status issue

Hi Everyone
I am having an issue with the status of Purchase order. When the Purchase order has single account assignment, everything is fine. But when I create a purchase order with multiple account assignment, the first line item is correct but when I ad second line, the still to deliver quantity gets added correctly but the amounts only reflect the recent item and not the previous one.
For example:
Item 10            Quantity 10
Item 20            Quantity 10         CC xxxx         GL account 666666
                                                   CC yyyy         GL account 666666
Status:    Ordered        20              200
                Still to deliver 20             100
Please help me with this issue.
Thanks,
Shalu
Edited by: Shalu G on Feb 9, 2010 12:07 AM

Resolved myself

Exchange 2010 all mail clients with internal cached and internal non-cached mode users having connection status issues, login prompt -- external is fine either way

Hello,
I'm seeing an issue that started this past Monday with no recent change to our environment.
External Outlook Anywhere users and Mobile users, OWA users are unaffected.
Internal Users are affected when using Outlook of any version, 2010 or 2013.
-Internal Users normally log into their workstation with their ad credentials, domain joined machines. Outlook opens without credentials prompting ideally.
1 . Using Cached Mode:
a. Login Prompts, slowness - Since Monday, users are getting prompted to login. The prompt goes away after logging in at startup. It is also causing high CPU
on the workstations.
b. Free/Busy, Out of Office doesn't work. I can, however complete auto-setup for a new user, so autodiscover is not completely down for internal users.
c. Checking Connection Status shows connecting status on highlighted entry below without ever establishing connection (just goes away).
The outlook icon in the system tray says "Outlook is requesting data from the server":
2. Using Non-cached mode
a. No Login Prompt at startup, business as usual
b. Free/Busy, Out of Office works fine. Autodiscover is fine.
c. Checking Connection Status shows normal except, it has "casarray URL, then status is referral" it seams to flicker this constantly then go away intermittently.
d. Main issue in non-cached mode is, sometimes a user will log into windows, open outlook and it will not open and says "server is unavailable. Retry, work offline, or cancel" I can try re-opening, same message.
Only after logging out of windows, logging back in, I can get back into outlook. This is not every time, or consistent with specific users, but random.
3. Lync Pop up for credentials often, though entering the password.
URLs are correct. Autodiscover, EWS, etc.
Already tried bypassing our loadmaster load balancer with host files on clients. same issue regardless of casarray node.
Not sure what is going on.
Josh

You have a hybrid configuration with Office 365, right? You didn't provide this valuable piece of information.
In Exchange Online PowerShell run this command:
Get-OrganizationConfig | FL PublicFoldersEnabled
If the value is "Remote" then users with Exchange Online mailboxes are looking to on-premises public folders. Be sure that you have legacy pubic folder interoperability properly configured.
http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Intel4965 | Association/DHCP | Status Issue

Similar Messages

Maybe you are looking for