1130 AP unable to connect to controller

I am trying to get an 1130 AP to connect to the controller, but it seems to be having trouble connecting via DNS discovery. I have cisco-lwapp- controller entered into DNS, and if I plug a laptop into the same switch port the AP uses, I am able to ping the controller by name. On some subnets, the AP has no problem connecting, but on others is unable to connect. If I look in the DHCP scope, I see that option 15 is set on the subnets that work and is not set on the subnets that don't work. Option 15 is not listed as required in any of the documentation, but it seems it may be needed. Has anyone else experienced this problem?

Option 15 is required for the AP to know what suffix to add to cisco-lwapp-controller to do the resolution. So if your option 15 is cisco.com, it would look up cisco-lwapp-controller.cisco.com
hope thie helps,
- Eric

Similar Messages

Yoga 2-830f - Unable to connect duelshock 4 controller using bluetooth.

As the title says I am unable to connect my duelshock 4 controller to my Yoga 2 via bluetooth. Has anyone got any ideas why this might be. Also on another note is the lenovo support site broken for anyone else? I am having multiple issues with loading boxs not loading when I select the option of contact us. Also I just added my tablet and it says my warrenty ends in november even though i bought the tablet in febuary this year!

This has been resolved .
There was network issue around hence we could not set up the connection .
We just had to open the firewall port with the crm on demand application and wallla.
Regardas
Rohan Lotlikar
+919673584623

Unable to connect on premises build controller to Visual Studio Online account

I've been looking into VSO for our build process, but I'm having some difficulty on the basic set up.
We use Unity3D and would require an on premises build controller. I've created a VM and attempted to set up a build controller using this article for details:
http://msdn.microsoft.com/en-us/library/ms181712.aspx
I'm able to open the build service configuration wizard and I get to the "Connect to Team Project Collection" window. However, when I attempt to add my server, using my username and password (which is also the global admin), I get a TF31003 error.
I've verified that I have build permissions, but I keep getting this error everytime I attempt to connect the controller to VSO.
I also attempted to use a custom build account, which had Build Service and Build Administrator membership. It also got the same error.
What could be causing this issue?

Hi Jason,
Thanks for your post.
Please follow the detailed steps in this
article to configure and connect On-premise Build Service for your VSO account, if still receive the same issue, please share you received the error under which detailed step.
When connecting to VSO account in Build Service, you need provide the user which added in your VSO account.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

[Solved] Samba log spam: Unable to connect to CUPS server

Hi everyone,
I'm running into an annoying issue with samba. I don't have any printers installed, and probably won't. However smbd complains to no end in /var/log/errors.log about not being able to connect to a cups server:
Apr 18 12:30:05 asakura nmbd[4361]: *****
Apr 18 12:30:05 asakura nmbd[4361]:
Apr 18 12:30:05 asakura nmbd[4361]: Samba name server ASAKURA is now a local master browser for workgroup MYGROUP on subnet 192.168.1.121
Apr 18 12:30:05 asakura nmbd[4361]:
Apr 18 12:30:05 asakura nmbd[4361]: *****
Apr 18 12:32:22 asakura smbd[4552]: [2009/04/18 12:32:22, 0] printing/print_cups.c:cups_connect(103)
Apr 18 12:32:22 asakura smbd[4552]: Unable to connect to CUPS server localhost:631 - Connection refused
Apr 18 12:32:22 asakura smbd[4553]: [2009/04/18 12:32:22, 0] printing/print_cups.c:cups_connect(103)
Apr 18 12:32:22 asakura smbd[4553]: Unable to connect to CUPS server localhost:631 - Connection refused
Those last two lines get spammed constantly.
I've done a little bit of research into the matter, and followed the steps here to try to resolve the problem: http://www.davekb.com/browse_computer_t … server:txt
Unfortunately it doesn't appear to make any difference.
Here is my /etc/samba/smb.conf:
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = MYGROUP
# server string is the equivalent of the NT Description field
server string = Samba Server
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = no
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
; [homes]
; comment = Home Directories
; browseable = no
; writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
; [printers]
; comment = All Printers
; path = /var/spool/samba
; browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writable = no
; printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[shared]
path = /media/shared
valid users = foosoft
public = no
writable = yes
[tomato]
path = /media/data1/tomato
valid users = foosoft
public = no
writable = yes
show add printer wizard = no
printing = none
printcap name = /dev/null
disable spoolss = yes
I'm totally out of ideas here, anyone have a tip on what I could try next?
Last edited by FooSoft (2009-04-18 19:52:28)

glad you posted it first i had the same problem.
However, samba was complaining that
printing = none
was invalid. I removed that line and it works great.
thanks
Last edited by lio (2009-10-16 00:20:14)

Suddenly unable to connect to wireless network...exhausted all fixes

I’ve got an odd problem with my two-week old MacBook Pro and its connection to my wireless network. I’ve done what I think is pretty exhaustive troubleshooting, but remain baffled. Here’s the story.
This morning I connected to my wireless network (DSL 2WIRE modem/router) with no problem. This afternoon I returned and Airport refused to connect, giving me the error message, “Airport is unable to connect to the wireless network…” The network shows up as being available, but when I attempt to connect, it wont. (I didn’t make any changes or install any programs this morning).
Here’s what I’ve done:
[1] Restarted the router
[2] Repaired permissions
[3] Deleted the network’s entry in Keychain Access
[4] Re-entered my WEP code (assuring it is in correctly; I’ve tried both with the “$” and without)
[5] Used interface robustness and without.
[6] Attempted to join the network from the System Preferences>Network.Airport route.
[7] Created a new account and tried connecting.
Other tidbits of information:
[1] Another MacBook in the house connects to the network with no problem.
[2] My MacBook can connect to another (unsecured) network that I can “see” in my house.
So, it would seem my Airport card is working okay.
Any ideas??

Some more info (in case anyone is listening...)
I tried turning off the WEP code and could connect. (Since I share files on my home network, this isn't a "solution").
I also tried Resetting the MacBook Pro System Management Controller (SMC)(See: http://docs.info.apple.com/article.html?artnum=303319). I did this (I think -- there wasn't any indication that the reset "took"), but alas -- no luck.
I gave Apple Care a call, but the support guy, while courteous and all, didn't have anything to offer other than telling me to take it in to an Apple Store for a repair (clearly it isn't a hardware issue).
Heeellllppppp!

Unable to connect to LAN - Integrated 10/100BASE-T Ethernet LAN (RJ-45 connector)

Unable to connect to LAN, downgraded laptop from Windows 8 to Windows 7 64-bit. Have tried using the HP device identifier, and installing all drivers under Network for the laptop on WIndows 7, though none of them showed as being for Local Area Network.I also tried following this thread: http://h30434.www3.hp.com/t5/Wireless-Internet-Home-Networking/Integrated-10-100BASE-T-Ethernet-LAN-RJ-45-connector/td-p/4040756Downloaded the suggested drivers there for the HP Envy 17t-j100I also tested downloading the drivers here for Windows 7: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=7&Level=5&Conn=4&DownTypeID=3&GetDown=false Neither worked, I am still only able to connect via Wi-Fi, but not via LAN with actual cable attached.In case necessary, hardware ID for the Realtek PCIe FE Family Controller:
PCI\VEN_10EC&DEV_8136&SUBSYS_1854103C&REV_05PCI\VEN_10EC&DEV_8136&SUBSYS_1854103CPCI\VEN_10EC&DEV_8136&CC_020000PCI\VEN_10EC&DEV_8136&CC_0200

Hi: You can use all of the W7 x64 drivers and software from the HP 2000t-2a00 on your model except the BIOS and firmware files. Make sure you install the Intel chipset installation utility first and reboot before trying to install the Realtek LAN driver. http://h22207.www2.hp.com/us-en/drivers/selfservice/hp-2000-2a00-notebook-pc-series/5259212/model/5275371

Unable to connect to MSA 2000

Good morning all,
I need some expertise... I am not too familiar with the MSA storages and have 2 of them in my office. The previous IT guy did not show me how to connect to them and since his leaving the company had gone through some network changes...
So my problem is that they are currently given static IPs and given a static gateway. So I am unable to connect to them via a CAT5. Now one of them has a console cable going into one of my servers. I tried using Putty to connect to the device through the serial port but when hitting the Enter key, I get giberrish...
Can someone help me get connected to the CLI so I can put each device to DHCP?
The models are:
MSA2324sa
MSA2312sa
The Array Config Utility only shows the SAS controller installed in the server for the server's array of disks.
This question was solved.
View Solution.

I found the answer to this problem. When using Putty, you need to change the baud rate... Below are the settings:
Set the communications properties to 115200 , 8 , n , 1 , and no flow control
Also when in the CLI, you change the IP addressing information with the following command:
set network-parameters ip 1.2.3.4 netmask 255.255.0.0 gateway 1.2.3.1 controller a

Macbook air is unable to connect on hidden wireless network

Dear users and support,
I have just bought my macbook air with lion os already installed, but I am unable to connect to hidden wireless network. Is there any trick to fix it? even though I am typing the name and password it's unable to login.
Please advice.
tks,

Back up all data before making any changes.
Step 1
Take all the applicable steps in this support article.
Step 2
If you're running OS X 10.8.4 or later, run Wireless Diagnostics and take the remedial steps suggested in the summary that appears, if any. The program also generates a large file of information about your system, which would be used by Apple Engineering in case of a support incident. Don't post the contents here.
Step 3
This step will erase all your settings in the Network preference pane. Make a note of them before you begin, and recreate them afterwards. It may be helpful to take screenshots of the preference pane.
Triple-click the line below on this page to select it:
/Library/Preferences/SystemConfiguration
Right-click or control-click the highlighted line and select
Services ▹ Reveal
from the contextual menu.* A folder should open with an item named "SystemConfiguration" selected. Move the selected item to the Trash. You may be prompted for your administrator password.
*If you don't see the contextual menu item, copy the selected text to the Clipboard (command-C). In the Finder, select
Go ▹ Go to Folder...
from the menu bar, paste into the box that opens (command-V). You won't see what you pasted because a line break is included. Press return.
Reset the System Management Controller.

HT4061 my computer unable to connect itunes server

my computer unable to connect itunes server,even itune help is also not connect to server
the massage will be "iTunes Help is unavailable because your computer isn’t connected to the Internet.

in diagnostics report
Microsoft Windows 7 x64 Home Basic Edition (Build 7600)
Dell Inc. Inspiron 1545
iTunes 11.0.0.163
QuickTime not available
FairPlay 2.2.32
Apple Application Support 2.3.2
iPod Updater Library 10.0d2
CD Driver 2.2.3.0
CD Driver DLL 2.1.3.1
Apple Mobile Device 6.0.1.3
Apple Mobile Device Driver 1.63.0.0
Bonjour 3.0.0.10 (333.10)
Gracenote SDK 1.9.6.502
Gracenote MusicID 1.9.6.115
Gracenote Submit 1.9.6.143
Gracenote DSP 1.9.6.45
iTunes Serial Number 00DABA000B0C13D0
Current user is not an administrator.
The current local date and time is 2012-12-12 11:43:11.
iTunes is not running in safe mode.
WebKit accelerated compositing is enabled.
HDCP is supported.
Core Media is supported.
Video Display Information
Intel Corporation, Mobile Intel(R) 4 Series Express Chipset Family
Intel Corporation, Mobile Intel(R) 4 Series Express Chipset Family
**** External Plug-ins Information ****
No external plug-ins installed.
iPodService 11.0.0.163 (x64) is currently running.
iTunesHelper 11.0.0.163 is currently running.
Apple Mobile Device service 3.3.0.0 is currently running.
**** Network Connectivity Tests ****
Network Adapter Information
Adapter Name:    {A21769EE-B8FA-43A8-ACC9-8B4AC6B200C6}
Description:    Microsoft Virtual WiFi Miniport Adapter #2
IP Address:    0.0.0.0
Subnet Mask:    0.0.0.0
Default Gateway:    0.0.0.0
DHCP Enabled:    No
DHCP Server:
Lease Obtained:    Wed Dec 31 16:00:00 1969
Lease Expires:    Wed Dec 31 16:00:00 1969
DNS Servers:
Adapter Name:    {61D7CACF-EC6D-4ED3-BAE8-0FE3AC647BFF}
Description:    Dell Wireless 1397 WLAN Mini-Card
IP Address:    192.168.1.5
Subnet Mask:    255.255.255.0
Default Gateway:    192.168.1.1
DHCP Enabled:    Yes
DHCP Server:    192.168.1.1
Lease Obtained:    Wed Dec 12 09:36:06 2012
Lease Expires:    Thu Dec 13 09:36:06 2012
DNS Servers:    192.168.1.1
Adapter Name:    {27D403C7-FE78-4FBE-B11B-6D449ACA2B11}
Description:    Bluetooth Device (Personal Area Network)
IP Address:    0.0.0.0
Subnet Mask:    0.0.0.0
Default Gateway:    0.0.0.0
DHCP Enabled:    Yes
DHCP Server:
Lease Obtained:    Wed Dec 31 16:00:00 1969
Lease Expires:    Wed Dec 31 16:00:00 1969
DNS Servers:
Adapter Name:    {EAB5F805-06F2-4343-AB41-C1BB2A0028F5}
Description:    Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller
IP Address:    0.0.0.0
Subnet Mask:    0.0.0.0
Default Gateway:    0.0.0.0
DHCP Enabled:    Yes
DHCP Server:
Lease Obtained:    Wed Dec 31 16:00:00 1969
Lease Expires:    Wed Dec 31 16:00:00 1969
DNS Servers:
Active Connection:    LAN Connection
Connected:    Yes
Online:        Yes
Using Modem:    No
Using LAN:    Yes
Using Proxy:    No
Firewall Information
Windows Firewall is off.
Connection attempt to Apple web site was unsuccessful.
The network connection timed out.
Basic connection to the store failed.
The network connection timed out.
Connection attempt to Gracenote server was successful.
The network connection timed out.
iTunes has never successfully accessed the iTunes Store.

OD Master/PDC, 10.4.11, why xp clients unable to locate domain controller?

After a migration/upgrade from 10.3.9 to 10.4.11 Server, windows XP clients are intermittently unable to log in to or even bind to the PDC running on that server.
I did a clean format and install from the 10.4 media, choosing the standalone server type, and applied all the Software Updates, I got forward and reverse DNS working for my zone, then I followed the instructions at http://www.afp548.com/article.php?story=20050615173039158 to move my OD from a working 10.3.9 server to 10.4.
This server goes against the usual recommendations, as it provides DNS, OD master, PDC and file services to 32 clients all in the same subnet, 20 running Windows XP SP2 and 12 running OS X Client 10.4.x or 10.5.x.
File services and various other users of the OD/LDAP, for example Wildfire Jabber/XMPP server and Apache2/LDAP running on a separate Linux server, are able to authenticate against the new 10.4.11 OD.
However, at this point the symptoms become intermittent approx. 40% of the Windows XP clients were unable to log in with various domain accounts, yielding errors of the form "Unable to find domain FOO". If I remove a client from the domain by joining it to WORKGROUP and rebooting, then try to join FOO again, I'll get an error, "Unable to locate Domain Controller for FOO..."
The set-up:
My server's FQDN is myserver.foo.example.com
The server's DNS is authoritative for the 10.10.10.0/24, foo.example.com zone and I have the trailing dot's in the right places, so ping myserver.foo.example.com, ping myserver, and ping 10.10.10.10 (server's example IP from the foo.example.com zone) all work correctly.
The DHCP server for this vlan is providing my DNS server to the clients, but is providing no netbios server. The XP clients are all set to use the DHCP server setting, which, according to the TCP/IP Advanced Settings panel, means that they'll revert to netbios over tcp/ip since no wins server is specified.
In Server Admin->Windows->General:
Role: Primary Domain Controller (PDC)
Description: FOO Domain at example.com
Computer Name: myserver
Domain: FOO
Server Admin->Windows->Access:
Allow Guest Access: Check
Client Connections: Unlimited
Authentication: NTLMv2 & Kerberos, NTLM, and LAN Manager: All check
Logging->Log Detail: High
Advanced->Code Page: Latin US
Services: Workgroup Master browser and Domain master browser: check
WINS Registration: Off
Homes: Enable virtual share points: check
Should my Windows service on 10.4.11 be providing WINS or not? If so, should the DHCP server be set to point the clients to it? If not, how do the XP clients reliably resolve the FOO domain?
Why did all these XP clients work fine with a 10.3.9 Windows PDC but don't work with 10.4.11?
Another strange point - I can use the XP-side 'net view' command to poke around and things look reasonable. I.E. even the clients that aren't joined to the domain and can't locate the domain controller will return sane results for 'net view /domain:FOO'.

The new PDC does use the same domain name as the old PDC, and the SID mismatch is at least partially to blame. After I'd performed the upgrade and confused the windows clients, I saw the advice on using samba's net command to duplicate the old PDC's SID to the new PDC. Maybe someday I'll have the opportunity to try that.
I resorted to removing all the XP clients from the domain and re-joining them. The XP clients were still able to contact the domain intermittently. I used various command-line tools on the XP side, including the built-in net command as well as some others I downloaded such as the quite useful http://www.joeware.net/freetools/tools/findpdc/index.htm, as well as the client-side error messages during the domain join attempts and the messages in the Event log, to determine that the clients couldn't find the domain.
The XP client TCP/IP settings state that the clients will revert to using netbios if no WINS server is specified, but that clearly wasn't working reliably, so I just enabled the WINS server on the PDC, told the DHCP server to hand out its address for the netbios-related options for that subnet, rebooted the PDC, waited a while for things to settle out, and now all the clients can reliably find the PDC.
I still have no idea why the WINS-less set-up worked in 10.3 server but didn't work in 10.4 server, but believe me, I'll remember it now!

Ad agent connection erro unable to connect to server :0

Hello i want to configure ad agent 1.0.0.32 build 539 on windows server 2008 with patch installed.
but when i execute adactrl show running i see that
Cisco AD Agent adactrl -- version 1.0.0.32, build 539
Connection error. Unable to connect to server:0
An exception occured! connection Error
For further information use:
adactrl help
i test adactrl restart, reboot server no change.
nps must be install ?

Hi
I am running into the same error trying to setup AD agent Windows 2003 Server Standard Edition with SP2 (and I have disabled the Windows Firewall). The AD Agent is installed on the same machine as the domain controller.
Thanks
C:\IBF\CLI>adactrl show running
Cisco AD Agent adactrl -- version 1.0.0.32.1, build 598
Connection Error. Unable to connect to server: 0
An exception occured! Connection Error
For further information use:
adactrl help
C:\IBF\CLI>adactrl start
Cisco AD Agent adactrl -- version 1.0.0.32.1, build 598
Connection Error. Unable to connect to server: 0
An exception occured! Connection Error
For further information use:
adactrl help

Windows 7 laptops unable to connect to WiFi automatically

Hello All,
We are facing a wierd issue where the Windows 7 laptops are unable to connect to the corporate Wifi automatically.
We have pushed the profiles using Group Policy and there are about 15 profiles present on each laptop. The SSIDs are not broadcasted and PEAP is the authentciation method. While the Windows XP and some of the older Win 7 laptops connect fine the newer Dell 6410/20s doesnt. Upgrading the wireless card drivers hasnt made a difference.
I am posting this to know if anyone else on this forum has faced this issue and found a fix? Please suggest what could be the problem. Thank you in advance.
Best Regards

Hello Scott,
I am unable to set the policy to 2.4 only since there are a lot of APs sharing the controller and dont want to bump off all the clients that are able to client.
Today tried upgrading a cleints wireless NIC drivers and that didnt make much difference. And I am not seeing any debug output on the WLC for this client.
I think either some laptops are not probing actively or the WLC is ignoring the probe requests.
Could someone please guide how can i check if the laptops are sending probe requests for a particular SSID ??
I know it can be done using a wireless sniffer, but unfortunately i am not based onsite nor there is anyone onsite who can help.
Thanks,
Jeen

Unable to find domain controller for the specified domain. Please explicitly specify the domain controller.

Im getting error "Unable to find domain controller for the specified domain. Please explicitly specify the domain controller." when I try to create an AD connection for my User Profile Service. The entire sharepoint environment is installed
on one server. That server has everyting on it, AD, SQL, Sharepoint, and its the domain controller. I cant figure out why this will not identify?Trevor Fielder

Hi,
Did you get this error when clicking on the Populate Containers button?
If yes, please make sure that you have provide the domain credentials in the account name and password
boxes below when entering the domain information. The account must be granted the replicating directory changes permission on the domain.
You can refer to this blog:
http://www.harbar.net/articles/sp2010ups.aspx
Xue-Mei Chang

Unable to connect to site collection (website)

Hi
I have just set up Sharepoint Foundation 2013 on a Windows 2012 R2 domain controller.
I have created a site collection and have assigned it a name but am unable to connect to it.
I did this years ago on a 2003 server but cannot remember what I did (and it might not be relevant now...)
After creating the site collection this page is displayed:
http://img537.imageshack.us/img537/9210/e09e0a.jpg
But when I click that link this is displayed:
http://img539.imageshack.us/img539/5084/a7ea1d.jpg
Have I missed a step when doing this?
Just one website (site collection) will be created and used.
Can someone help me with this, please?
Thanks

Hi, Alex
Thanks for replying.
When I create the collection the following is displayed:
When I click the link I see a page can't be displayed message
Unfortunately, your link 404's but I looked up loop back check and found instructions on how to disable the loop back check:
Disable the authentication loopback check
Re-enable the behavior that exists in Windows Server 2003 by setting the DisableLoopbackCheck registry entry in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry
subkey to 1. To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer: 1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3.Right-click Lsa, point to New, and then click DWORD Value.
4.Type DisableLoopbackCheck, and then press ENTER.
5.Right-click DisableLoopbackCheck, and then click Modify.
6.In the Value data box, type 1, and then click OK.
7.Exit Registry Editor.
8.Restart the computer.
Is this what you are referring to?
When I look at IIS, I cannot see htlincs listed as a site.
I will do some more research. However, if anyone has any links to content that will help me solve this issue I would be grateful. The 'collection' needs to be accessible by everyone within our network (single site, single subnet).
Thanks :)

Unable to connect to VM over RDP

Hello,
I have a VM that I am suddenly unable to connect to over RDP.
The machine is connected to a virtual network that is connected to my local network over a site to site VPN.
I was previously able to RDP using both the public endpoint and over the VPN tunnel. I can still connect to other machines over the VPN so I know the VPN is working. I also cannot ping the machine from another Azure VM on the same subnet in my Azure virtual
network
I have tried the various troubleshooting steps around restarting and resizing the VM. None of which has helped. I have not yet tried deleting the VM and trying to reattach the disks.
I would normally shrug it off and rebuild the machine but it is a domain controller and I'd rather not have to go through the process of removing a failed domain controller.
As a further troubleshooting step I downloaded the VHDs to try and run them locally in Hyper-V to see what is going on in the console window there. The machine starts and blue screens with error 0xc00002e2 but I am not sure if this related or just an issue
with migrating from Azure to Hyper-V
Can anyone assist? Thank you in advance.
Tom

Hi,
Just to double check: Have your assigned a static IP? That is a NoNo!
If not then try the following
1. Download the RDP file again and try connecting again
2. Shut down and restart the machine via the management portal
3. Makesure the BuiltIn firewall in Windows 2012 is not blocking your RDP connection
4. The RDP endpoint is created by default and so should be correct, however double check. If you have created a custom RDP connection, you have to also use the public port within the servername
Cheers and goodluck

1130 AP unable to connect to controller

Similar Messages

Maybe you are looking for