WEP encrypted network - can't connect

I'm trying to use netcfg2.0.6 to connect to a WEP-encrypted network, but it doesn't work, with the error message:
:: father up - Wireless association failed. [FAIL]
I can correctly connect to a different wpa-encrypted network, so I'm assuming it's a problem with my configuration, not my hardware.
ifconfig -a (just relevant wlan0 part) gives:
wlan0 Link encap:Ethernet HWaddr 00:15:AF:3B:64:A9
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
iwconfig before attempting to connect (however, I have tried to connect earlier today, which is probably why the ESSID is set):
wlan0 IEEE 802.11g ESSID:"02wireless314821"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
The profile I'm using for this connection is:
CONNECTION="wireless"
INTERFACE=wlan0
SCAN=no
SECURITY="wep"
ESSID="02wireless314821"
KEY="xxxxxxxxxx"
IP="dhcp"
TIMEOUT=20
I'm using the stock kernel from testing, with the rtl8187 driver.
Does anyone have any idea what's wrong, and how to fix it?

I have the exactly same issue. I have to do 'netcfg2 wifi' about 3-5 times to connect. I also have iwl3945. More here (my thread about this issue). I quickly wrote this script:
#!/bin/bash
ifconfig wlan0 up
iwconfig wlan0 essid linksys key `grep KEY /etc/network.d/wifi | cut -d'"' -f2`
sleep 1
ifconfig wlan0 192.168.1.101
echo "nameserver 192.168.1.1" > /etc/resolv.conf
route add default gw 192.168.1.1
sleep 1
ping www.seznam.cz
When run for the firs time, it freezes and I have to do ^C (C-c or Ctrl-c) to kill it and run it again. Second time it goes like:
SIOCADDRT: File exists
PING www.seznam.cz (77.75.76.3) 56(84) bytes of data.
64 bytes from www.seznam.cz (77.75.76.3): icmp_seq=1 ttl=56 time=14.1 ms
64 bytes from www.seznam.cz (77.75.76.3): icmp_seq=2 ttl=56 time=13.6 ms
^C
--- www.seznam.cz ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1003ms
rtt min/avg/max/mdev = 13.680/13.938/14.197/0.284 ms
I haven't tested it more yet, because it works ten times faster than netcfg2 for me, which makes me happy for now. I have no idea whats going on behind if/iw commands.
Last edited by dante4d (2008-06-15 10:02:32)

Similar Messages

  • I can't connect with wep encrypted network

    Hi,
    I'm trying to connect with this accesspoint:
    Cell 03 - Address: 00:14:C1:30:FE:ED
    Channel:11
    Frequency:2.462 GHz (Channel 11)
    Quality=40/70 Signal level=-70 dBm
    Encryption key:on
    ESSID:"Masters"
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s
    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
    Mode:Master
    Extra:tsf=000000063d3dc183
    Extra: Last beacon: 136ms ago
    IE: Unknown: 00074D617374657273
    IE: Unknown: 010882848B962430486C
    IE: Unknown: 03010B
    IE: Unknown: 2A0100
    IE: Unknown: 2F0100
    IE: Unknown: 32040C121860
    IE: Unknown: DD060010180201F5
    Of course i tried:
    [root@myhost shnela]# iwconfig wlan0 essid Masters key s:mastuning2000
    [root@myhost shnela]# iwconfig
    lo no wireless extensions.
    wlan0 IEEE 802.11bgn ESSID:"Masters"
    Mode:Ad-Hoc Frequency:2.412 GHz Cell: 66:BA:DC:7E:D2:E5
    Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Encryption key:6D61-7374-756E-696E-6732-3030-30
    Power Management:off
    eth0 no wireless extensions.
    But I didn't get ip address:
    [root@myhost shnela]# dhcpcd wlan0
    dhcpcd[1040]: version 5.2.12 starting
    dhcpcd[1040]: wlan0: waiting for carrier
    dhcpcd[1040]: timed out
    or
    [root@myhost shnela]# dhcpcd wlan0
    dhcpcd[1092]: version 5.2.12 starting
    dhcpcd[1092]: wlan0: rebinding lease of 192.168.4.63
    dhcpcd[1092]: wlan0: broadcasting for a lease
    dhcpcd[1092]: timed out
    I tried also netcfg with profle "stancja":
    CONNECTION='wireless'
    DESCRIPTION='A simple WEP encrypted wireless connection'
    INTERFACE='wlan0'
    SECURITY='wep'
    ESSID='Masters'
    KEY='s:mastuning2000'
    IP='dhcp'
    # Uncomment this if your ssid is hidden
    #HIDDEN=yes
    But when I use it, it returns:
    [root@myhost network.d]# netcfg stancja
    :: stancja up [BUSY]
    > WPA Authentication/Association Failed
    I don't know what WPA Autenthication do here...

    Oh.. I'm very sorry. I confused my "iwconfig" output...
    I've similar problem with this particular ap with debian too ( I can connect onnly with wicd).
    I changed frequency and tried change ap addr:
    [root@myhost shnela]# iwconfig wlan0 ap 00:14:C1:30:FE:ED
    [root@myhost shnela]# iwconfig wlan0 freq 2.462G
    [root@myhost shnela]# iwconfig
    lo no wireless extensions.
    wlan0 IEEE 802.11bgn ESSID:"Masters"
    Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
    Tx-Power=15 dBm
    Retry long limit:7 RTS thr:off Fragment thr:off
    Encryption key:6D61-7374-756E-696E-6732-3030-30
    Power Management:off
    eth0 no wireless extensions.
    [root@myhost shnela]# dhcpcd wlan0
    dhcpcd[1336]: version 5.2.12 starting
    dhcpcd[1336]: wlan0: waiting for carrier
    dhcpcd[1336]: timed out
    I'm stil Not-Associated.
    This is my rc.conf file:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # 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_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK="localtime"
    TIMEZONE="Europe/Warsaw"
    KEYMAP="en"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MODULES=()
    # Udev settle timeout (default to 15)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # 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="myhost"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    interface=wlan0
    address=
    netmask=
    broadcast=
    gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="no"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as 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 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
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(hwclock syslog-ng network netfs crond alsa sensors)
    Last edited by shnela (2012-02-12 20:23:50)

  • Can't connect or see me home network, can see/connect to others.

    I have a fun one. I can't see or connect to my home network on 3 seperate iphone 3g's.(not 3gS.) I have a laptop, desktop and xbox that connect fine. It was working 4 days ago on this same router with the same settings. my SSID is being broadcast. I have the same security settings I had before, nothing has changed. WEP, channel 11, 802.1 g and b enabled. I can see my nieghbors wireless networks, but not mine at all. I can even connect to one of my neighbors unsecured network if the wind blows right and I get enough bars. I have reset the network settings on one iphone, restarted it, hard reset, complete restore, tried to "find other" networks. Nothing. (My network is on channel 11 because ALL of my neighbors are currently on channel 6 and it causes all my computers to drop due to interference. Worked fine for days on channel 11.)
    It's a brand new belkin router. And it was working fine for over a week. And the laptop, desktop, and xbox are still working fine. but none of the iphones in my house (3) can even see the net work on the screen. (And yes, the SSID is being broadcast.)
    Has anyone ever seen this issue?

    ok. I have a Belkin Wireless N Router. For some reason the settings appear to have become corrupted. I still have no clue why it was able to work with the computers and xbox, but not the iphones. I now have it working.
    The solution:
    Reset your router back to factory. Then rebuild your network settings, do not "restore" from a file. (Don't know why but it didn't work.) I made sure to connect to the network with the phone after each change and saved the settings on the router each time.
    Part of the problem may be with alternate channel settings, after I changed to channel 11 again, (to avoid the competition issue with my neighbors on channel 6) the iphone did lose view of the wireless until I rebooted the router. Make sure your router is connected with a hardline while you make the changes.
    All is working now, 3 iphones, 2 computers and an xbox in a pair tree!

  • New Mac Mini - Existing Wireless Network - Can't Connect

    I have an existing wireless network that works fine with an iBook G3. I just hooked up my Mac Mini and it can see the network, but it can't connect. The menu of available networks on the Mac Mini is also much more limited than that of the iBook. Is there an interference issue? If yes, why does the iBook working?
    Mac Mini 1.66GHz Intel Core Duo   Mac OS X (10.4.8)   iBook G3

    I see a string of discussions under Mac Mini.

  • Wireless Network - can't connect!!

    Lenovo N 3000 running Windows Vista Business
    Product 0769A64
    I can't connect to wireless internet. Am at the end of my tether and hope it's something simple!
    This is what's happening so far...
    Using Access Connections, I can use the wireless radio to find the network I want. It's a public wireless connection (in a library). It has signal strength of 60%. This has been more than fine for me in the past. Everyone else is using it so why can't I!?!?!
    When I try to connect through Access Connections, I get the following message:
    Unable to connect to the selected wireless network. You may need to configure your system to support the authentication method that is in use. Do you want to configure now?
    I click Yes, (don't really know what I'm doing at this point so just OK out of that window)
    Then it tries to connect. It then goes through Applying wireless settings - OK, then when it says 'waiting for association, it fails.
    If I connect through networks, I can connect to the local network only, but not the internet.
    What I've tried to fix it (don't even know if any of this is relevant...):
    Made sure it's automatically setting IP address.
    Switched off Windows Firewall
    Boot in safe mode.
    Checked the network adapter and it is working properly and has up to date drivers.
    In Control Panel- Network connections, under Wireless Network Connections, I've disabled/enabled TCP/IPv6 and TCP/IPv4 in various combinations.
    Thought I may as well let the cat have a go at fixing it after all that lot.
    Run command prompt as administrator.
    ipconfig /release shows: No operation can be performed on Wireless Network connection while
    it has its media disconnected
    ipconfig /all shows:
    Host Name..............Default-PC
    Primary Dns Suffix.....:
    Node type..............Hybrid
    IP Routing Enabled.....No
    WINS Proxy Enabled.....No
    Ethernet adapter Local Area Connection
    Media State............Media Disconnected
    Connection-specific DNS Suffix..:
    Description............Intel(R) PRO/Wireless 3945ABG Network Connection
    Physical Address.......:00-1B-38-0c-25-E2
    Autoconfiguration Enabled....Yes
    Wireless LAN adapter Wireless Network Connection:
    Media State............Media Disconnected
    Connection-specific DNS Suffix...:
    Description............isatap.(453E23F5-D966-4B89-B53C-A4E3D9CF0071)
    DCHP enabled...........Yes
    Autoconfiguration enabled...Yes
    Then a load of stuff about Tunnel adapters - *6, *7 and *9 are discomnnected. Apparently.
    Tried to run PC Doctor on the network card and it passed the following tests:
    PCI Express Status Test
    Wireless Connectivity Test
    Wireless signal Strength Test
    Network Link Test
    But it couldn't run the :
    TCP/IP Network Communication Test
    Any help at all would be incredibly gratefully received!!
    Thanks, Claire.

    I just purchased a Thinkpad from Lenovo with the Intel 5100 AGN wireless card in it. I kept losing my connection to the Internet. I searched on the web for a solution and tried a number of the suggestions, one of which solved one problem (access connections was turning off the wireless radio during inactivity to "save power"), but the problems persisted, even after I let Windows manage the connections.
    The first symptom I noticed was that Windows could not find any networks. The next one I noticed was that the signal strength would drop very low. I even saw that when the laptop was 2 feet away from the router.
    I finally came to the point where I was suspecting the Intel 5100 AGN itself. I have 2 other computers that use my wireless router and they have no problems, and people have come over with laptops and have not had any problems.
    The router I have is D-Link Di-624 Xtreme-G. It seems to work just fine. I reconfigured the router to not use its Super-G mode. That appears to have eliminated the problem. It is still too early to be sure since the problem is intermittent, but it has stayed connected for a day now (whereas I used to lose the connection frequently in any given day).
    I can't say for sure if the problem is with the 5100 AGN card, but I suspect it is. Given that I have never had this kind of problem with other computers (with varying cards) but only with this new one, the culprit seems to be the Intel 5100 AGN.
    There are a lot of posts on the web about this very problem and no one seems to have found the answer.
    I may have fixed the problem within my home by reconfiguring the router, but I can't do that for other routers (eg in a coffee shop). Other people have "solved" the problem by buying a new router (an expensive solution). The real fix has to be in the 5100 AGN itself, either a better driver (I have the latest version 12.1.0.14), or some card configuration (or else somehow replace it with a better wireless card).

  • Can see wireless network, can't connect. HELP!

    I have an iMac 1GHz PowerPC G4 running 10.3.1 that I just installed an AirPort card into. I can see my wirless network, but I cannot connect to it. The password is correct, but I keep getting the error "There was an error joining the selected AirPort Network". Please help!

    I'm not positive on this, but it might be a encryption compatibility problem between your network and your AirPort Card.  I believe that OS 10.3.x is only capable of the basic encryption WEP, and not the the more modern encryptions WPA and WPA2.  I also think if you upgrade to 10.3.9, that might help get you into WPA encrpytion but it still not up to WPA2 that many modern networks now use.  Then there is 40 bit and 128 bit encryption, and I can't help you there with that.
    There are two iMacs with a G4 1Ghz chip, the 15" model M9285LL/A or the 17" model M8935LL/A.  Both of these are AirPort Extreme ready.  Did you use an AirPort card or an AirPort Extreme card?  Perhaps this might be a conflict.
    There are WiFi protocols like  IEEE 802.11a/b/g/n (with each letter signifying a different protocol).  I'm pretty sure the original AirPort card on worked on IEEE 802.11a/b.  That might be a problem.
    I have an old Tangerine iBook running 10.2.8, that I can't use anymore on WiFi because it couldn't handle the encryption. 
    I hope some of these might be helpful.
    Good luck.

  • Airport Extreme can see networks, can't connect to any

    I recently bought an iMac G4 (1Ghz, 17") on eBay and am having problems getting the Airport Extreme card to connect to any network. It came with 10.5.1 installed and I've updated it to Leopard 10.5.8
    I'm a bit of newbie with this Mac, but am learning quickly and I've tried to do my due diligence research prior to posting. I think I've tried every solution I've found recommended on forums for others with my problem.
    Here's the basic info on what I've tried (by themselves and various combinations):
    -changing the channel the network operates on.
    -changing from WEP to WPA
    -changing to no security at all
    -changing to manual DHCP setup
    -disabling Wireless-g only to allow b & g, and I've tried allowing only g
    -I tried moving AppleAirport.kext to the desktop to let the system rebuild it with a restart - it was not rebuilt so I moved it back in and restarted again
    -reset your router
    -made sure router firmware was up to date
    -creating a new network location
    -went to Library > Preferences to delete com.apple.internetconfigpriv.plist and com.apple.internetconfig.plist but there were no files with those names in that folder
    None of these options changed any response to the ways I've tried to connect to the internet.
    It connects fine through the router with an ethernet cable. With this option it takes the network address 192.168.1.5
    I also tried to connect to my neighbor's open network, with that network it will either timeout or ask me for a WEP password, which isn't needed.
    These are the errors I get when trying to connect to my own network wirelessly:
    -When I go through Network Setup Assistant, I get the error: "The password you entered is invalid." Even though I know it is correct (checked and rechecked to make sure all keys were working in a text file).
    -When I go through System Preferences > Network I get a Connection Timeout every time it tries to connect.
    -When I go through Network Diagnostics through Safari, it can't find any Apple Wireless Devices to work with or it gives me a connection timeout.
    My iPod Touch 2nd Generation has never had a problem connecting to this router or the neighbor's open network.
    Neither have any of my three Dell laptops.
    AirPort Card Information:
    Wireless Card Type: AirPort Extreme (0x14E4, 0x4E)
    Wireless Card Locale: USA
    Wireless Card Firmware Version: Broadcom BCM43xx 1.0 (4.170.25.8)
    Current Wireless Network: wireless network not available
    If it matters, I've got an Actiontec router and I'm connecting to Verizon FiOS.
    Thanks in advance for any recommendations. I guess if the Airport Extreme card [or software] won't work I'll just have to try a USB network adapter (want to avoid this as this iMac only has USB 1.1).
    Ed

    Hi there!
    Were any software install and restore discs included with the computer to support
    the license and ownership, maintenance and help upkeep the computer's OS X?
    Not sure where to begin in resolve the connection issues you have presented,
    since I am almost under siege in my offline life with problems others foist on me.
    Your issue may be in part due to a scenario where enabling WEP can causing
    an issue of a self assigned IP address; the address sometimes may be just a
    default and not that of the router's giving one to the computer. You can some-
    times reset and hope the router can give you a new different IP address or DNS.
    There usually is something else to this, if that is the case.
    However, to make sure the computer itself is in a good state of health, and you
    have some of the basic means at your disposal, (or to know what you have) is
    why I am replying. And once that is mostly a certainty, to see if the settings to
    choose the AirPort as a viable Network choice in the System Preferences, with
    wireless on top of the available options open to the computer. You can drag in
    order of desired connection type, the Ethernet, dialup, Airport, etc - means of
    making or sustaining a connection in the Network panel. If these items are not
    correctly chosen, the available wireless Airport won't work. And the status of
    the Airport connection won't be visible in the main menubar header either.
    Have you been through some of the several Apple Support documents on topic?
    • Mac OS X: Connect to the Internet, troubleshoot connection & set up small network:
    http://support.apple.com/kb/HT1714?viewlocale=en_US
    • Mac OS X: Troubleshooting a cable modem, DSL, or LAN internet connection:
    http://support.apple.com/kb/TS1317
    • AirPort troubleshooting guide (primarily settings & base station)
    http://support.apple.com/kb/HT1401?viewlocale=en_US
    For computer basics, to check and do simple software maintenance of the Mac
    OS X, you can boot the computer in SafeBoot (shift key held on startup until a
    login window appears) and from GO in main Finder window, see Utilities folder
    in the drop-down menu, and look for then launch Disk Utility from the Utilities.
    In Disk Utility, choose the Macintosh HD, then 'repair disk permissions'. You
    may be able to later click on the hard drive icon of the Brand of the HDD as
    seen in the same sidebar where the Macintosh HD was located, and choose to
    'verify' the hard disk drive from the choice in the Disk Utility panel then available.
    When done with these items in Disk Utility, quit it; then restart the Mac normally.
    {For other levels of Disk Utility repair on the hard disk drive, you need to boot the
    computer from the OS X Installer's disc#1 and choose Disk Utility from its menu
    bar prior to actually running that Installer. The drop down menu bar has options
    and select them carefully; since you can do quite a bit to the computer's drive if
    the wrong item is chosen out of turn or when not needed. A booted disk utility is
    in a position to act more thoroughly on a hard disk drive that is then unmounted.}
    If the computer is in a good state of preventative maintenance and permissions
    repairs, etc the main issue would be in the choice of settings to access the internet
    via the means at the computer's disposal; and choosing the hardware path in the
    Network panel of System Preferences is one of the main portals. There are several
    items in here, including being able to check-mark and move the order of importance
    the main items in a Network preference window, so the computer chooses them first.
    If the antenna cable and other connect to/from the AirPort card in the base of the iMac
    is properly pressed firmly into position and the card is OK, the physical and electronic
    paths should be assured; as far as that goes...
    Some of the changes to settings may not have been necessary or help in connecting;
    so I am not so sure what ones would need to be changed back to their defaults.
    Good luck & happy computing!

  • VPN to a Windows Network - can't connect to server using RDC

    I'm trying to connect to my office's windows network.
    I can connect using Cisco VPN but can't when I try to Connect to Server when specifying AFP or SMB as the path. I was told SMB is not supported and that I should just be able to use RDC once the VPN is established. RDC however is not connecting for me either. Any suggestions are greatly appreciated. Thnx

    Check your System Preference settings under sharing,
    if your firewall is on it may cause issues. Turn it
    off and see if that solves it for you. If not make
    sure you're using the latest client (4.9).
    Hi. Problem occurs with and without firewall on. I'm using Cisco VPN 4.9 too. I've been able to use RDC before which is weird. I'm not sure, but ever since the last Apple Security Update last week...I have been having this problem. But I'm not ruling out anything the IT dept. may be doing. :\

  • New airport express has error, now network can't connect to internet to

    Purchased new airport express to use solely for airplay, ran airport utility and there was an error. Now airport express is not recognized and wireless network (Fios router) has no internet connection.

    It's optional, but in my opinion, it would still be a good idea to perform the complete network power cycle that I outlined above.  This will give the network a "fresh start" and minimize the chances of an error occurring during the setup of the Express.
    Perform a Factory Default Reset as suggested by Tesserax above.
    Temporarily, locate the Express in the same room or close proximity to the Actiontec modem/router and power it on for a few minutes. Do not connect an Ethernet cable to the Express, as it will be configured using wireless.
    Click the WiFi icon at the top of the Mac's screen and look for a listing of New AirPort Base Station
    Click on AirPort Express just below that listing
    That will get the setup "wizard" running to take a minute to analyze the network and likely suggest that the Express be setup to extend the Actiontec network.
    Technically, it cannot do this, but it should be able to join the Actiontec network for use with AirPlay if the security settings on the Actionec are compatible with the Express.
    Enter a name that you want to call the Express and then click the Other Options button.
    Select the Add to an existing network option, if not already selected, and click Next
    Follow the prompts, making sure that the name of the network and password are entered correctly.
    If the setup is successful, you will see a message of Setup Complete and the Express will display a green light. Click Done and move the Express to the desired location and power it back up again.  The Express needs to be located where it can receive a good quality signal from the modem/router wireless.

  • Airport express connected to my existing network - Can I connect a device to the network through it's ethernet port?

    Is it possible when my airport express is wirelessly connected to my existing network - to connect a device to the network through it's ethernet port or is it wireless only at that point?
    I'm trying to connect my A/V Receiver in another room to my network without having to run a CAT5 cable all the way to the router.  I'd rather be able to connect it to my airport express if it will work that way.

    Is it possible when my airport express is wirelessly connected to my existing network - to connect a device to the network through it's ethernet port or is it wireless only at that point?
    Yes.....IF
    You have an AirPort Express 802.11"n" version configured to "join a wireless network" and you have enabled the option to "Enable Ethernet Clients"
    Or
    You have an AirPort Express 802.11"n" configured to "extend a wireless network" from another Apple "n" router, in which case the Ethernet port is enabled by default

  • Issue with connecting to encrypted network after logging in.

    I work for an academic institution and we have two networks that the students are able to access the web by; open and encrypted. We have made each computer in the library default to access the encrypted network through an app called Xpress Connect and a majority of them work properly. However, after logging off a user and then logging back in, some of the computers claim they are connected to the Encrypted network and have the proper IP, however are unable to access web pages. When system preferences is opened, the 802.1X encrypted network still has the button to connect to encrypted. When the button is pressed, internet access is gained.
    I have deleted the following files from Library>Preferences>System Configuration:
         com.apple.airport.preferences.plist
         com.apple.network.identification.plist
         com.apple.smb.server.plist
         NetworkInterfaces.plist
         preferences.plist
    Then I restarted the computer and manually set the preferences to connect to the Encrypted network. The same issue occured where it says I am connected but I have no internet access. I then click the connect button under the Network panel of System Preferences and then it finally works.
    Is there any way I can set the computer to automatically start the connection to the 802.1X encrypted network?

    You'll have to talk to the Xpress Connect people, perhaps it requires a update.
    Mac's connect automatically to encrypted networks if it's stored in the keychain, provided they are not hidden and not WEP Encrypted networks since that's worthless standard now.

  • Can I connect a wired device to access network?

    I have an Airport Express set up as "Join a Wireless network" Can I connect a wired device to the ethernet port of my AE so that it can access the network?

    The Ethernet port is normally enabled in the "Join" mode,  if you have one of the newer 802.11n models of the AirPort Express.
    If you have an older "b/g" version of the Express, the Ethernet port is not enabled in the "join" mode. Check the model number on the side of the Express. If you see A1084 or A1088, this is an older version of the Express.
    Test your current Express to see if the port is already enabled by temporarily turning off the wireless on a laptop and connecting the laptop to the Express using an Ethernet cable. See if you can get an Internet connection. If you can, you know the Ethernet port is working.

  • MacBook Pro can't connect to iPod via wireless

    Hi,
    I have a fresh installed Mac OS X 10.5.5 on my new MacBook Pro.
    Nothing was installed on it! no firewall, nothing! But i can't get connection to my iPod touch 2g.
    I can see my iPod via bonjour, it has an IP, but i can't successful ping it. When i start the application "Remote" on my iPod, i can see it in iTunes, can't connect to itunes either.
    What's wrong? On my other macbook i have no problem at all.
    Thank you very much

    I am having the same issue. If I plug an Ethernet cable into my Late 2008 MBP, I can connect to my iPod touch using any of the several apps, like Remote, AirSharing, 1Password, etc.
    However, I cannot connect to the ipod using the MPB's airport. Like the peter2k, I can't even ping the iPod. Other laptops on the same network can wireless connect and ping my ipod just fine.
    This is driving me nuts! Btw, prior to getting this laptop, I had an Early 2008 MBP that I used to connect to my ipod touch. I did a migration to this new MBP, but it has never been able to connect.

  • Lync 2010 Mobile client can't connect to the server. it may be busy or temporarily unavailable

    I have the following issue after renewed the Lync internal and external certificates, Lync Mobile client get the following message when try to connect from internal or external network "can't connect to the server. it may be busy or temporarily
    unavailable"
    PS I tried a lot of solutions from different articles, but the same result. 
    presented below my environment: 
    Two Lync 2010 frontend servers with one pool.
    Two edges server.
    HW load balancer.
    Log from Lync connectivity analyzer.
    User Name: [email protected]
    Logging test parameters:
    SIP Uri: [email protected]
    Discovery Type: Automatic Discovery
    Network access: NetworkAccessExternal
    Selected client: ApplicationLyncMobile2010
    Starting Lync server autodiscovery
    Please wait; this test may take several minutes to complete...
    Starting automatic discovery for secure (HTTPS) internal channel
    Sending HTTP request to
    https://lyncdiscoverinternal.xxx.com/[email protected]
    Exception encountered while sending an HTTP request to
    https://lyncdiscoverinternal.xxx.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to
    connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    An error occurred while sending the request.
    Unable to connect to the remote server
    An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:443
    For troubleshooting, try using a browser to open the server discovery URL
    https://lyncdiscoverinternal.xxx.com/[email protected]
    System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden
    by its access permissions 192.168.89.25:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    Server discovery failed for secured internal channel against
    https://lyncdiscoverinternal.xxx.com/
    Starting automatic discovery for unsecure (HTTP) internal channel
    Sending HTTP request to
    http://lyncdiscoverinternal.xxx.com/[email protected]
    Exception encountered while sending an HTTP request to
    http://lyncdiscoverinternal.xxx.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to
    connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    An error occurred while sending the request.
    Unable to connect to the remote server
    An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:80
    For troubleshooting, try using a browser to open the server discovery URL
    http://lyncdiscoverinternal.xxx.com/[email protected]
    System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden
    by its access permissions 192.168.89.25:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    Server discovery failed for unsecured internal channel against
    http://lyncdiscoverinternal.xxx.com/
    Starting automatic discovery for secure (HTTPS) external channel
    Sending HTTP request to
    https://lyncdiscover.xxx.com/[email protected]
    Exception encountered while sending an HTTP request to
    https://lyncdiscover.xxx.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect
    to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    An error occurred while sending the request.
    Unable to connect to the remote server
    An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:443
    For troubleshooting, try using a browser to open the server discovery URL
    https://lyncdiscover.xxx.com/[email protected]
    System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden
    by its access permissions 192.168.89.25:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    Server discovery failed for secured external channel against
    https://lyncdiscover.xxx.com/
    Starting automatic discovery for unsecure (HTTP) external channel
    Sending HTTP request to
    http://lyncdiscover.xxx.com/[email protected]
    Exception encountered while sending an HTTP request to
    http://lyncdiscover.xxx.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect
    to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    An error occurred while sending the request.
    Unable to connect to the remote server
    An attempt was made to access a socket in a way forbidden by its access permissions 192.168.89.25:80
    For troubleshooting, try using a browser to open the server discovery URL
    http://lyncdiscover.xxx.com/[email protected]
    System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden
    by its access permissions 192.168.89.25:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    Server discovery failed for unsecured external channel against
    http://lyncdiscover.xxx.com/
    None, AutoInternalSecureD, AutoInternalUnsecureD, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST,
    MobilityMCXInternalLMXCheckGET, MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
    Automatic discovery of the Lync server failed. Please verify the server requirements at
    http://go.microsoft.com/fwlink/?LinkId=278998 . Lync mobile apps do not require automatic discovery. You could enter the server FQDN manually and test connectivity again.
    Microsoft Lync Connectivity Analyzer cannot analyze deployment readiness until a discovery test has completed successfully.

    Hi 
    Is that Port 443 opened? check the fire wall.
    is that external Lync clients are logging in with out any issues.
    by seeing the Log it is unable to connect on port 443
    Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made
    to access a socket in a way forbidden by its access permissions 192.168.89.25:443
    For troubleshooting the Mobility issues follows this
    http://blogs.technet.com/b/nexthop/archive/2012/02/21/troubleshooting-external-lync-mobility-connectivity-issues-step-by-step.aspx
    Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

  • Mobile phone Can't connect to the Notebook Microsoft Virtual WiFi Miniport Adapter

    1. Create Microsoft Virtual WiFi Miniport Adapter 
              1.1 netsh wlan set hostednetwork mode=allow ssid=NETWORK key=password keyUsage=persistent 
              1.2. netsh wlan start hostednetwork
    2. Connect Network Sharing--open
    3. phone using wifi to connect the network
    can't connect ,wha's wrong? notebook can surf through Ethernet connection.
    If i set a static ip in the mobile phone which is the same net section like the Microsoft Virtual WiFi network, DNS:8.8.8.8 . Then can connected, but can't surf, anybody can give me some helps?
      Ethernet connection:
    1. ADSL dail mode
    2. Static IP is setted
    3. DNS is setted

    Hi midource,
    Please update your wireless network adapter driver for good measure.
    Check your phone connection properties see if it could get IP address from your computer properly.
    Static IP doesn’t mean your phone has connected to network, if you set static IP the connection will show connected but without internet.
    This issue could be caused by incompatible hardware with Virtual Wifi Miniport Adapter hotspot, especially on some android devices.
    But we still could do some configuration changing and give it a try.
    Check properties of your adapter Ethernet connection->sharing, check “Allow other network to connect through…” and “Allow other network users to control…”
    Tight click Ethernet connection-> properties->Advanced (advanced settings might be different depends on WIFI adapter manufacturer)
    Disable 802.11n mode
    Disable 40 Mhz Bandwidth Compatibility Mode
    Run Netsh command you mentioned above as administrator.
    Disable firewall temporarily.
    Check your issue again after re-enable your Virtual Wifi Miniport connection.
    If the issue still persists
    Please try other devices on your Windows 8.1 Virtual WIFI Miniport Adapter hotspot. If they works check compatibility issue with your phone manufacturer or set a router for network sharing.
    Regards
    D. Wu

Maybe you are looking for