NAC issue with DHCP

There are a few computers in the building that when they start i have to do a repair in the connection. If i put those same computers in the admin Vlan(doesn't goes through NAC) i dont need to do the repair. I think something is blocking in the unauthenticated role. But the rare thing is that i'm allowing the DHCP and Active directory servers on the unauthenticated role.

The "Enable VLAN Pruning" option is enabled by default for CAS Virtual Gateways. Make sure that "Enable VLAN Pruning" is turned off when "VLAN Mapping" is disabled. Turning the "Enable VLAN Pruning" option on when the "VLAN Mapping" option is disabled can cause the CAS to discard all VLAN packets from passing through in either direction.

Similar Messages

[Solved] Several installs and issues with DHCP issue every time.

Edited: more concise information!
Hi folks,
I was using Arch fine for months but decided to reinstall it fresh at the new year, but since then I have been plagued by connection issues. I install Arch and follow many of the tips found in these Wikis to set it up how I like then install preload and readahead.
Post-Installation Tips
http://wiki.archlinux.org/index.php/Pos … ation_Tips
- LCD filtered fonts
- Disable IPv6 (I use Chorus/NTL and they have a tip for improving Firefox that disables IPv6, so I think that this is not to blame)
Laptop
http://wiki.archlinux.org/index.php/Laptop
- Battery state monitoring utilities (acpi)
- Laptop-mode-toold
- Powernowd
Maximising Performance
http://wiki.archlinux.org/index.php/Max … erformance
- Swapiness
- Mount /tmp to RAM
My internet connection works fine, even when rebooting, but later I turn on my computer and WICD or networkmanager fails on "obtaining IP address. I really think that there is something in one of these tips that is causing this problem, but I am at a loss as to what. Like I say, I was using it happily for many months before these current issues. The only thing I did differently was systematically set up my computer with all the tips detailed above, where as before, I collected these tips over a period of time and did not do them all straight after installation. I have tried rolling back the changes and this has not fixed the issue.
I have had this issue over many reinstalls, using networkmanager or WICD and each time I was hoping that I was doing something wrong. I have an Ubuntu and work Windows laptop that both work fine, so I don.t think it is anything to do with the connection itself.
I am not sure what information you would need so I thought I would post both of these files. If you would like anything else, give me a shout and i can post it.
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_GB.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Dublin"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(acpi-cpufreq vboxdrv coretemp)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="laptop"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="dhcp"
eth0="dhcp"
INTERFACES=(eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(preload syslog-ng hal wicd @powernowd @laptop-mode @fam @alsa @sensors @readahead-list)
/etc/resolv.conf
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
Thanks for your help,
Scott
Last edited by ScottArch (2010-02-14 12:30:25)

Hey Scott!
I don't know if it is helpful in any way but I have a similar problem with my desktop PC.
I have two ethernet controllers installed and somtimes I had a Ip address assigned and sometimes I didn't.
One which is connected to the router and a 2nd one I use sporadically to connect additional computers.
The dhcpcd would fail to load even if I followed steps suggested from other forum members.
My temporary fix was to run:
# dhcpcd
manually.
If this helps you might consider adding "dhcpcd" at the end of
/etc/rc.d/network
I know it's not really a fix but it helps me to get a working connection whoch otherwise would fail - or work if lucky but i don't like lucky with network/internet ^^

FlexConnect AP Deployment- Clients having issues with DHCP

I have 7 2602I access points deployed and operating in FlexConnect. We are doing both local switching and local authentication. These AP's are in a FlexConnect Group with local Radius server defined as the primary server in the Flex Group. This has been working for a few days. The vlan these users are getting DHCP is local and there is a local DHCP server. There is also a backup DHCP server at the central site.
We are beginning to get reports of users having problems connecitng to wireless. Authentications asre successful, but when I look at the WLC, I notice they are not getting an IP address. They either show 0.0.0.0, or the default address 169.254.12.2. Some are connecting, and some do not. This issue is very intermittent. I will also add, this location does have periods of high latency, hence the reason we are doing local switching/local auth. This client eventually got an IP address, but it took a while.
We never had any issues unitl we deployed in Flex mode. I could switch these Ap's back to local mode(central switch/central auth) and this problem would never occur. Any ideas? Thanks.

I agree that in local auth mode the WLC does not learn as much info, but if you check learn IP address under the WLAN it will learn it and can be seen from monitor clients.
Although authentications are successful, I have not ruled out some sort of local auth issue.
One other thing to note, we got a debug client and the first dhcp request went to the local dhcp server, then a request to the backup dhcp at HQ. however the dhcp request was fulfilled by the local dhcp server. The local server appears to be working correctly, and there are plenty of addresses available.
Sent from Cisco Technical Support iPhone App

PXE boot issue with DHCP and SCCM server on different subnets

I'm working with a client on the operating system deployment module of SCCM.
Their network configuration currently has a single large subnet for client
computers with a DHCP server on the same subnet. The SCCM subnet is
configured on a seperate subnet with no DHCP server on the subnet. We want to
configure client computers to be able to boot using the PXE client to deploy
OS images to the machines but can not get PXE-boot to work correctly.
Also, the client does not want to make changes to their network
infrastructure routers or switches to remedy this problem. Are there settings
on the DHCP or SCCM servers we can implement to make this work? If so, what
needs to be installed or configured on each server. We currently already have
WDS installed on the SCCM server and the SCCM server is configured as a PXE
Service Point within SCCM. Both WDS and the PXE Service Point seem to be working fine.
Any help would be appreciated.
Thanks,
Gary

I am Brazilian,
sorry for wrong english
My DHCP is on linux,
in my own structure VLANS
The system center is on the network
10.0.4.0/24
The machines on the network 10.0.5.0/24
The problem is that the machines that
are not on the same network system center
can not boot
I tried configuring / etc/dhcp3/dhcpd.conf
follows
option vendor-class-identifier "PXEClient";
option bootfile-name "\
\ SMSBOOT \ \ x86 \
\ wdsnbp.com";
option tftp-server-name
"10.0.4.101"; ---->
IP server
But it did not work, anyone know
how to configure?

Anyone else having issues with DHCP settings resetting?

I think this is a glitch with OS X Server 3.0.1... I have the server handle DNS and DHCP instead of the router, and after a reboot, DHCP settings revert to off and the default Ethernet IP pool.
I tried the usual, even formatted the hard drive and installed from scratch. I also deleted Server.app and /Library/Server, then redownloaded Server from the App Store. I also verified and repaired permissions.

Bob-
If you are using the old iPad 1 dock with an iPad 2, there is a problem due to the different shape of the new iPad's bottom. Some have suggested folding some paper to stuff between the back of the iPad and the dock, to help make better connection.
Fred

10g install on (DHCP based) rhel5 -issue with DHCP

Hello, I am trying to install Oracle 10.2 on my laptop (RHEL5) which is DHCP configured.
In Windows system, it can be resolved by Installing a Loopback Adapter. How to resolve this in RHEL?
Thanks in advance,
Lily

Hand edit .ora files and replace IP address with machine name or 127.0.0.1.
This is also the easiest solution for Windows too.

ISSUE With my WRT600N Wireless Router --

Hello, I am having trouble with my Wireless Router. It is the WRT600N model Linksys Router and the issue I am specifically having is my wireless access. I have several devices which access wirelessly and am starting to have more and more issues of late, not sure why...?
I was wondering how to configure each device accessing my wireless net individually as I have Network MAgic asnd have seen a couple of the items on my network with the same ip addresses. I would like to assign a number to each device and see if that eliminates the issues I have been experiencing..?
I have looked through these question pages and have not found the answer I was looking for so I hope this has not been asked before. I also saw a post that kind of caught my interest and it was regarding using two WRT600N's routers together for better range etc. I have an issue with raqnge on my system and have an old WRT54 Router and would like to know if I could do the same thing with this and incorporate this router into my system as a wireless access point (WAP) only. If this is possible, what would the steps be to accomplish this...
My main issue I chose to writer about here was recently experienced when I got an Ipad and my Ipad has issues remaining connected to my WRT600N Router and I checked my network program and noticed that it was assigned the samw IP address as one of my boys X-Boxes. I believe currently we have approximately 9-11 devices that periodically connect wirelessly to my network. Some devices are PSP's and only occassionally connect and I have NEVER seen all the devcices connect at the same time. I believe the max at once would be approximately 5-6 devices. Is this too many at once...? Is the router overloaded with the amount of devices I have connected...?
Please let me know what you would recommend for my situation,
Darius Taylor
[email protected]

2 wireless routers can not communicate wirelessly with each other.
You need to connect cable between 2 routers and use the second wireless router as access point.
Follow this link to connect Linksys router to another router.
Some of your devices are getting same IP address. This might be the issue with DHCP server of the router. You can try DHCP reservation on the router so that each device will get unique IP address.

Configuration Issue with my Cisco 871 Router

Hi all,
I am a newbie to the Cisco IOS.
I got a Cisco 871 Router that I'd like to use for internet connection. My LAN network is 192.168.1.0/24 and the ISP has assigned us the IP 41.212.79.108/24 and gateway 41.212.79.1.
With my current configuration, I can hit the router - 192.168.1.1 - and it's WAN port - 41.212.79.108 - but not the gateway.
Below is my current config:
Hoggers#show config
Using 4414 out of 131072 bytes
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Hoggers
boot-start-marker
boot-end-marker
logging buffered 51200 warnings
enable secret 5 **********************.
no aaa new-model
crypto pki trustpoint TP-self-signed-568493463
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-568493463
revocation-check none
rsakeypair TP-self-signed-568493463
crypto pki certificate chain TP-self-signed-568493463
certificate self-signed 01 nvram:IOS-Self-Sig#7.cer
dot11 syslog
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 10.10.10.1
ip dhcp excluded-address 192.168.1.1
ip dhcp excluded-address 192.168.1.2
ip dhcp excluded-address 192.168.1.3
ip dhcp excluded-address 192.168.1.4
ip dhcp excluded-address 192.168.1.5
ip dhcp excluded-address 192.168.1.6
ip dhcp excluded-address 192.168.1.7
ip dhcp excluded-address 192.168.1.8
ip dhcp excluded-address 192.168.1.9
ip dhcp excluded-address 192.168.1.10
ip dhcp excluded-address 192.168.1.100
ip dhcp excluded-address 192.168.1.90
ip dhcp pool ccp-pool
   import all
   network 10.10.10.0 255.255.255.248
   default-router 10.10.10.1
   lease 0 2
ip dhcp pool LANPOOL
   network 192.168.1.0 255.255.255.0
   default-router 192.168.1.1
   dns-server 41.212.3.2 41.212.3.253
ip domain name yourdomain.com
ip name-server 41.212.3.2
ip name-server 41.212.3.253
archive
log config
hidekeys
interface FastEthernet0
interface FastEthernet1
interface FastEthernet2
interface FastEthernet3
interface FastEthernet4
description Wan to Outside World
ip address 41.212.79.108 255.255.255.0
duplex auto
speed auto
interface Vlan1
description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$
ip address 192.168.1.1 255.255.255.0
ip tcp adjust-mss 1452
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 41.212.79.1
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip dns server
ip nat inside source static tcp 192.168.1.31 80 interface FastEthernet4 80
access-list 23 permit 10.10.10.0 0.0.0.7
no cdp run
control-plane
scheduler max-task-time 5000
end
I'll appreciate any light you can shed on what am missing.

2 wireless routers can not communicate wirelessly with each other.
You need to connect cable between 2 routers and use the second wireless router as access point.
Follow this link to connect Linksys router to another router.
Some of your devices are getting same IP address. This might be the issue with DHCP server of the router. You can try DHCP reservation on the router so that each device will get unique IP address.

Time Capsule download issues with Windows 7

Hello together
My problem is as follows: upload to Time Capsule with two PCs running on Windows 7 (both 32 and 64 bit) and a Mac Book Pro is working without any problems occuring. TC and the two PCs are in the same workgroup and PCs are connected via WIFI in private mode.
Download from TC to Mac Book Pro works without problems. But in contrast to that, when downloading with the two Windows7-based PCs the connecting is breaking off all the time and the message "Network error" will be displayed. In order to get a new connection to TC the power plug must be unplugged and replugged again. Do you have any advice what to do? Thanks very much in advance.

Are you using SMB compatible names for the TC and wireless.. short, no spaces.. pure alphanumeric.. If not do so?
I also recommend using fixed channels and maybe fixed mode. Lock up as much as possible as the PC does not deal as well as the Mac with the auto band, channel and mode switches.
I am not sure what you mean by this..
PCs are connected via WIFI in private mode.
Please explain a bit more.
Windows wireless drivers are often terrible.. many people have fixed issues by using a more recent driver direct from the wireless card manufacturer.. this is important.. not windows default driver,, not computer manufacturer supplied one.. eg intel card then get latest intel driver from intel.
Are you running bonjour for windows on the PC's??
Try using static IP address which also might help.. windows did have issues with dhcp in the past.

Issues with an LDAP server configured using DHCP instead of static.

Can anyone tell me if there is a known issue using a DHCP address instead of a static IP address to build a 10.4 MAC server that will is a LDAP master?
I have an LDAP master that is running 10.4 that has user account issues. Random users will suddenly not be able to authenticate against the server. I have been told this is because the server was originally built using a DHCP address and then migrated to a static IP. Being a UNIX geek this does not seem to make a lot of sense to me but I am new to MAC..... So?

It absolutely could be the cause of the issue. Open Directory uses Kerberos (among other things) for authentication. Kerberos is VERY VERY VERY particular about DNS... and if your OD master changed the IP address, it could cause these problems. I wouldn't expect that it would ever work, but perhaps some days the IP is the same as it was during initial setup.
Do a 'sudo changeip -checkhostname' from the server and see if it says everything is okay. If not, you definitely have things you need to fix. Frankly, with DHCP on the server you are 100% guaranteed to have problems at some point.

10.5 DHCP issues with Wireless - self assigned IPs?

We're having an issue with Mac OSX 10.5.4 clients, running the latest software updates, not getting an IP address via DHCP on our wireless network.
We're using Cisco APs, with multiple VLANs & SSIDs. They authenticate, but get automatic self-assigned IP addresses. None of our PC clients are experiencing this issue, nor older 10.4.x OSX clients. This looks like a bug, from what I was able to discover:
http://forums.macrumors.com/showthread.php?t=384947
Is Apple aware of this, and/or working on a fix? I've seen many issues over the last year or so with Airport clients and wireless connectivity..

This is a "user to user" help forum that is designed as a self-help system, independent of Apple's Technical Support system. No one here can say what Apple knows or is doing about a specific issue (pure speculation is discouraged). We share experience and suggest possible solutions or workarounds.
One way to ensure that your issue is brought to Apple's attention is to use their feedback form for OSX - http://www.apple.com/feedback/macosx.html
Since the link you posted is from late last year, there have been many updates to Leopard. Some of the updates mention network reliability. Even though Apple has stated that the Pram chips don't control network connections, I have had some luck by Zapping The Pram - http://support.apple.com/kb/HT1379 - Remember to check your System Prefs for things like date/time settings after you Zap.

EA3500 issue, possibily with DHCP lease renewal

I have a new EA3500 router that's working great for a variety of devices* except a Windows7 laptop. 24 hours after establishing a connection, the laptop loses connectivity and it's very difficult to re-establish a connection. Usually I have to reboot the router, but 24 hours later the problem returns and Windows is unable to connect.
My router settings include DHCP client lease time set to 1440 minutes (24 hours), so I thought the problem might have something to do with DHCP lease renewal. To test this theory, on Saturday night I did ipconfig/release and ipconfig/renew and established connectivity from the laptop.
Sunday morning I spoke with Linksys support and changed several settings per their recommendation:
Network mode mixed (I had it on N-only for some reason)
Assigned different SSIDs to the 2.4GHz band and 5 GHz band
2.4 GHz band channel is 20MHz only, using channel 9
5 GHz band channel is 40 MHz only, using channel 161
I also power cycled the router.
Everything worked fine until Sunday night, 24 hours after the release/renew, when I lost connectivity. I am not sure what to try next and whether the problem lies with the router or the laptop.
* other devices include Macbook, 3 iPhones, iPad, 2 Kindles, printer, DVD player

If you are only having this problem with the laptop then there is a possibility that the problem might really be with the laptop. What you can do on the router though is to add the laptop on DHCP reservation. In that way, even if the router’s DHCP Lease time will stop, the laptop will still be connected since the laptop will now have a fix ip address.

Windows 7 Pro DNS issue with static IP

0
down vote
favorite
I have been unable to solve a DNS problem I am having as follows:
I have a Windows 7 Professional (64 bit) computer running VirtualBox with a couple of Windows XP guests (not sure if this bit is relevant). After heavy file copying/transfer on both of the Windows XP machines, both the guest machines AND the host loose anything
DNS related, so I cannot call anything by name, but by direct IP works fine. The only resolution is to reboot the (host) machine and it will then work OK for a while until it happens again. The only trigger to make it seem to happen quicker is to re-initiate
the heavy file transfer and this then causes the DNS resolution to stop working again.
The machine has a fixed IP address, so it isn't related to DHCP.
I've tried the machine connected wired and wireless, no difference.
The IP settings are manual and I have tried giving it the DNS settings of the router (normal settings) and I have also tried giving it Google's DNS servers (8.8.8.8 & 8.8.4.4). No difference.
It seems to happen (sooner) during heavy traffic.
Other Windows 7 machines in the network work fine (though they are Home version, not Pro).
ONLY DNS fails, direct IP works OK.
Reboot seems only solution at the moment.
I am now lost as to what to try to resolve this issue, I do not really want to reload Windows 7 as it is a relatively new install... I have read about issues with wired connections on my router (BT Home Hub 2.0) so tried a wireless connection, still the
same.
Here is my ipconfig /all (it shows the BT Home Hub router DNS settings, but it also failed with Google's 8.8.8.8 and 8.8.4.4 entered here and also with the routers 192.168.1.254 (default).
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\G>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : e1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 30-85-A9-AD-07-81
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::59f:484a:827f:42ba%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.87(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 238060969
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
DNS Servers . . . . . . . . . . . : 217.32.171.21
213.120.234.30
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-28-56
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8d2d:7418:381b:8dc0%15(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 336068647
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{486D4DCC-9CB7-417E-A796-596E0E6B1D54}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{67455999-75A5-436E-9EAC-12B093363132}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\G>
Any ideas where to look, or what other info to provide for any assistance?
Many thanks in advance.

Hi,
This has just happened again, here is the content of the netstat results as requested...
If I kill the VirtualBox virtual machines, it starts working again. It is as if there are no ports left, but I am not occupying that many? Surely Windows 7 can cope with this?
I feel I am missing something important, but cannot put my finger on it...
Further below, I have re-run the netstat command AFTER I have closed the VirtualBox machines and the system works OK.
netstat results DURING ISSUE:
Active Connections
Proto Local Address          Foreign Address        State           PID
TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1444
[FileZilla Server.exe]
TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1692
[MESMTPC.EXE]
TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    0.0.0.0:110            0.0.0.0:0              LISTENING       1660
[MEPOPS.EXE]
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       752
RpcSs
[svchost.exe]
TCP    0.0.0.0:143            0.0.0.0:0              LISTENING       1524
[MEIMAPS.exe]
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    0.0.0.0:1221           0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:2199           0.0.0.0:0              LISTENING       4820
[VirtualBox.exe]
TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING       1756
[mysqld.exe]
TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       1104
CryptSvc
[svchost.exe]
TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
[WinVNC.exe]
TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
[WinVNC.exe]
TCP    0.0.0.0:8300           0.0.0.0:0              LISTENING       3464
[sc_serv.exe]
TCP    0.0.0.0:8301           0.0.0.0:0              LISTENING       3464
[sc_serv.exe]
TCP    0.0.0.0:8360           0.0.0.0:0              LISTENING       3080
[sc_serv.exe]
TCP    0.0.0.0:8361           0.0.0.0:0              LISTENING       3080
[sc_serv.exe]
TCP    0.0.0.0:9022           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:9023           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:9080           0.0.0.0:0              LISTENING       4804
[VirtualBox.exe]
TCP    0.0.0.0:10001          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10002          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10003          0.0.0.0:0              LISTENING       4828
[VirtualBox.exe]
TCP    0.0.0.0:10011          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:10012          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:10013          0.0.0.0:0              LISTENING       4780
[VirtualBox.exe]
TCP    0.0.0.0:25566          0.0.0.0:0              LISTENING       3648
[TerrariaServer.exe]
TCP    0.0.0.0:30001          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30002          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30003          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30004          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30005          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30006          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30007          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30020          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30021          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30039          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30080          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30081          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30082          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30083          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30084          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30085          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30086          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30087          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30088          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30089          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30090          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30091          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30092          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30093          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30094          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30095          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30096          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30097          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30098          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30099          0.0.0.0:0              LISTENING       4788
[VirtualBox.exe]
TCP    0.0.0.0:30101          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30102          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30103          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30104          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30105          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30106          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30107          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30108          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30109          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30110          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30111          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30112          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30113          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30114          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30115          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30116          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30117          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30118          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30119          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30120          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30121          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30139          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30180          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30181          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30182          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30183          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30184          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30185          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30186          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30187          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30188          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30189          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30190          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30191          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30192          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30193          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30194          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30195          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30196          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30197          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30198          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30199          0.0.0.0:0              LISTENING       4812
[VirtualBox.exe]
TCP    0.0.0.0:30201          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:30239          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:33306          0.0.0.0:0              LISTENING       4796
[VirtualBox.exe]
TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       440
[wininit.exe]
TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       880
eventlog
[svchost.exe]
TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       1000
Schedule
[svchost.exe]
TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       508
[lsass.exe]
TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING       500
[services.exe]
TCP    0.0.0.0:49158          0.0.0.0:0              LISTENING       3048
PolicyAgent
[svchost.exe]
TCP    127.0.0.1:8361         127.0.0.1:49364        ESTABLISHED     3080
[sc_serv.exe]
TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING       1444
[FileZilla Server.exe]
TCP    127.0.0.1:14147        127.0.0.1:49162        ESTABLISHED     1444
[FileZilla Server.exe]
TCP    127.0.0.1:49162        127.0.0.1:14147        ESTABLISHED     3156
[FileZilla Server Interface.exe]
TCP    127.0.0.1:49212        127.0.0.1:49213        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49213        127.0.0.1:49212        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49214        127.0.0.1:49215        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49215        127.0.0.1:49214        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49216        127.0.0.1:49217        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49217        127.0.0.1:49216        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49218        127.0.0.1:49219        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49219        127.0.0.1:49218        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49220        127.0.0.1:49221        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49221        127.0.0.1:49220        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49222        127.0.0.1:49223        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49223        127.0.0.1:49222        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49224        127.0.0.1:49225        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49225        127.0.0.1:49224        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49226        127.0.0.1:49227        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49227        127.0.0.1:49226        ESTABLISHED     4288
[java.exe]
TCP    127.0.0.1:49364        127.0.0.1:8361         ESTABLISHED     3100
[Instore_Radioboss.exe]
TCP    192.168.1.87:139       0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    192.168.1.87:3389      217.156.134.12:22971   ESTABLISHED     1104
CryptSvc
[svchost.exe]
TCP    192.168.1.87:8360      81.148.248.221:1026    ESTABLISHED     3080
[sc_serv.exe]
TCP    192.168.1.87:25565     0.0.0.0:0              LISTENING       4288
[java.exe]
TCP    192.168.1.87:50644     37.139.0.151:8233      ESTABLISHED     4796
[VirtualBox.exe]
TCP    192.168.1.87:51019     81.27.96.46:21         TIME_WAIT       0
TCP    192.168.1.87:53126     192.168.1.86:445       ESTABLISHED     4
Can not obtain ownership information
TCP    192.168.1.87:60462     192.168.1.86:445       CLOSE_WAIT      4
Can not obtain ownership information
TCP    192.168.1.87:65029     37.139.0.151:8231      ESTABLISHED     4796
[VirtualBox.exe]
TCP    192.168.56.1:139       0.0.0.0:0              LISTENING       4
Can not obtain ownership information
TCP    [::]:21                [::]:0                 LISTENING
1444
[FileZilla Server.exe]
TCP    [::]:25                [::]:0                 LISTENING
1692
[MESMTPC.EXE]
TCP    [::]:80                [::]:0                 LISTENING
4
Can not obtain ownership information
TCP    [::]:135               [::]:0                 LISTENING
752
RpcSs
[svchost.exe]
TCP    [::]:445               [::]:0                 LISTENING
4
Can not obtain ownership information
TCP    [::]:3306              [::]:0                 LISTENING
1756
[mysqld.exe]
TCP    [::]:3389              [::]:0                 LISTENING
1104
CryptSvc
[svchost.exe]
TCP    [::]:30239             [::]:0                 LISTENING
4796
[VirtualBox.exe]
TCP    [::]:49152             [::]:0                 LISTENING
440
[wininit.exe]
TCP    [::]:49153             [::]:0                 LISTENING
880
eventlog
[svchost.exe]
TCP    [::]:49154             [::]:0                 LISTENING
1000
Schedule
[svchost.exe]
TCP    [::]:49156             [::]:0                 LISTENING
508
[lsass.exe]
TCP    [::]:49157             [::]:0                 LISTENING
500
[services.exe]
TCP    [::]:49158             [::]:0                 LISTENING
3048
PolicyAgent
[svchost.exe]
TCP    [::1]:14147            [::]:0                 LISTENING       1444
[FileZilla Server.exe]
UDP    0.0.0.0:123            *:*
964
W32Time
[svchost.exe]
UDP    0.0.0.0:500            *:*
1000
IKEEXT
[svchost.exe]
UDP    0.0.0.0:3702           *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:3702           *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:4500           *:*
1000
IKEEXT
[svchost.exe]
UDP    0.0.0.0:5355           *:*
1104
Dnscache
[svchost.exe]
UDP    0.0.0.0:53274          *:*
4780
[VirtualBox.exe]
UDP    0.0.0.0:53727          *:*
4788
[VirtualBox.exe]
UDP    0.0.0.0:54111          *:*
4828
[VirtualBox.exe]
UDP    0.0.0.0:54112          *:*
4828
[VirtualBox.exe]
UDP    0.0.0.0:54113          *:*
4780
[VirtualBox.exe]
UDP    0.0.0.0:55421          *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:58596          *:*
964
EventSystem
[svchost.exe]
UDP    0.0.0.0:59838          *:*
4812
[VirtualBox.exe]
UDP    0.0.0.0:62498          *:*
4796
[VirtualBox.exe]
UDP    127.0.0.1:1900         *:*
4172
SSDPSRV
[svchost.exe]
UDP    127.0.0.1:55045        *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.1.87:137       *:*
4
Can not obtain ownership information
UDP    192.168.1.87:138       *:*
4
Can not obtain ownership information
UDP    192.168.1.87:1900      *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.1.87:55043     *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.56.1:137       *:*
4
Can not obtain ownership information
UDP    192.168.56.1:138       *:*
4
Can not obtain ownership information
UDP    192.168.56.1:1900      *:*
4172
SSDPSRV
[svchost.exe]
UDP    192.168.56.1:55044     *:*
4172
SSDPSRV
[svchost.exe]
UDP    [::]:123               *:*
964
W32Time
[svchost.exe]
UDP    [::]:500               *:*
1000
IKEEXT
[svchost.exe]
UDP    [::]:3702              *:*
964
EventSystem
[svchost.exe]
UDP    [::]:3702              *:*
964
EventSystem
[svchost.exe]
UDP    [::]:4500              *:*
1000
IKEEXT
[svchost.exe]
UDP    [::]:5355              *:*
1104
Dnscache
[svchost.exe]
UDP    [::]:55422             *:*
964
EventSystem
[svchost.exe]
UDP    [::]:58597             *:*
964
EventSystem
[svchost.exe]
UDP    [::1]:1900             *:*
4172
SSDPSRV
[svchost.exe]
UDP    [::1]:55042            *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::59f:484a:827f:42ba%11]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::59f:484a:827f:42ba%11]:55040 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::11a6:2283:bc40:c0cb%16]:1900 *:*
4172
SSDPSRV
[svchost.exe]
UDP    [fe80::11a6:2283:bc40:c0cb%16]:55041 *:*
4172
SSDPSRV
[svchost.exe]

An issue with authentication and authorization on ISE 1.2

Hi, I'm new to ISE.
I have an issue with authentication and authorization.
I have ISE 1.2 plus patch 6 installed on VMware.
I have built-in Windows XP supplicant and 2960 cisco switch with IOS c2960-lanbasek9-mz.150-2.SE5.bin
On supplicant I use EAP(PEAP) with EAP-MSCHAP v2.
I created authentication and authorization rules with Active Directory as External Identity Source. Also I applied authorization profile with DACL.I login on Windows XP machine under different Active Directory accounts. Everything works fine (authentication, authorization ), but only for several hours. After several hours passed , authentication and authorization stop working . I can see that ISE trying authenticate and authorize users, but ISE always use only one account for authentication and authorization . Even if I login under different accounts ISE continue to use only one last account.
I traied to reboot switch and PC,but it didn’t help. Only rebooting of ISE helps. After ISE rebooting, authentication and authorization start to work properly for several hours.
I don’t understand is it a glitch or I misconfigured ISE or switch, supplicant?
What should I do to resolve this issue?
Switch configuration:
testISE#sh runn
Building configuration...
Current configuration : 7103 bytes
! Last configuration change at 12:20:15Tue Apr 15 2014
! NVRAM config last updated at 10:35:02 Tue Apr 15 2014
version 15.0
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname testISE
boot-start-marker
boot-end-marker
no logging console
logging monitor informational
enable secret 5 ************
enable password ********
username radius-test password 0 ********
username admin privilege 15 secret 5 ******************
aaa new-model
aaa authentication dot1x default group radius
aaa authorization network default group radius
aaa authorization auth-proxy default group radius
aaa accounting update periodic 5
aaa accounting dot1x default start-stop group radius
aaa server radius dynamic-author
client 172.16.0.90 server-key ********
aaa session-id common
clock timezone 4 0
system mtu routing 1500
authentication mac-move permit
ip dhcp snooping vlan 1,22
ip dhcp snooping
ip domain-name elauloks
ip device tracking probe use-svi
ip device tracking
epm logging
crypto pki trustpoint TP-self-signed-1888913408
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-1888913408
revocation-check none
rsakeypair TP-self-signed-1888913408
crypto pki certificate chain TP-self-signed-1888913408
dot1x system-auth-control
spanning-tree mode pvst
spanning-tree extend system-id
vlan internal allocation policy ascending
ip ssh version 2
interface FastEthernet0/5
switchport mode access
ip access-group ACL-ALLOW in
authentication event fail action next-method
authentication event server dead action reinitialize vlan 1
authentication event server alive action reinitialize
authentication host-mode multi-auth
authentication open
authentication order dot1x mab
authentication priority dot1x mab
authentication port-control auto
authentication periodic
authentication timer reauthenticate server
authentication violation restrict
mab
dot1x pae authenticator
dot1x timeout tx-period 10
spanning-tree portfast
interface FastEthernet0/6
switchport mode access
ip access-group ACL-ALLOW in
authentication event fail action next-method
authentication event server dead action reinitialize vlan 1
authentication event server alive action reinitialize
authentication order dot1x mab
authentication priority dot1x mab
authentication port-control auto
authentication periodic
authentication timer reauthenticate server
authentication violation restrict
mab
dot1x pae authenticator
dot1x timeout tx-period 10
spanning-tree portfast
interface FastEthernet0/7
interface Vlan1
ip address 172.16.0.204 255.255.240.0
no ip route-cache
ip default-gateway 172.16.0.1
ip http server
ip http secure-server
ip access-list extended ACL-ALLOW
deny icmp any host 172.16.0.1
permit ip any any
ip radius source-interface Vlan1
logging origin-id ip
logging source-interface Vlan1
logging host 172.16.0.90 transport udp port 20514
snmp-server community public RO
snmp-server community ciscoro RO
snmp-server trap-source Vlan1
snmp-server source-interface informs Vlan1
snmp-server enable traps snmp linkdown linkup
snmp-server enable traps mac-notification change move
snmp-server host 172.16.0.90 ciscoro
radius-server attribute 6 on-for-login-auth
radius-server attribute 6 support-multiple
radius-server attribute 8 include-in-access-req
radius-server attribute 25 access-request include
radius-server dead-criteria time 5 tries 3
radius-server vsa send accounting
radius-server vsa send authentication
radius server ISE-Alex
address ipv4 172.16.0.90 auth-port 1812 acct-port 1813
automate-tester username radius-test idle-time 15
key ******
ntp server 172.16.0.1
ntp server 172.16.0.5
end

Yes. Tried that (several times) didn't work. 5 people in my office, all with vers. 6.0.1 couldn't access their gmail accounts. Kept getting error message that username and password invalid. Finally solved the issue by using Microsoft Exchange and "m.google.com" as server and domain and that the trick. Think there is an issue with imap.gmail.com and IOS 6.0.1. I'm sure the 5 of us suddently experiencing this issue aren't the only ones. Apple will figure it out. Thanks.

Connection Issues with BT infinity + HH3

I have had BT infinity installed for a couple of months now and I have got some issues with the connection that I am getting.
Now the Internet connection speed is not a issue getting about 35mb wired and 26mb over Wi-Fi and is pretty stable.
But when using my iPad 2 and watching a youtube video even at the lowest quality (using the App or Website) sometimes the video will often stop loading at a point and will not load the rest of the video so the video will just stop. This does not happen on my laptop.
This also affects the BBC iPlayer App, where I cannot even get a programme to even start playing. This all worked fine with BT Option 3.
It also effects Apps like Twitter were loading new tweets in the timeline can sometimes take forever for just a bit of text.
My Xbox 360 also will not connect to the WiFi at "N" only at "G". Even though I have one of the new style Xbox 360's that has Wireless N. Also i find the Download speeds realy slow. Took nearly 30 Miniutes to download a 1.3 GB file compared to about 6-8 on my laptop.
The one computer that i connected to the HH3 via a Ethernet cable has the most issues where it can take many minutes to load up the simpliest webpage like eBay. This problem does not happen all of the time but useally a couple of time per week. And what seems to happen is you click on a link and nothing happens then everthing loads.
Has anybody got any of these issues as this laptop seems to be fine but the iPad will not also load the content, and the computer that shouyld be the fastest seems to sometimes be the speed of a dial-up Modem.
Apart from getting rid of the HH3 and getting someting like a Apple Airport Extreme are there any other soloution to why this happens. This is not what i thought BT Intinty would be like.

It could be a dodgy router but check the following first
1) All connections are set to use DHCP(automatic) rather than fixed IP addresses and that the IP list on the Hub does not contain duplicate entries.
2) As the wired connection is running slowly it is unlikely to be a wireless conflict but use Inssider 2 to ensure you are not using a crowded channel the HH3 is supposed to do this automatically but seems flaky
You could try getting a new Hub sent to you but unless you feel rich or have Apple shares there are cheaper cable routers than the Apple ones around & any router that offers PPOE will work. Plenty of reviews on the web and you can buy them from £20 up.

NAC issue with DHCP

Similar Messages

Maybe you are looking for