Connect wireless clients / PIN

I am trying to add a wireless client to my network and am following the instructions on the following linked Web site:
http://docs.info.apple.com/article.html?path=AirPortUtility/5.1/en/ap2118.html
I want to allow a client access to my network using the PIN method.
When I try to enter a number in the PIN field, I am unable to type anything in the field. The cursor is in the field and blinking, but when I type, no characters are entered.
How can I solve this problem?
Message was edited by: Diamondtron

I appreciate the responses to this thread, but I am still experiencing my issue. Here is a more detailed breakdown of the issue
Problem Statement: After installing the Linksys product, all clients are able to access the Internet, but not all clients can "see" each other.
Clients consist of 1 Dell Desktop PC running Windows Vista and two laptops (one Dell and one Compaq/HP both running XP PRO).
I am able to ping from the Vista machine to the XP/Dell, but not in the other direction.
I have enabled sharing on all systems but still cannot map to the printer connected to the Vista machine.
I have created a workgroup and can see the XP laptop (I haven't joined the HP laptop to the WG yet) from the Vista machine, but cannot see the Vista machine from the laptop.
All sharing worked fine when I was running the previous wireless setup (2WIRE SBC/YAHOO DSL modem). I did not have to go to the extent of creating a workgroup and a "network," the machines were able to communicate fine.
I am inclined to believe the issue lies with the router, but Linksys disagrees. The router itself seems to be working correctly and I have been assured by Linksys Tech Support that there are no settings on the router that would prevent clients from seeing (pinging) one another.
(Edited post for guideline compliance. Thanks!)
Message Edited by JOHNDOE_06 on 04-16-2008 01:07 PM

Similar Messages

Issue connection wireless clients and AP reboot

Hi all,
I have 2 problems in my Wifi infrastructure.
1) All my AP's reboot randomly, the 1st reboot was after a power failure of all the building. the 2nd one was yesterday, but we don't know why...
Here are the logs : ap_logs.png
2) I have motorola 9190 connected to a specific SSID, our customer use these motorola to scan the merchandising. They disconnect some times and they have to reconnect manually again, or reboot the scanner...
Here you can find the logs also: scan_logs.png
Here you can see the client was connected at 8h03, and disconnected at 8h05...
If someone can help me, because i really don't understand what is going on...
Thanks in advance,
Alexis

Stay away from this code... I would recommend you to go for 7.6.130.0 (7.6 MR3) when it releases within next couple of weeks.
Then see whether problem persist
HTH
Rasika
**** Pls rate all useful responses ****

How to manually connect wireless clients on Time Capsule with Airport 6.1?

I'm having trouble setting up wireless access for an older Dell laptop and a wireless HP 4500 printer on a new Time Capsule wireless network. All of the workarounds that I've found (adding a client manually so no WPA password is needed; generating an equivalent network password, etc) and even the Time Capsule setup manual itself reference options in AirPort Utility that are not available up on my Mac running Mountain Lion. I've figured out that the AirPort for Mountain Lion must be the root of the problem--and I can see that there are 5.6 vs. 6.0 discussions. Clearly the 6.0 version has a whole new interface and advanced options don't appear readily available. Can AirPort 5.6 run on Mountain Lion? Or is there a another way to get to these manual settings so I can get these devices to just work?
It's a real bummer to have no information from Apple to update the Time Capsule user manual and help files for what obviously is a common problem in setting up a mixed wireless network.
Thanks for the help.

You are right of course.. it is about time Apple updated Time Capsule both hardware and instruction for usage on v6 utility. I wonder if TC is doomed in the future which apple sees is all cloud.
You can load 5.6 into mountain lion.. you cannot run it as the application installer will fail. But it is still easy to get it working.
Download the 5.6 package.
Download unpkg http://www.macupdate.com/app/mac/16357/unpkg
Run unpkg
Open the dmg and drag the pkg file over to unpkg.. the 5.6 utility will be loaded to a directory on the desktop. Drag the file to your utility directory.. you only need the main file.
But it could be even easier to just download and install the airport utility for windows.. which will have bonjour for windows. Plug into the TC by ethernet.
Whichever way you do it.. change the TC name and wireless names to SMB compatible.. ie short, no spaces and pure alphanumeric.. no apostrophe.. that absolutely ghastly Apple invention.
Set a workgroup name in the file sharing. WORKGROUP generally
Set guest account to read and write.. at least initially as it is easier by far to get access.
I would also lock channels and if the computer uses 5ghz then give 5ghz wireless a different name.. The band swapping is only for Macs.

E1200 Wireless Client List will not display and causes web UI to temporarily stop responding

I picked up an E1200 and set it up successfully. I am using wireless MAC filtering, and decided to pull up the list of connected wireless clients (Wireless >> Wireless MAC Filter >> push "Wireless Client List" button).
When I do so, it immediately throws this back:
Immediately after this the Web UI of the E1200 becomes inaccessible. It still routes traffic, and the router remains pingable, but it will not allow access to the Web UI for several minutes. The error that appears upon attempt to access the Web UI during this time window is similar to the above, but reads "Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the connection."
I have tried this in Google Chrome, Firefox 4, and MSIE on two separate computers. Each browser displays the error a bit differently (MSIE, for example, just says it can't display the page and gives no further detail) but the net results are always the same. I have tried resetting the device to factory defaults in addition to re-downloading the firmware from the Cisco/Linksys website and installing it. No improvement.
I have also noted that the Log (Administration >> Log; and yes, I have it enabled) doesn't appear to be picking up anything at all. In fact, the Security log, which supposedly (according to the Help) "displays the login information for the Router’s browser-based utility," is also blank.
Is this a bug, or should I head back to the retailer and swap this device?

Ok - I nailed this down, I think, and it looks like a firmware bug.
Short version is that a factory reset cleared the issue, but during stepwise reconfiguration the problem came back. Through a bunch of iteration I figured out that if I have the E1200's DHCP server disabled *and* have wireless clients connected to it, the problem I described appears.
Turn the DHCP server back on and the problem goes away. Turn it off and the problem comes back. Turn it back on and it goes away. You get the idea.
If I had to pose a theory here, it's that the initial display of the Wireless Client List, which uses "IP Address" as the default sort, somehow implodes if the E1200 isn't actually assigning those IP addresses to the clients.
When this happens it appears to crash the Web UI wholesale. Just for grins, while the Web UI was unresponsive, I pinged the router it as before - still pingable - then ran nmap against it - no open ports found on the router. When the Web UI is functional, though, nmap detects port 80 quite easily. I have not timed how long it takes for the Web UI to come back up, but it is longer than 5 minutes, and I presume some sort of watchdog process has to detect that it has gone kaput and start it up again.
Final test was to restore my saved configuration from before the factory reset (note that the saved config was done under the same firmware version, and in this config, the DHCP server is disabled). Boom, problem. Wait for the Web UI to come back, turn on the DHCP server. Problem goes away. Turn the DHCP server off. Boom, problem comes back.
So, there you go.
Would be interesting if someone could verify this via a test against another E1200. It may be worth noting that in my baseline test I was also using Manual wireless setup (vs. Wi-Fi Protected Setup), and WPA2. Didn't make any other setting changes from the factory defaults. I did not actually have to turn the Wireless MAC Filter on to do the test. All one needs to do is click Enable on the Wireless MAC Filter tab, and then do *not* click Save Settings - just clicking Enable will light up the Wireless Client List button, which you can then push to get the list. That is how I handled testing to ensure that neither specific entries, nor the Prevent/Permit setting, nor having the filter enabled in saved configuration were involved in the problem.
Separately, no explanation for the lack of entries in the security log, but that pretty much looks like a firmware bug to me as well.

Getting Wireless client list in WRT54G?

On one of the other sites Isaw a post showing a URL you could use to get a WRT54G to lsit the currently connected wireless clients. unfortunately this URL did not work on my v5. The DHCP client list is useless because I host my DHCP server elsewhere and don't use the internal server.
Does anyone know how to tickle a WRT54Gv5 into giving up the wireless client list?
Thanks In Advance,
Mark

The wireless client list is available in the WRT54G v5+. The URL is http://192.168.1.1/WClient.htm
The button to display the table is hidden until Wireless MAC Filter is ENABLED on the /Wireless/Wireless MAC Filter page.
http://192.168.1.1/WFilter.htm

Wireless clients cannot get to internet

Hi All,
I'm fairly new to networking and have been trying to troubleshoot an issue with my home lab.
I have a Cisco 2800 router with 2 interfaces, gig0/0 that is the "external" interface and gets an IP via DHCP, and gig0/1 that is the internal interface with IP 10.10.10.1 and a DHCP pool of 10.10.10.100 - 10.10.10.254. A nat pool containing the external interface IP (192.168.1.110) exists.
Current configuration : 3229 bytes
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Router
boot-start-marker
boot-end-marker
no aaa new-model
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 10.10.10.1 10.10.10.99
ip dhcp pool dpool1
import all
network 10.10.10.0 255.255.255.0
dns-server 8.8.8.8 8.8.4.4
default-router 10.10.10.1
ip domain name home.local
ip name-server 8.8.8.8
ip name-server 8.8.4.4
multilink bundle-name authenticated
interface GigabitEthernet0/0
ip address dhcp
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
interface GigabitEthernet0/1
ip address 10.10.10.1 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
no mop enabled
interface FastEthernet0/3/0
shutdown
interface FastEthernet0/3/1
shutdown
interface FastEthernet0/3/2
shutdown
interface FastEthernet0/3/3
shutdown
interface Vlan1
no ip address
shutdown
ip http server
ip http authentication local
ip http secure-server
ip nat pool ovrld 192.168.1.110 192.168.1.110 prefix-length 30
ip nat inside source list 1 pool ovrld
access-list 1 permit 10.10.10.0 0.0.0.255
snmp-server community public RO
control-plane
scheduler allocate 20000 1000
end
Coming off the internal interface is a 3750, and attached to that 3750 is a 4400 Wireless Lan Controller.
I'm able to create a wireless network that uses the router for DHCP and clients can connect to this wireless network and obtain an IP from that DHCP pool. The wireless clients can ping the default gateway (10.10.10.1) as well as every other device on that network, including hard-wired devices on the 3750. The arp table on the router also shows the wireless clients.
However, only clients connected via ethernet can access the outside (internet), wireless clients, who appear to get the exact same network config, are unable to access the internet they can only access other devices on that 10.10.10.0 network.
So I'm confused as to why with what appears to be the proper default gateway (10.10.10.1) and a valid IP from the router, what could be broken so hard-wired clients can NAT to the outside while wireless clients can't? I can't find any setting on the WLC 4400 that would be restricting wireless clients from leaving the local network.
Any clarification on my issue/my understanding of the problem would be greatly appreciated. Cheers!

Hello smorrissey,
May I ask, how many end devices do you have connected to the switch? And if you tried to connect wireless clients simultaneously with wired devices?
Because from your config it seems you're using only dynamic NAT:
ip nat inside source list 1 pool ovrld // this command will translate IP picked by ACL 1 to address in pool named ovrld. Because you have only 1 address in this pool, only 1 inside device will be able to communicate with outside world (Internet) at a time.
I would suggest to add keyword "overload" at the end of this command (ip nat inside source list 1 pool ovrld overload) to enable PAT, which will allow multiple LAN devices to use 1 outside address at the same time thanks to port address translation.
Hope this will help.
Michal

Can't connect iPod Touch to Airport Extreme using "Add Wireless Clients"

I am unable to connect my iPod Touch to the local wireless network (Airport Utility v5.4.2) using "Add Wireless Clients..." in the Base Station menu.
My Powerbook G4 connects OK (with the PIN - as requested)
I can find no information in Apple's manuals or Help.
Message was edited by: Peter Mitchell3
Message was edited by: Peter Mitchell3

You seem to be going about this backwards. Setup your Airport base station to:
broadcast in all modes (b/g/n)
No MAC address filtering
Encryption set to WPA
SSID on (you are broadcasting your network's name)
DHCP on (you are automatically assigning IP addresses)
On your touch, go to Settings > WiFi >Other Networks, enter your network name, tell the touch which security you are using (WPA) and enter your password. You should connect to your network.

Can't add wireless client in Airport Extreme, what is and where is 8-digit pin?

Recently we bought a new MacBook Pro and at home I have a wireless network for my computer. I wanted to add the MBP to the network, but without using the network password, so I was looking around on here to see how to do it and I looked at the manual, but the manual doesn't tell me where or what the 8-digit pin is.
My question:
How do I add a client using an 8-digit pin, more specifically, where can I find this number?
I've looked at a few discussions in here regarding the same issue, but found no result. Sorry if this really has been solved before and I was not able to find it.
Details:
Computers:
iMac (bought in November 2007)
MacBook Pro (Sept 2011)
OSX:
Lion 10.7.1 (on both machines)
Airport Base Station:
Airport Extreme 802.11n (2nd Generation)
Version 7.5.2
Airport Utility:
Version 5.5.3 (553.20) (on airport admin machine, iMac)
Network:
-Closed
-Not extended
Wireless Security:
WPA2 Personal
I am unsure if this piece of information is of any use or importance, but I have an older machine (PowerMac G4) connected to the Aiport Extreme via Ethernet, aswell.
Thanks

Yes, I think so? Maybe I should have specified my goal with the network.
Since my brother got a new laptop, I needed to add him to the network somehow. I didn't want him to know/use my password, so I was looking into creating a separate network altogether, but as I learned I cannot do that with the Airport Extreme I have. Then I was looking into other ways that would allow me to let him use the network but without having to type in the password, and I found that "Add a Wireless Client" thing. According to that, all I needed to do was put in an 8-digit pin that was "provided" by the client. I thought that I could just make up some 8-digit pin and that ultimately would be his "password" for the network, but even typing in abritrary 8 digits wouldn't allow me to click on the "continue" button or whatever button that is, the button would remain inactive.
I temporarily changed the password to the network to have him added, for now (connecting normally, click network name and type in password), but if I can figure out how to get him on something separate or just him not having to type in the password, that would be better so I can revert or change my password to something else more meaningful for me.
I hope this makes more sense.

Some wireless clients can't discover or connection to local wired systems

Hi,
I've just upgraded my home wireless from an NetComm NB5540 + modem to a LinkSys X3000.
Internet access works fine for all devices, but some wireless devices can't "see" my Win7 desktop system that's on a wired connections to the router.
I've tried three devices...
Galaxy Note phone (running ICS 4.0.4) can discover and connect to file shares on my desktop system without any problems.
Asus Transformer Prime tablet (running JellyBean 4.1.1) can see the router on the local network, but can't see my desktop. Even if I manually type in the IP address it can't connect to it
Likewise my old WinXP laptop can see the router but can't see or connect to any other devices.
Any suggestions welcome.
Hugh
ps. I tried connecting the NetComm router with just Wifi configured to one of the ethernet ports on the X3000, so I've got two Wifi networks running in parallel. If I connect to this second WiFi network with any of the above devices then they can all discover and connect to my desktop system on the wired connection to the X3000.

Just to test network connectivity, why don't you ping the wired client from the wireless devices that are not able access it? Do post your results so we can further analyze this scenario. By the way, when you cascaded another access point (using the NetComm router) to the X3000, was it via LAN- LAN? Was the X3000 still the DHCP server for the wireless clients?

Bridge does not work for wireless clients - connecting to existing network.

Hi - I really hope somebody can help out here, after hours of trial & error, I have finally given up
I need to connect my Airport Extreme Base Station to my existing network. I have a linksys router (192.168.15.1) connected to my modem and this linksys router acts as DHCP server too.
I suppose I have to use "bridge mode" for that to work. But should the linksys be connected to the AEBS using the AEBS's WAN or LAN port?
If I use "bridge mode", then wired computers to the AEBS works fine - getting an IP from the linksys etc. BUT, the wireless clients will have a self-assigned IP and not get through to the internet. It's like the AEBS will not allow wireless clients to "get through" unless AEBS itself is handing out IP addresses.
Page 36 of this manual ( http://manuals.info.apple.com/en/DesigningAirPort_Networks10.5-Windows.pdf ) shows the setup I want. But in the picture, it says "Ethernet WAN port" but the text says: "The Apple wireless device (in this example, a Time Capsule) uses your Ethernet network to communicate with the Internet through the Ethernet LAN port ( <--> )." I don't know which one to use, WAN or LAN - they show WAN but say LAN?
When I set it up as "share an IP address", the AEBS status tells me "double nat" and to change from "shared IP" to "bridge mode". I do that, and everything seems fine - for the wired clients. Now the wireless clients cannot connect, Airport on the MacBook Pro just say "Connection failed" and the MacBook says "Invalid password" (translated from danish), even though I set the Airport Utlity to save the password in keyring, so it should be correct... If I disable wireless encryption, the wireless clients will connect but get a self-assigned IP, and therefor not work (cannot get online)...
It seems the only way I can get wireless to work, is if I set AEBS up as DHCP, but then it won't be on the "same network" as the linksys (192.168.15.1), but rather on 10.0.x.x as I select. If I select 192.168.x.x within AEBS, I'm also getting some error messages, conflict/subnet thing.
Anyway - I really hope somebody knows how to get wireless clients to get an IP address from existing ethernet when connected to the AEBS.
Thanks!!

I've given up and had to go back to running "Double NAT" which also reports as a "problem" within the AEBS, but I just "ignore" it so the light will always be green.
It still ***** though, as "Double NAT" is also a reason for "Back to my Mac" not working properly, but how the ** am I supposed to avoid Double NAT when the wireless will not work in bridged mode?!

2504 controller + 2602 APs = wireless clients connectivity problems

Hello, everybody!
I have a connectivity problems of wireless clients. The symptoms are:
1) Some clients receive 169.254.x.x., instead a correct DHCP addresses, less in a minute connection drops, and in controller's "Monitor" > "Clients" tab these clients are marked as "Excluded".
2) Most of the clients receive the correct addresses from DHCP (192.168.2.x), but also loose connection soon.
3) Wireless clients with correct addresses can't ping each other, gateway and an address of the controller's dynamic interface (all of them are in same subnet).
4) And the most suspicious problem is that some machines are unable to connect to APs after several attemps to do that. I mean, I configure controller and change some options, trying to understand, whether they were applied or not and constantly connect and disconnet certain PC to the SSID. After five or ten attempts I can't connect to the SSID. During these attempts, the others PCs stay connected, without interruptions, and they could be reconnected again. It's like some kind of port security works, but I'm not sure...
Do you have any ideas which options should I configure?
My configuration:
I have three interfaces on the controller: virtual, management (default) and dynamic (it is set to the WLAN)
I have one SSID, WPA/WPA2, AES/TKIP, authentication PSK.
My clients are a/b/g/n, all are permitted on the controller. No custom security policies were applied.
All the devices are in a single room: controller, one AP and different clients: desktop, notebooks, iPad, Nokia Lumia, etc.
I have an internal DHCP Server on the controller and it works perfectly well.
I can provide all the screenshots required from web-interface of the controller...
Many thanks in advance for all ideas that you have about these problems...

Hi, there!
The problem was solved.
1) APIPA address receives only single machine with Win8 - I think there are some firewall issues
2) Other devices have been loosing connection because they were mobile devices, like iPad and Lumia. If you keep working with it, it doesn't drop the connection
3) The dynamic interface address and gateway address were inaccessible because i had not used an appropriate port on the controller. =)))) Firstly, it was just a guess, but it proved.
Now, everything works with WPA2, AES, PSK...
It is a very good day!)
The only question remains: why I can't connect machines, which have a static IP? During the controller initialization, I said "yes" for permitting static IPs...
Guys, many thanks for your help!

APEx '03 and Non-Apple Wireless Client Connection Problems

Good morning. I have a 2003 vintage AirPort Extreme, running 5.5.1 firmware (due to the issues with the newer firmware discussed on this forum).
--> Wired iMax
My setup is DSL-->APEx--|
--> Apple Wireless Clients
--> Linksys w54 acting as a bridge
In order to get the Linksys working in the first place, I had to remove the WEP, not a huge deal as we live in the boonies and no one within range of the APEx. I couldn't figure out how to get anything to work with Apple wireless security outside of the Family. I have it manually set to channel 1, and radio mode to G only.
My problem basically is that non-Apple devices can see the SSID but cannot connect. The problem at hand are my kids' various PSPs & Ninendo DS's, and a little Windows CE netbook. Of course, none of these simple devices give anything helpful in terms of errors. Those three different devices all have their own version of the same error: See the SSID, try to connect, but fail.
I'd like to figure out this problem, although the simpler solution might be to just buy another cheap Linksys on craiglist and use it for the non-Apple stuff.

Bump?

HT4260 Can i control which wireless clients i like to betrol which wireless clients i like to be connected on my airport base station?

Can i control which wireless clients i like to betrol which wireless clients i like to be connected on my airport base station?

Yes. Use AirPort Utility's MAC Address Access Control.
AirPort Utility > select your base station > Edit button > Network tab > "Enable Access Control" > click the Timed Access Control button.
You need to specify the clients you want to control by their MAC address, which is usually printed on the device's exterior case.

Can't Add Wireless Clients; Can't Type PIN into Setup Field

I have an Airport Express "n" station, set to be compatible with "b" and "g" as well.
I would like to use the Add Wireless Clients feature of 7.3.2.
In the Airport Utility, when I go to:
Base Station > Add Wireless Clients
and follow the prompts, it never finds any first-time clients to assign a PIN to, even when there's one present that already has logged in and out of the network with a password.
Am I misunderstanding the way this function works? I assume from the Help page that when a client is within range, you can assign it a PIN for 24 hours or permanently. But I can't seem to make it work.

Since writing the title of this post, I was able to type numbers into the setup field; I forgot to delete that from the title. Apologies.

Network Policy Server windows 7 non domain wireless clients could not connect (Event id 6273 reason code 265)

Hi,
We have successfully configured network policy server on windows server 2012 and all wireless clients could connect to our network except windows 7 and xp non domain clients.The clients that are successfully authenticated includes windows 8,mobile users
(andriod + iOS) domain as well as non domain clients.If we join windows 7 pc to the domain it successfully connects but non domain clients could not connect.We have large number of windows 7 users that have their own laptop machines and we dont want
each laptop to join the domain.
On server event 6273 generated with reason code 265 "The certificate chain was issued by an authority that is not trusted".Plz help how to resolve this issue.I have searched on the internet but no proper solution found.

Hi,
According to the error message, it seems that you used certificate-based authentication methods and the non-domain computers has no Trusted Root Certificate for the CA that enrolled the certificate for the NPS.
For more detailed information, please refer to the links below:
Certificates and NPS
Manage Trusted Root Certificates
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Connect wireless clients / PIN

Similar Messages

Maybe you are looking for