Wireless Clients cannot communicate to eachother.

I have a 871W router that I am having trouble getting wireless clients to communicate.
I can ping and use applications from any wired client to any wireless device. However I am unable to ping or use any other protacol from one wireless device to another.
I have confirmed that there is no firewalls on the endpoints blocking communication.
I have removed ACLs on the BVI1 interface but that had no affect.
Any assistance would be greatly appreciated.
Current configuration : 7670 bytes
version 12.4
no service pad
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
service sequence-numbers
hostname cc-fw-router
boot-start-marker
boot-end-marker
logging buffered 51200 debugging
enable secret 5 $1$crkU$2cWtWnMRjMvfo4ADb4pfi0
aaa new-model
aaa authentication login default local none
aaa session-id common
resource policy
clock timezone PCTime -5
clock summer-time PCTime date Apr 6 2003 2:00 Oct 26 2003 2:00
ip subnet-zero
no ip source-route
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 10.10.10.1
ip dhcp excluded-address 10.10.20.1
ip dhcp pool sdm-pool1
   import all
   network 10.10.20.0 255.255.255.0
   default-router 10.10.20.1
   dns-server 192.168.2.244 8.8.8.8
ip dhcp pool xbox
   host 10.10.20.20 255.255.255.0
   hardware-address 0100.1dd8.5b52.73 ieee802
   dns-server 192.168.2.251 4.2.2.2
ip inspect name DEFAULT100 cuseeme
ip inspect name DEFAULT100 ftp
ip inspect name DEFAULT100 h323
ip inspect name DEFAULT100 icmp
ip inspect name DEFAULT100 netshow
ip inspect name DEFAULT100 rcmd
ip inspect name DEFAULT100 realaudio
ip inspect name DEFAULT100 rtsp
ip inspect name DEFAULT100 esmtp
ip inspect name DEFAULT100 sqlnet
ip inspect name DEFAULT100 streamworks
ip inspect name DEFAULT100 tftp
ip inspect name DEFAULT100 tcp
ip inspect name DEFAULT100 udp
ip inspect name DEFAULT100 vdolive
ip tcp synwait-time 10
no ip bootp server
ip domain name yourdomain.com
ip name-server 4.2.2.2
ip ssh time-out 60
ip ssh authentication-retries 2
crypto pki trustpoint TP-self-signed-1816499983
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-1816499983
revocation-check none
rsakeypair TP-self-signed-1816499983
crypto pki certificate chain TP-self-signed-1816499983
certificate self-signed 01
30820252 308201BB A0030201 02020101 300D0609 2A864886 F70D0101 04050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 31383136 34393939 3833301E 170D3038 30323039 32313436
31395A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D31 38313634
39393938 3330819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100BD37 F594F5B4 726A60BA 2C99B43C 0DE6814A 17BB53C2 A2202828 D6AA7774
7E3FF99D 7A6B06D8 C7A52D0E 2989CF78 F5E892C0 9A9DA783 1E6C8B59 6F8B01D7
1E631226 D372D65B 6E72CA49 D572FEA6 26131F83 32F87678 4B13735F 383D9F65
287E2CE3 46459CAD 582DB438 6E599885 BAE48719 4AC9EB73 8BC32114 C6C637C9
80350203 010001A3 7A307830 0F060355 1D130101 FF040530 030101FF 30250603
551D1104 1E301C82 1A63632D 66772D70 65746572 2E796F75 72646F6D 61696E2E
636F6D30 1F060355 1D230418 30168014 391859D0 F5A8499D 8EF185B7 DC937161
7F2B7CBA 301D0603 551D0E04 16041439 1859D0F5 A8499D8E F185B7DC 9371617F
2B7CBA30 0D06092A 864886F7 0D010104 05000381 8100BC17 189FF9F1 01349085
70E363E9 47AB7A9A 6F80498B D8F727DF 687CC37E 8FF3024F 30451A97 C4C81676
C2FCA1A0 2B51D091 AA0B44E7 BA7FCA6A ED98CF5F 3EE60AD4 AB79DB09 BBE94F64
C83FB22E 8936E561 C84AF542 DB4756E3 6EF31359 4210262A 43D2E1F7 15DD3E32
15278156 9569D8BE 5EC38773 9A2EFB63 11C55FFD 93B4
quit
username user privilege 15 secret 5 $1$wVlg$THSMUBnF3f3A3o2Oh18xS/
username ccadmin password 7 09774C051612111B180439
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
crypto isakmp key 01234567890123456789 address 96.252.99.66 no-xauth
crypto ipsec transform-set ESP-3DES-SHA1 esp-3des esp-sha-hmac
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto map SDM_CMAP_1 1 ipsec-isakmp
description Tunnel
set peer OFFICEVPN IP
set transform-set ESP-3DES-SHA1
match address 103
bridge irb
interface FastEthernet0
interface FastEthernet1
interface FastEthernet2
interface FastEthernet3
interface FastEthernet4
description $FW_OUTSIDE$$ES_WAN$
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip virtual-reassembly
ip route-cache flow
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 1
interface Dot11Radio0
no ip address
encryption mode ciphers tkip
ssid my_home
    authentication open
    authentication key-management wpa
    guest-mode
    wpa-psk ascii 7 133E1413181F0138273D15
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
station-role root
no dot11 extension aironet
bridge-group 1
bridge-group 1 spanning-disabled
interface Vlan1
description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$$FW_INSIDE$
no ip address
ip virtual-reassembly
bridge-group 1
interface Dialer0
description $FW_OUTSIDE$
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1452
ip nat outside
ip virtual-reassembly
encapsulation ppp
ip route-cache flow
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication chap pap callin
ppp chap hostname verizonfios
ppp chap password 7 01050316521109012745411A
ppp pap sent-username verizonfios password 7 120F00051B11030A2C222B3B
crypto map SDM_CMAP_1
interface BVI1
description $ES_LAN$$FW_INSIDE$
ip address 10.10.20.1 255.255.255.0
ip access-group 100 in
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1200
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer0
ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip nat inside source route-map SDM_RMAP_1 interface Dialer0 overload
ip nat inside source static udp 10.10.20.20 88 interface Dialer0 88
ip nat inside source static tcp 10.10.20.20 3074 interface Dialer0 3074
ip nat inside source static udp 10.10.20.20 3074 interface Dialer0 3074
logging 10.10.20.27
access-list 1 remark INSIDE_IF=BVI1
access-list 1 remark SDM_ACL Category=2
access-list 1 permit 10.10.10.0 0.0.0.255
access-list 1 permit 10.10.20.0 0.0.0.255
access-list 100 remark auto generated by Cisco SDM Express firewall configuration
access-list 100 remark SDM_ACL Category=1
access-list 100 deny   ip host 255.255.255.255 any
access-list 100 deny   ip 127.0.0.0 0.255.255.255 any
access-list 100 permit ip any any
access-list 103 remark SDM_ACL Category=4
access-list 103 remark IPSec Rule
access-list 103 permit ip 10.10.20.0 0.0.0.255 192.168.2.0 0.0.0.255
access-list 103 permit ip 10.10.20.0 0.0.0.255 10.1.1.0 0.0.0.255
access-list 110 deny   ip 10.10.20.0 0.0.0.255 10.1.1.0 0.0.0.255
access-list 110 deny   ip 10.10.20.0 0.0.0.255 192.168.2.0 0.0.0.255
access-list 110 permit ip 10.10.20.0 0.0.0.255 any
access-list 120 remark Xbox
access-list 120 permit tcp any eq 88 host 10.10.20.20 eq 88
access-list 120 permit tcp any eq 3074 host 10.10.20.20 eq 3074
access-list 120 permit udp any eq 3074 host 10.10.20.20 eq 3074
dialer-list 1 protocol ip permit
snmp-server community public RO
no cdp run
route-map SDM_RMAP_1 permit 1
match ip address 110
control-plane
bridge 1 protocol ieee
bridge 1 route ip
banner login ^CAuthorized access only!
Disconnect IMMEDIATELY if you are not an authorized user!^C
line con 0
no modem enable
transport output telnet
line aux 0
transport output telnet
line vty 0 4
privilege level 15
transport input telnet ssh
scheduler max-task-time 5000
scheduler allocate 4000 1000
scheduler interval 500
end

see the option "client Isolation"in the Ap
Posted by WebUser Anshul Rohilla

Similar Messages

Wireless clients cannot get ip address

I have 7 WLANs configured all work fine but the latest. The 7th WLAN I configured will not let clients get an IP address. I can plug a wire into the port with the same VLAN configured on the port and I get an IP address but wireless clients connected to an AP on that port cannot get an IP adddress. Any suggestions would be appreciated.

Hello,
where is the DHCP server configured?
- do all other 6 WLAN's work fine with the same DHCP server.
- do you have any H-REAP VLAN mapping , or AP groups configured?
they will override the WLAN-interface configuration.
Kind regards
Talal
=======
please rate answers that you find useful , and mark as answered - when it is :-) - so others can find it easily

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

How do I enable two wireless clients to communicate with each other?

I have a WRT54GL with the latest firmware. I have two computers which are both connected to the router, with IP addresses assigned via DHCP. Neither has a firewall running. I cannot get them to communicate with each other -- even ping doesn't work. I can ping the router itself using the IP address assigned to it on the WAN side by my ISP. Both computers have no problem reaching the internet through the router.
What settings on the router will enable the communication to occur? I can't find anything in the router's user interface which appears to control this.
Thanks.
Solved!
Go to Solution.

Hi annie25,
I think it would be best to check on netgear or belkin technical forums how to make these two talk.
Yesterday is history. Tomorrow is mystery. Today is a gift.

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?!

Flexconnect AP(Local Switching) Wireless clients are not able communicate eachother

Hi,
Scenario : We are deployed the WLC in Corparate Office and Access Points are placed in Branch Office with FlexConnect Local Switching mode.
In this case, I am not able to Ping the Wireless clients eachother . Peer to Peer Block Option also Disabled.
Some time Wireless clients Ping eachother & some times not. Both Wireless clients are associated with Same AP & Same WLAN SSID.
Please help me urgent ..
Devices :
1)WLC 2500 series , Software 7.2
2)Cisco 1400 series APs
3)CISCO ACS server for AAA authentication
Regards,
Shanmugam Nachimuthu

Hi Shanmugam,
Please apply following steps to configure P2P setting for WLAN:
Step 1 Choose WLANs to open the WLANs page.
Step 2 Click the ID number of the WLAN for which you want to configure peer-to-peer blocking.
Step 3 Choose the Advanced tab to open the WLANs > Edit (Advanced) page.
Step 4 Choose one of the following options from the P2P Blocking drop-down list:
• Disabled — Disables peer-to-peer blocking and bridges traffic locally within the controller whenever possible. This is the default value.
NOTE: Traffic is never bridged across VLANs in the controller.
• Drop—Causes the controller to discard the packets.
• Forward - Upstream — causes the packets to be forwarded on the upstream VLAN. The device above the controller decides what action to take regarding the packets.
NOTE: To enable peer-to-peer blocking on a WLAN configured for FlexConnect local switching, select Drop from the P2P Blocking drop-down list and select the FlexConnect Local Switching check box.
Step 5 Click Apply to commit your changes.
Step 6 Click Save Configuration to save your changes.
Thanks,
Prashant Gondaliya

I cannot get my Airport Express to accept wireless clients.

I cannot get my Airport Express to accept wireless clients. After resetting to factory default and reconfiguring, it works briefly but then stops again.
The Airport Express is on the second floor of my house and is seen by Airport Utility. Using a LAN cable with the Express works no problem.
My network is created by an Airport Extreme (ground floor) and extended by a Time Capsule (first floor)
Have run through all settings repeatedly and as I said I can get it to work briefly by resetting and then reconfiguring, but after a short while again my iOS devices can no longer connect and revert to cellular.

I cannot get my Airport Express to accept wireless clients. After resetting to factory default and reconfiguring, it works briefly but then stops again.
The Airport Express is on the second floor of my house and is seen by Airport Utility. Using a LAN cable with the Express works no problem.
My network is created by an Airport Extreme (ground floor) and extended by a Time Capsule (first floor)
The issue is most likely due to the fact that the AirPort Express may be too far from the AirPort Extreme to properly extend it with enough bandwidth to be useful.
It is important to understand that with Apple 802.11n or 802.11ac base station an extended network works in a wheel-like fashion with the base station to be extended at the hub and each extending base station along one of the spokes. This type of configuration does not allow for daisy chaining the base stations. That is, in your case, both the Time Capsule and AirPort Express are attempting to extend the AirPort Extreme.
Each extending base station must be within a certain signal quality range in order to extend the network properly. Please check out the following AirPort User tip for details.

Deskjet F4500 Printer cannot communicate wirelessly after Mac 10.8 update

Installed Mountain Lion update
Printer cannot communicate wirelessly (blue light blinks)
Uninstalled HP Software
Reinstalled software using usb cable, otherwise printer not recognized.
Software successfully installed
Ran software update
New HP Software installed 2.9
Printer still connected with usb cable and is recognized in Printer preferences as idle
Box checked to configure device for wireless network
Directed to use usb cable to configure (it already is)
clicked continue
Hp Installer determines that computer is connected to a wireless network
correct net name indicated
wep password entered
looking for network
Get the following message:
Device not connected
To configure the network settings of the selected device, please connect it temporarily via usb. The device can be disconnected from the usb once the network setting are transferred
click okay, but cannot continue because printer is already connected by usb.
Ran wireless net test by pressing scan button
No filtering FAILS
I can print using USB cable
Any help?

When it is indicated that the printer is offline - is it? Check the front of the printer in the wireless menu to tell (print a wireless network test).
If it is still connected to the Belkin, I suspect the Belkin does not support Bonjour (mDNS) properly so your Mac cannot find the printer.
Also, you do not want to use the CD, anyway. It is outdated and will not support 10.8. Download and install the latest software for your printer from the "Support & Drivers" link at the top of this page.
Try this sequence:
Download and install this: http://support.apple.com/kb/DL907
Restart your Mac.
Reset the printing system:
- Go to System Preferences > Print & Scan
- Right (or control) click in the rectangle listing your printers and select Reset Printing System.
WARNING - this will delete ALL of your printers!
- Select the plus sign to re-add a printer. Select the Defualt tab on the top of the window. Look for the printer, select it and wait until the "Add" button becomes available. Click it.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Cannot "Add Wireless Client"

I have been using iMac for years and worked well with my Airport Express. Yesterday, one of my friends brought a notebook running Windows Vista to my house and wanted to connect his machine to my airport wireless network, but it failed. I want to know if there is anything I need to do so that I can allow another pc connecting to my network? I've read through almost all docs I could find in the apple web site; when I followed one of them by opening Airport utility and tried to click on the "Add Wireless Client", I found this option is dimmed and not able to click on it? Could someone help me? thanks a lot.

That is only an option if you are using MAC address filtering. Since you are not, you don't have to worry about that.
Is your AirPort Express (AX) set to 802.11n operation only? If so, is this Windows laptop capable of 802.11n? If not you will need to configure the AX to a 802.11b/g compatible mode.
What type of wireless encryption are you using? Is this Windows laptop compatible with that?
If you are outside the US, try configuring the AX to use a channel between 1 and 11.

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

Jabber for Mac 9.2.1 Cannot communicate with the server

Hi All,
I'm using Webex and the Jabber for Mac 9.2.1 client that was automatically pushed. I see "Cannot communicate with the server" when I attempt to login.
The same credentials work correctly when using the 8.6.5 client version. I've attached the problem report file.
I would appreciate some guidance on what I need to do to get this to work.
Cheers,
Steve

We've seen this with a few of our users as well. All started noticing having issues Friday morning. As this is a hosted service for us via webex we had our engineers call in to Jabber support. Cisco performed a modification to their account and they were able to connect again. No SRV records were messed with.
***EDIT*** - This appears to have been caused by a certificate issue. The Trusted Root Certificate for QuoVadis expired and was not renewed on some machines.
Go here: https://www.quovadisglobal.com/QVRepository/DownloadRootsAndCRL.aspx
Install the Cert for : QuoVadis Root CA2 (in windows, download as DER>right click file>install)
Jabber should connect now. The issue was in SSL validation with the appropriate hosted servers.

New 2012 R2 domain - xp clients cannot join or print

I just migrated a 2003 domain to 2012 R2.   Things were working ok & then XP clients became AD stupid.
Steps I took:
Added a VM 2012 R2 DC to the domain. Server had DNS installed. Ran dcdiag & bpa and resolved any issues.
About a week later I moved all roles over to the VM DC.
Tore down one of the NT2003 DCs (not VM) and rebuit it as a 2012 R2 DC w/DNS. Ran dcdiag & bpa and resolved any issues. Had problems with DNS scavenging removing some static records. readded records & made sure the "Delete
record when it becomes stale" was unchecked on all static records (all fwd & rev zones).
Moved all roles from the VM DC to the hardware DC.
After a week I tore down the 2nd (& last) nt2003 DC (not VM) and rebuilt it as a 2012 R2 DC w/DNS. Ran dcdiag/bpa and fixed any issues. Also ran it on the other DCs.
Removed the VM 2012 R2 DC from the domain (demote, remove features, remove from domain, power off, delete VM).
Everything seems to be working fine. dcdiags look clean, event logs seem good.
Bump forest/domain to 2012 R2 native.
Then, a few days later, it goes bad. I (after hours) install all accumulated updates on both DCs. Reboot both.
Next AM a user calls. Her thin client cannot connect to the terminal services server. DNS has deleted its dns record, even though the delete when stale was unchecked. :| So I readd the static record and turn off scavenging.
Problem solved.
Next call s from a XP user (we have XP, Win 7, and thin clients). She cannot print. Printers show "cannot connect". Try various things to no avail. Check Win 7 boxes and they're working fine & printers are connected.
Note that the XP & Win7 boxes all pull their DHCP address from the same dhcp server/scope.
Review error logs and run dcdiag. There are several somewhat esoteric errors. After several hours or tail chasing I decide to take a more scorched earth tack. I demote the 2nd DC and remove AD & DNS from it. After demotion and role
removal I check AD and it still shows the DC. I remove the now just a server from the domain. Clean up DNS & AD removing all traces. This takes a while as I have to run variuos scripts (tahnk you google) to ensure AD is clean.
Run dcdiag and resolve issues. Even a detailed dcdiag comes out clean. Replication tests show the old server is now forgotten.
Check XP boxes and they still show printers as "cannot connect".
Remove a XP PC from the domain. Try to rejoin and I get a error. Rename it and still get the error. I can ping, nslookup, etc and they return the correct IP.
I've tried the simple change the join a domain in system properties. That gives a somewht non descript error. The network identification wizard seemed to find the domain but didn't work. As it was trying to find the PC in AD, I went ahead
and added it via AD users& Computer console. Run the wizard and it tells me it found the record in AD. It then says "a domain controller for the domain [ourdomain] could not be contacted." !? Yet the prior screen it told
me it had found the record for the PC on the DC.
nslookup for ourdomain.local as well as dcname.ourdomain.local resolve correctly. Tried chenging the PC to static - no change. Rename the old win 2012 R2 dc (now just a server outside the domain), reboot, and the try to rejoin the domain.
Works flawlessly.
BTW - We're running tcpip w/o netbios over tcpip.
So basically my XP boxes cannot use AD printers and cannot join the domain. IDK if they're picking up gp updates (I'll check in the AM), but I suspect they're not.
Short of buying a truckload of Win 7 licenses and reloading OSs, what can I do to fix this?
Details on the XP box error (fyi - I did a record to record comparison to a Win 2008 domain's SRV records and they look identical (except, fo course, the domain& server names)) :
The domain name [ourdomain] might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain [ourdomain]:
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.[ourdomain]
Common causes of this error include the following:
- The DNS SRV record is not registered in DNS.
- One or more of the following zones do not include delegation to its child zone:
[ourdomain]
. (the root zone)
For information about correcting this problem, click Help.
dcdiag /test:dns results
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = Domctl1
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\DOMCTL1
      Starting test: Connectivity
         ......................... DOMCTL1 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\DOMCTL1
      Starting test: DNS
         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... DOMCTL1 passed test DNS
   Running partition tests on : DomainDnsZones
   Running partition tests on : ForestDnsZones
   Running partition tests on : Schema
   Running partition tests on : Configuration
   Running partition tests on : [ourdomain]
   Running enterprise tests on : [ourdomain].local
      Starting test: DNS
         Test results for domain controllers:
            DC: Domctl1.[ourdomain].local
            Domain: [ourdomain].local
               TEST: Dynamic update (Dyn)
                  Warning: Failed to delete the test record dcdiag-test-record in zone [ourdomain].local
               Domctl1                      PASS PASS PASS PASS WARN PASS n/a
         ......................... [ourdomain].local passed test DNS

I see the following errors:
"TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing
connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period
to elapse between successive connections from a given local endpoint to a given remote endpoint."
Please read that: http://social.technet.microsoft.com/Forums/windowsserver/en-US/d770e9fd-53a2-4ae9-99b3-2754c4564592/tcpip-connection-issue-on-windows-server-2008-sp2?forum=winserverPN
"DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols; requested by PID      b70 (C:\Windows\system32\dcdiag.exe)."
As you can see, it is pointing to 8.8.8.8. You need to make sure that public DNS servers are configured as forwarders and not in IP setting of your DCs. Better if you could use your ISP DNS servers as public ones instead of 8.8.8.8.
Please read this Wiki article for recommendations about IP settings: http://social.technet.microsoft.com/wiki/contents/articles/18513.active-directory-replication-issues-basic-troubleshooting-steps-single-ad-domain-in-a-single-ad-forest.aspx
" TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone [ourdomain].local
Warning: Failed to delete the test record dcdiag-test-record in zone [ourdomain].local
[Error details: 9505 (Type: Win32 - Description: Unsecured DNS packet.)]
Here, you need to make sure that only secure DNS updates are allowed if you would like to secure dynamic updates. This is detailed in here:http://social.technet.microsoft.com/wiki/contents/articles/21984.how-to-secure-dns-updates-on-microsoft-dns-servers.aspx
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password

Hi can anyone help me. I have a apple macbook laptop OSX 10.5.8 . When i push print, it shows my printer but says cannot communicate with printer. (epson stylus nx125). Do I need new drivers? Please help . regards Cindy

Hi can anyone help me. I have a apple macbook laptop OSX 10.5.8 . When i push print, it shows my printer but says cannot communicate with printer. (epson stylus nx125). Do I need new drivers? Please help . regards Cindy

Welcome to Apple Support Communities. We're users here and do not speak for "Apple Inc."
Some basic printer troubleshooting steps before worrying about a printer driver:
1. Have you tried turning the printer off and back on?
2A. Is the printer attached with a cable?
     If yes, have you tried unplugging and re-plugging both ends of the printer cable?
     If that does not help, can you test the printer with another cable?
2B. If your printer is not connected to the computer with a cable, have you tried restarting your printer (assuming wireless connection)?
     Have you tried restarting your wireless router?
3. Have you tried restarting your MacBook? (Be sure to save your work first.)
4. Does the printer have ink? (Doesn't usually generate a 'communications error' though)
5. Have you updated OS X or the program you're trying to print from recently?

Either there is no default mail client or the current mail client cannot .....

Windows7 Ultimate 64 bits, Office 2013 32 bits.
My issue is that running Outlook 2013 I get the message
Either there is no default mail client or the current mail client cannot fulfil the message request. Please run Microsoft Office Outlook and set it as the default mail client.
OK, so this should be straight forward:
I set outlook at the default mail client and associate all file with it from Outlook\File\Option. Nope. That does not work.
I go through default programs and set the default mail client as Office 2013 and associate all file with it from Outlook.   Nope. That does not work.
I check the registry and it shows that the 64 bit or 32 bit reversion is the default mail client. So that does not help.
I install the 64 bit version instead of the 32 bit version. Nope. That does not work.
I clean the registry and temp file. Nope. That does not work.
I tried: Uninstalled with the Microsoft
fix uninstall and reinstall. This does not work.
Contact the phone technical support. This
does not work.
Addin,s does not work. Adobe, iCloud Addin .... does not work.
'Send email to'   menu does not work.
No application communicates with
Outlook, no Microsoft or third apps.
I can only send and receive emails
from within Outlook.
This program is lousy, any
possibility that my money back.
Thanks
Has anyone got any ideas?   All the suggested fixes on this forum do not fix this issue.

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Best Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Wireless clients unable to access internet on new WRT54G - Help!

I have multiple wireless clients that cannot access the internet. They all get valid IP addressing. I can ping the router. But I can't access anything on the internet. I just setup this router and I do this sort of stuff for a living and I give up. It shouldn't be this difficult. Two of the clients are Vista and the other is XP. Again, the connection to the router is perfect. I just can't access anything beyond the router. The single wired client works fine. Help!

Thanks... I've tried that. All of these hosts were actually working just fine with my old DLink router, but that router died over the weekend, so I replaced it with the Linksys. For the life of me, I can't see any reason why these hosts can't route out to the internet.

Wireless Clients cannot communicate to eachother.

Similar Messages

Maybe you are looking for