Change network address of acs server

Put in a new backup ACS server and the senior guy put in temp host address. Now
need to change the temp host address to its permanent address but need a little clarification. Do you just change it in the Windows srvr 2003 tcp/ip stack or do you need to change it also inside the CSACS app?? Can't find it in the manuals easily.

Yes you'll need to change ACS config. Just locate the AAA Server entry for the server (in Network Config) and set the ip address to the new value.
Or you can always just enter the server name instead in case the address changes again.
tip: in network config you can enter DNS names instead of ip addresses for devices & aaa servers.

Similar Messages

Valid hostname or network address required in server description:10024

Since applying 10.8.5, the mail server won't run and this message is in the SMTP log
valid hostname or network address required in server description:10024
If I turn off filtering the existing email on the queue aren't processed because smrp-amavis is not available.
What's going wrong and how can I correct it?

OK, seems a lot of emails were left on the queue. after much Googling, I found
postsuper -r ALL
This got things moving again and the outstanding queue cleared.

Ora VM 3.2.1 - how to change IP address of VM server? (management interface)

Hi, I cannot find in doc how I can change IP address of VM server.
I have static IP address 10.3.37.29, and should be 10.3.37.27.
I have 8 virtual guests on this server, I cannot aford to lose it.
Can everybody tell mi any tip, how to manage it, please?
Thank you in advance
Vladislav

Hi ,
Please use the below link to change the Ip address of the server :
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.3/user/guide/diagnos.html#wp1165007
Thanks--
AfroZ
If this post answers your question, please click the "Correct Answer" button"

Changing ip address of one server to another in license server

Hi everyone,
I donu2019t know if my question belongs in here; forgive me because Iu2019m a newbie here and in using SAP as well. I was designated to investigate about a recurring issue of one of our client. The scenario goes like this..
Our client has 2 stores/branches (A& B); each store has sap server and license. We normally install remote desktop and sap business one client so that their workstation can connect to the server and do their task efficient with authorization. We always receive calls that they were offline the whole night. Why is this scenario happening? We found out that the license server ip address of store B (under license administration) was already changed to Store Au2019s ip address. They claiming that they never did anything. They donu2019t do it manually (adding store Au2019s ip add to sap b1 service mgr). Please give me any other advice/ suggestions or to dou2019s for me to be able to track if its our mistake or our clients mistake?
Iu2019m looking forward to your answers soon.
Thanks,
Pipay

Hi Sir Rahul,
I'm glad you replied, I actually did the same thing. The reason why they're saying that the server A ip add becomes sever B ip add is because the ip add were change, and this thing can be possible if there's someone (maybe the user itself or client) manually change the ip address in license server or add it in service manager. BUT when we ask them, they did not change it manually nor add it. they keep on insisting, Itu2019s just automatically change and if I'll conclude that there were the one who made a mistake, I still have to check first. What are the possible scenarios why these things happened; aside from manually add/encoding. Is it because of the sap b1 client?
My co-worker told me that she notice this store doing this scenario: from one of server Au2019s workstation (A.1) they will connect to server B which I think can cause server A to offline. Is it possible?? Iu2019m confuse but I need to resolved this issue
Thanks,
Pipay

How do you change network location type on Server 2012?

Within Network & Sharing Center there appears to be no options available to change a network type as you could do in Server 2012?
Within Network List Manager policies everything is set to "not configured" so this should not be disabling any functionality.
Thanks.

Hi,
Firstly, if the server is domain joined, when it starts to detect the network location, the machine will contact a DC via port 389. If this detection successful, it will get the domain profile. And we cannot change it.
However, if the server is not domain joined, the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.
We can do this by referring to
Turn sharing on or off or
How to change network location type in Windows 8.
Also we can refer to
Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles.
All the above articles can apply to Windows Server 2012.
Hope this helps.
Jeremy Wu
TechNet Community Support

Router Source address for ACS Server

Does anyone know how to configure a router(MSFC in this case so the same ip address is sent to the ACS server for authenticating. The source address may not always be the same depending on the path taken, If the source address isnt an ip address configured for one of my devices the acs server rejects the attempt and the router defaults to local login. I tried settigng a loopback address and always telnetiing to the loopback address however the source address from the MSFC is not the loopback I have 38 vlans, snd i suppose i could configure thoe ip addresses under a device, however if iI add a vlan then I must remember to add that vlan to ACS. Im sure there is a simpler way to address this, I just cant seem to find the configs needed on the MSFC to make it work.
Any help will be greatly appreciated.
Thanks

Hi,
Sounds like you need:
ip tacacs source-interface interface-name
(or ip radius source-interface interface-name)
It's recommended to use a loopback interface, so this would give you (assuming loopback0):
ip tacacs source-interface loopback0
HTH - plz rate if it does
Andrew.

Changed IP address of FC Server - Now a client app issue...

Okay, so of course I changed the IP address of our Final Cut server after the install. Now, the client machines freakout when you load the client. They sit there and give you some errors. I click on "OK" and hope to see the window where you could type in a new IP address, but instead it just quits out. If you try about a dozen times it sometimes comes up, but mostly doesn't.
Any ideas? I tried trashing preferences but no luck. Must be hiding something somewhere!
Ryan

Have you tried clearing out all your java and browser caches? Make sure the browser is pointing to the right URL for download... I have some users able to log into different instances of FCSvr. Each new FCSvr is saved in the dropdown of the Java client.

Change IP address of LDAP Server

Hi,
I am using Directory Server 5.1 SP 2 HF2, and have installed the server using a 10.x.x.x address but now need to change this to a production 172.x.x.x address. Is this an easy process and how do you go about doing this?
Are there any Sun docs on this?
Thanks
D

There is a script called admin_ip.pl provided with the directory that will handle the IP address change. It is located in the /shared/bin directory.

Change the IP address of ACS

Hello Guys,
I will soon be changing the IP address of my ACS server since i will be moving it to a new VLAN. this ACS is also integrated with Microsoft Active Directory users for authentication of the wireless lan users.
my main worry is if i change the IP address of the ACS, do i need to do anything on the Active Directory server? will i have any certificate related issues? the ACS i am running is version 5-1-0-44-6.
any advice is highly welcome and appreciated.

Hi Abukuru,
If you need to change the IP of ACS server then there will be no effect on "Certificate" but you need to update the ACS server address at the network wired devices using TACACS+ and RADIUS.
There will be no issue in the integration done with windows AD (Active Directory). But still to be more sure you can test the settings from inside the ACS server.
If any issue aroses then you can always put your query here.
Thanx and Regards
Anim Saxena
*Rate Helpful Post*

ACS Database Replication over VPN with overlapping Network Addresses

We currently have two co-locations each situated in different provinces. We have two ACS servers which we want to deploy at each co-location. All our network equipments are behind PIX/ASA devices. Getting them to replicate over the VPN should be easy but in our case we have overlapping Network Addresses at both ends of the tunnels.
As per Cisco data does not transit a NAT device when the two Cisco Secure ACS servers communicate and a successful database replication can occur only if the secondary ACS server perceives no change in the IP header or content of the data it receives. So that means we will not be able to Implement NAT to achiever this.
Has any one of you faced this problem of replicating ACS Database over the VPN with overlapping Network Addresses and was anyone able to successfully solve this issue using a work around ?
All provided info and comments are greatly appreciated.

I can help with the 3005 setup if you decide to go that route.
You will need to add 2 network list entries under Configuration>Policy Management>Traffic Management>Network Lists.
You will need to configure a local and remote address. The local will be one of the public ip's for the site.(Provided by your ISP)The remote will be the device you are connecting to on the other end.
You will also need to add a Nat Lan to Lan rule under Configuration>Policy Management>Traffic Management>Nat>Lan to Lan.
Use a static Nat type. The rest will look similar to my example.
Source(Local address)Translated(Public Ip Address used in the network local list)Remote(Ip address of the device on the other end)
Now just create an Ipsec lan to lan tunnel. You will need to agree with the ISP on des type and auth type. Use you local and remote networks you created earlier.

Message Server Unreachable (after changing IP address at host)

Hi guys,
I changed the IP address in my server. According to note 403708, I updated the new IP address in /etc/hosts. The note also suggests me to change in /etc/services but I see no IP address for me to update.
Later when I restart my sapinstance, I see the disp+work.exe is "Running, but Message Server Unreachable". I've also updated the IP address in SM59 but I see no change.
This is what I got from dev_rfc.trc:
ERROR file opened at 20071206 221839, SAP-REL 620,0,674 RFC-VER 3 549374 MT-SL
T:5048 Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1400
T:5048 <* RfcDispatch [1] : returns 1:RFC_FAILURE
This is what I got from dev_disp:
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3212]
Anyone has any idea?

Yes I'm on Windows, the path that i'm refering is:
winnt/system32/drivers/etc/services
winnt/system32/drivers/etc/hosts
Anyway my prob is fixed now. Probably the problem is due to I did not restart the server after changing the IP. Anyway everything looks pretty fine now
Thanks guys

What effect on OEM when change IP address on server?

Hi All,
I will change IP address on server that Oracle Enterprise Manager(OEM) is reside on what effect that occured on OEM when change IP address. What things need to be modified such as configuration files ,etc.
Thank you
Mcka

trying to help Tom answer some of your questions. he may has better answer
1. Hosts file that you told are keep in client or
server(and what path?)it's a file for your OS to resolve hostname into IP address.
in unix it's usually under /etc/hosts
in windows it's under
C:\WINDOWS\system32\drivers\etc
filename is lmhosts
You don't really need the file if you use DNS, this lead to second question
2. What is the DNS ,Agent?DNS -> domain name server
It's a server help your resolve domain name, hostnames into IP address. So you can just type www.oracle.com to goto Oracle website instead of 141.146.8.66
DNS is not a single server on big network, especially internet. there are many servers and also DNS agent to help you get quick naming resolution. When server is updated the change need to be populated to other servers and agents.
3. Why is the reinstall OEM?maybe Tom want to change his server's hostname?
Like he said, OEM identify server by hostname not ip address, so you are safe to change IP address only. No need to reinstall
4. What is the OMS?typo?
>
Sorry,if I ask the basic questions.you come to the right place.

The dreaded: The network address is invalid error - SQL 2014 Cluster on Server 2012 R2

Trying to setup an SQL 2014 Failover cluster on Windows Server 2012 R2 (two nodes). Every time I get to the assign a SQL server Network Name piece of the setup I get the following error message:
The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'
This happens whether I use the Advanced cluster installation procedures or the normal installation. I have tried the following based on anything I can find on the web:
1) Removed the clustered MTDTC role.
2) Deleted the NIC Team (4 1GB NICs). Deleted all but 1 NIC from the server device manager.
3) Shutdown the second node.
4) Lanman Server registry change posted someplace on this forum that does not stick on reboot
None of the above, separately or in combination, has worked to allow SQL 2014 to be installed as a cluster role.
There is no virtual machines added to the cluster. This is not a VMware installation. It is straight Windows 2012 R2 with a two node cluster (setup identically).
Any ideas, suggestions, comments?
Thanks,
-Andrew

Hi Alberto and Lydia,
The cluster was verified, there are only warnings related to a lack of redundant network paths as the cluster verification doesn't recognize a team of 4 nics are redundant. I updated AD to include the permissions detailed in the link Lydia provided,
still no go.
I'm not sure how to attach the installation logs to this message forum other than as text in the message, so here you go:
Summary:
Overall summary:
Final result:                  User cancelled
Exit code (Decimal):           -2068380094
Exit facility code:            1207
Exit error code:               1602
Exit message:                  User has cancelled.
Start time:                    2015-03-24 09:55:25
End time:                      2015-03-24 10:01:04
Requested action:              CompleteFailoverCluster
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for ComponentUpdate: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
Cluster properties:
Machine name: SUN-PIE-CS-01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine name: SUN-PIE-CS-02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Data Quality Client                      1033                 Standard
Edition     12.0.2000.8     No         Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine Properties:
Machine name:                  SUN-PIE-CS-01
Machine processor count:       16
OS version:                    Windows Server 2012
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Package properties:
Description:                   Microsoft SQL Server 2014
ProductName:                   SQL Server 2014
Type:                          RTM
Version:                       12
SPLevel:                       0
Installation location:         \\sun-server2\data\Software\Microsoft\SQL 2014\x64\setup\
Installation edition:          Standard
User Input Settings:
ACTION:                        CompleteFailoverCluster
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
CONFIGURATIONFILE:
CONFIRMIPDEPENDENCYCHANGE:     false
ENU:                           true
FAILOVERCLUSTERDISKS:          <empty>
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    <empty>
FAILOVERCLUSTERNETWORKNAME:    sun-pie-mt-01
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS:              false
INSTALLSQLDATADIR:             <empty>
INSTANCENAME:                  MSSQLSERVER
QUIET:                         false
QUIETSIMPLE:                   false
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - Native
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Integration Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Setup Support Files
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity SDK
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Writer
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Documentation Components
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Browser
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
    Message:
        User has cancelled.
    HResult : 0x84b70642
        FacilityCode : 1207 (4b7)
        ErrorCode : 1602 (0642)
    Stack:
        at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
        at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)

Mail.app doesn't hava connection with imap server when changing network.

Ive got a strange problem after upgrading OSX from 10.6.8 to 10.8.4.
I have got a xserve, with osx 10.6.8. (mail) server installed on it.
When i am in the office (LAN) mail works just fine. if iam home and wake my macbook from sleeping i see in the mail app the attention mark telling my something is wrong with the mail account.
If i open the connection doctor it say's can't connect to IMAP server. if i check my iOS devices there is nothing wrong, everything is working and i can send/recieve mail. on iOS and OSX the settings are the same with SSL enabled and password type.
When i tried to telnet the mailserver address with the IMAP or SMTP port i get a connection. so, there is no firewall blokking my connection.
But now the strange thing when i quit my mail.app and start it again the mail gets connection again. So is there a problem when changing networks when the Mail.App is stil active?

That's just to bad, will it be solved in a future release of OSX?
I don't know... maybe Apple will force me migrating to Mavaricks.
it seems that although w'r using DNS, the outside ip gets remebered or the connection isn't closed down properly when putting the macbook to sleep.
I can try offcource to configure the outside LANip (Non dns) in my mail client.
I will post with results..

Setting up Network Address Server Settings (Static IP)

To be abundantly clear, I do not want to change my Internet Connection Type - its dynamic and will stay that way. I'm not paying my ISP (Time Warner Cable - RoadRunner in NYC) for a static IP address.
I am changing my network address server settigns to disable DHCP, and hopefully assign static IPs to the various comps/devices in my home network. For various reasons (mostly security/ease of use) it would be handy to know my desktop/media center is always (for example) 192.168.1.101, my laptop is always 192.168.1.102, xbox is always...etc etc.
I have DHCP under network address server settings, and attempted to change TCP/IP protocol of my adapters in the comps to static IP (instead of obtain one automatically). I followed the WRT54G router manual whilst doing this. So I inputted the IP for each comp I want to use, 255.255.255.0 for a subnet mask, and the default gateway (in the example, it would be 192.168.1.1, though I want to use a different internal IP address for my network as a security precaution). Now it also wants primary and alternate DNS. TimeWarner won't tell me this information. They say they tell my router it (since its DHCP) and it changes. So...if I want static IP addresses for the devices in my network, I need my router to have a static ip address externally? that means I pay more. Or have I got it wrong? Please advise. I know I could check the router's status page and grab the two DNS servers its currently using, but then when my router's IP and DNSs change due to the internet connection being dynamic, I'd have to go change all the devices in the network (PITA!!). Thank you for your help.

Most ISPs don't actually change their DNSs only the internet IP adress... you can try grabbing those DNS 1 & 2 and set it to your PC. try checking if those will change for verification.
If not, then for primary DNS, use 192.168.1.1 (equivalent for your router so whatever the DNS your router will use, it will just route it. but it doesnt always work), for the alternate DNS: you can use 4.2.2.1 or 4.2.2.2
"a helping hand in a community makes the world a universe"

Change network address of acs server

Similar Messages

Maybe you are looking for