Tomcat Setup Problems

I am setting up Tomcat in an attempt to complete the Java Server Pages Fundamentals tutorial. I am new to JSP so please bear with me. I have followed the directions for installing Tomcat and referenced posted topics in the forum archives with no success. These are the exceptions that are repeatedly thrown:
Catalina.start: LifecycleException:  null.open:  java.net.BindException: Address already in use: JVM
_Bind:8080
LifecycleException:  null.open:  java.net.BindException: Address already in use: JVM_Bind:8080
        at org.apache.catalina.connector.http.HttpConnector.initialize(HttpConnector.java:1130)
        at org.apache.catalina.core.StandardService.initialize(StandardService.java:454)
        at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:553)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:780)
        at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
        at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)
----- Root Cause -----
java.net.BindException: Address already in use: JVM_Bind:8080
        at org.apache.catalina.connector.http.HttpConnector.open(HttpConnector.java:950)
        at org.apache.catalina.connector.http.HttpConnector.initialize(HttpConnector.java:1128)
        at org.apache.catalina.core.StandardService.initialize(StandardService.java:454)
        at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:553)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:780)
        at org.apache.catalina.startup.Catalina.execute(Catalina.java:681)
        at org.apache.catalina.startup.Catalina.process(Catalina.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243)I have tried changing the port and I get the same response. My OS is XP Pro and I'm using JDK 1.4.
I greatly appreciate any input. Thanks!

I was having this same problem Rob!! I discovered that Tomcat will place (at least it did on my Win2k, WinXP systems) an "Apache Tomcat" service in my services manager, and set it to run on 'automatic'. This means, every time I was booting up, Tomcat was already starting. And because it is then a 'windows service' so to speak, you cannot turn it off using Tomcat's 'shutdown' shortcuts! Naturally, when I tried to start Tomcat using the established shortcuts it wouldn't work because it was already running (unbeknownst to me).
So, if you have this same issue:
-in a comman line, type "services.msc" to bring up the services console window
-fine the "Apache Tomcat" service entry, right-click on it, and select 'properties'
-in the properties dialog you can stop the service
-once stopped, change the 'startup type' to 'manual'
Now you can use Tomcat's start and stop services as you wish.

Similar Messages

  • I need to upgrade my 10.5.1 os on my G4/1.25 (I'm having some audio-midi setup problems), but it's a machine that is not connected to the internet.  Do I have any options?  Thanks!

    Friends,
    I'm having some audio-midi setup problems on my G4/1.25/10.5.1 machine.  I'm thinking that a routine OS upgrade might help.  However, this machine is not connected to the internet.  Are there any alternate methods for upgrading system software?  Thanks in advance!

    OK, what you should do is download the updates on another machine and burn them to a disc.  Start at this link http://support.apple.com/downloads/#leopard for downloads and find, among other things, the 10.5.8 combo updater that works on PPC machines, plus security, QuickTime and other updates.  Going from 10.5.1 to 10.5.8, there will probably be a bunch of things that you should install.  Being off the internet with the machine, you can't have Software Update sort it out, so something might get missed, unfortunately.
    My suggestion is this: if it looks like you might need a download, get it onto that disc.

  • Setup problem, windows xp, firefox upgrade to 4 and asked to reboot but did not progress. keeps asking to restart even if I try to remove

    setup problem, windows xp, firefox upgrade to 4 and asked to reboot but did not progress. keeps asking to restart even if I try to remove

    Hi marsano,
    Usually the only reason it will ask you to reboot is if there is a file that must be modified that the updater doesn't currently have access to. You should try running the Firefox program once as Administrator:
    * Right-click the icon and choose ''Run as Administrator''
    If that doesn't help then do a clean reinstall.
    # Download a fresh copy of Firefox from the [http://www.mozilla.org/firefox/fx/ Mozilla download page] and save the file to the desktop.
    # [[Uninstalling Firefox|Uninstall]] your current version of Firefox and remove the Firefox program folder before running the new installer.
    # Run installer
    Remember that you don't want to remove personal data when uninstalling. That way you'll still have your personal information.
    Hopefully this helps!

  • Apache webserver can't find tomcat - mod_jk problem?

    Hi
    I have recently upgraded HP-UX apache software
    FROM
    Apache webserver: 2.0.55
    Apache tomcat : 5.5.9
    TO
    Apache webserver: 2.0.55
    Apache tomcat : 5.5.9
    I have 2 tomcats running, one JVM for a daytime service and another for a nighttime service.
    So while 1 tomcat is down, the other is up, apache always running.
    However, since I have upgraded, I see the following error messages in jk.log:
    [Mon Nov 20 07:00:41 2006] [error] ajp_connection_tcp_get_message::jk_ajp_common
    .c (949): ERROR: can't receive the response message from tomcat, network problems or tomcat is down (127.0.0.1:8059), err=-232
    The tomcat in question is up - and the messages returned are 500 responses - server configuration issue.
    Get several a day.
    Basically using mod_jk to bind the tomcat installations to apache webserver.
    What is new though in mod_jk 1.2.10 is that a shared memory file is specified. I am wondering what happens to this memory that is used to load balance the workers when tomcats are bounced.
    Issues go away after a bounce of apache - but after each tomcat has been stopped once - messages start to fail intermittently after that.
    Done some googling but do not see any solutions - so here's hoping!
    Thanks.

    Noticed my deliberate mistake!
    From
    Apache 2.0.32
    Tomcat 3
    Still no joy with with this in terms of finding a solution to why the newer version of apache cannot find tomcat after it has been bounced.
    mod_jk.so version 1.2.9 introduced the shared memory for the workers, which as far as I can is the main config change in the 2 versions of apache that came from HP.
    So rolled back to the old version of apache with the new version of tomcat - and everything works fine!

  • Simple VISA Setup Problem

    Hi all,
    I'm having issues working with VISA in LabVIEW. Previously, I've used Peek/Poke VIs (before they were VISA VIs) that allowed me to read and write directly to registers at a given Windows address. I have a new, custom PCI Express board that uses the same architecture that I've worked with previously only this time I'm trying to access the registers using VISA.
    As this is my first time using VISA, I'm having some setup problems. Yesterday I got to a state where logically things should work but I still end up getting an error when I try to run a simple VISA Open command (see attached screenshot).
    The initial problem I had was I was not able to acquire a VISA resource that opens a session to my PCIe board...it would simply not show up on the resource list. After reading around I discovered I needed to create a custom VISA driver for my board. Once I did that using the VISA Driver Wizard, the device showed up in my list (as seen in the screenshot). I wrote the simplest of all VIs where I simply open that VISA resource, however, the error seen in the screenshot is produced.
    I'm pretty sure this is a simple setup issue, but does anyone know what I'm doing wrong?
    Attachments:
    Screenshot1.JPG ‏145 KB

    Hi bonhomme,
    I see you're having some issues using VISA. It sounds like you're new to VISA, so I wanted to pass along some information that we have availble on this software. This link gives good general information about VISA, and the related links are extremely helpful in finding specific issues.
    Thank you for attaching your error. This is extremely helpful in debugging since we can actually see the numbers. There is another forumn that talks about these at this link and at this link. 
    Hope this helps you out!!
    Lea D.
    Applications Engineering
    National Instruments

  • CDC setup problem

    {noformat}Dear all,{noformat}{noformat}Trying to troubleshoot a CDC setup problem in ODI:{noformat}{noformat}I got an error when trying to "Start Journal" from the CDC source model (in Designer).{noformat}{noformat}Here is what I've done:{noformat}{noformat}1. grant the following role to the CDC source schema (user):{noformat}{noformat}DBA, execute on DBMS_CDC_PUBLISH, connect, resource, select_on_change_sets, create session, select_catalog_role, execute_catalog_role, create sequence{noformat}{noformat}2. in the CDC source model "Journalizing" tab, specify JKM 9i logminer (CDC source is on 9i) and specify "Automatic Configuration"{noformat}{noformat}3. add a subscriber "SUNOPSIS" to the source model -> Changed Data Capture (Operator successfully run){noformat}{noformat}4. "add to CDC" from source model -> Changed Data Capture{noformat}{noformat}5. "Start Journal" from source model -> Changed Data Capture (Operator run failed with the following errors in the "create Journal" step){noformat}{noformat}
    30475 : 99999 : java.sql.BatchUpdateException: ORA-30475: feature not enabled:
    ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 298
    ORA-06512: at line 1
    30475 : 99999 : java.sql.SQLException: ORA-30475: feature not enabled:
    ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 298
    ORA-06512: at line 1
    java.sql.BatchUpdateException: ORA-30475: feature not enabled:
    ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 298
    ORA-06512: at line 1
    at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:367)
    at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9119)
    at com.sunopsis.sql.SnpsQuery.executeBatch(SnpsQuery.java)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execCollOrders(SnpSessTaskSql.java)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
    at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
    at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
    {noformat}{noformat}Any idea?{noformat}{noformat} {noformat}{noformat}William Lam
    {noformat}

    Hi Cezar,
    Thanks for following up. Below is from the description tab of the "Create Journal" steps:
    LOADING:
    select     FULL_TABLE_NAME     FULL_TABLE_NAME
    from     CDCSRC.SNP_TMP_TABLE_LIST     TMP
    where     TMP.FULL_TABLE_NAME = 'CDCSRC.DEPT'
    and     not exists      (
              select     'X'
              from     CDCSRC.SNP_CDC_OBJECTS     OBJ,
                   CDCSRC.SNP_CDC_SET_TABLE     TBL
              where     TBL.FULL_TABLE_NAME          = OBJ.FULL_TABLE_NAME
              and     TBL.FULL_TABLE_NAME          = TMP.FULL_TABLE_NAME
              and     TBL.CDC_SET_NAME          = 'CDCSRC.CDCSRC'
              and     OBJ.FULL_OBJECT_NAME     = 'CDCSRC.J$DEPT'
              and     OBJ.CDC_OBJECT_TYPE          = 'JRN_FULL_NAME'
    DEFAULT:
    BEGIN
         DBMS_LOGMNR_CDC_PUBLISH.CREATE_CHANGE_TABLE(
         owner          => 'CDCSRC',
         change_table_name     => 'J$DEPT',
         change_set_name     => 'SYNC_SET',
         source_schema     => 'CDCSRC',
         source_table     => 'DEPT',
         column_type_list     => 'DEPTNO NUMBER(2) ',
         capture_values     => 'new',
         rs_id          => 'n',
         row_id          => 'n',
         user_id          => 'n',
         timestamp          => 'y',
         object_id          => 'n',
         source_colmap     => 'n',
         target_colmap     => 'n',
         options_string     => ''
    END;
    The error message from the Execution Tab:
    30475 : 99999 : java.sql.BatchUpdateException: ORA-30475: feature not enabled:
    ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 298
    ORA-06512: at line 1
    30475 : 99999 : java.sql.SQLException: ORA-30475: feature not enabled:
    ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 298
    ORA-06512: at line 1
    java.sql.BatchUpdateException: ORA-30475: feature not enabled:
    ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 298
    ORA-06512: at line 1
    Once again, the setup details:
    - CDC source is on Oracle 9i
    - KM used is Oracle 9i LogMiner
    - enabled archivelog in Oracle 9i
    - installed logminer by running the 2 sqls as described in the earlier tread.
    I need to meet a tight deadline for POC completion and I desparate need some help here.
    Thanks and regards,
    William

  • Simple setup problems with JSTL and Tomcat

    Hi all, I'm having some problems getting JSTL to work the 1st time. JSTL setup seems to be a common problem for relative newbies, but having read previous threads, I still haven't been able to solve my problem so hopefully someone can help:
    the jstl.jar and standard.jar are in my WEB-INF/lib directory, so I don't think it's a classpath problem.
    My jsp page has the following at the top:
    <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %>Later, I reference a bean var with :
    <c:out value="My var is : ${var.property}"/>In my web.xml I have:
      <taglib>
       <taglib-uri>http://java.sun.com/jstl/core</taglib-uri>
       <taglib-location>/WEB-INF/lib/jstl.jar</taglib-location>
      </taglib>And I've placed the actual tld (c.tld) in the WEB-INF directory.
    On startup I get the error when compiling the JSP:
    No such tag out in the tag library imported with prefix c
    Can anyone help here?
    Thanks in advance,
    Mike

    I think this note from the JSTL mailing list by Shawn Bayern, one of the lead developers of Jakarta JSTL and the author of "JSTL In Action", will clarify it:
    http://www.mail-archive.com/[email protected]/msg04587.html
    Don't put that <taglib> in your web.xml. All the books tell you to do it, but Shawn Bayern has the right answer. The URI should be the one that's in the TLD JAR .tld files.
    I use JSTL and Tomcat 4.1.24 without the <taglib>, and it works fine. - MOD

  • Setup problem - Tomcat ID & Pwd

    Hi! I just installed Sun Java Studio Enterprise 8 and I am trying to set the User ID and password for the embedded Tomcat Server.
    I reviewed Help and found where to set the User ID and password (The User ID is initially "ide" and I can't read the password).
    I tried to change the User ID and password there, but it does not accept them next time I try it.
    Can anyone help with this?
    Thanks!
    Michael O'Neal
    Houston TX

    If I understand you correctly you are asking about tomcat users and roles
    Default user/password values are tomact/tomcat. Check them here:
    jstudio_ent8/ide/enterprise1/jakarta-tomcat-5.5.7/conf/tomcat-users.xml
    If you would like to have user with administrative rights then just check comments
    in above file about 'manager' user

  • Help! -why can't start Tomcat --Installation problem??

    I downloaded Tomcat 5.0.30.exe and installed Tomcat 5 and JDK 5 on my local computer (I also have IIS installed, and Java App Server (from J2EE); yes I have plenty of space lol);
    I did this in the command line:
    Set JAVA_HOME=C:\jdk1.5_03; and I also added this env variable to my user & system Path variables in System Properties dialogue (just to exclude this problem).
    and I remember during the Tomcat.exe installation, the JVM was already correctly set to C:\Program Files\Java\jre1.5_03\bin\client\jvm.dll (I also tried set JVM to C:\jdk1.5_03\jre\bin\server\jvm.dll and it did not seem to make any difference)
    I am still not able to startup the service (don't see my admin page even though the system tray says the Tomcat is running).
    Does any of the above setup seem wrong? I'm a novice in Java/JSP and just want to try developing some web service in Java/JSP instead of ASP or .NET.
    I'd appreciate all your advice and help!!
    Thanks in advance!!

    When I say "Startup" in the command, the original command window displays Using CATALINA_HOME: C:\apache\tomcat5, so I guess it was correctly set already ...?
    By default, it is using 8080 port... If I have my IIS running, would that have conflict? IIS runs on 80. I don't think I've anything running on 8080.
    localhost_admin_log has the following everytime I try to see admin page in my web browser:--------------------------------------------------------------
    2005-05-05 10:06:06 ApplicationDispatcher[admin] Servlet.service() for servlet admin.login_jsp threw exception
    javax.servlet.jsp.JspException: Cannot find message resources under key org.apache.struts.action.MESSAGE
         at org.apache.struts.taglib.TagUtils.retrieveMessageResources(TagUtils.java:1233)
         at org.apache.struts.taglib.TagUtils.message(TagUtils.java:1082)
         at org.apache.struts.taglib.bean.MessageTag.doStartTag(MessageTag.java:226)
         at admin.login_jsp._jspx_meth_bean_message_0(login_jsp.java:131)
         at admin.login_jsp._jspService(login_jsp.java:78)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:696)
         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
         at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:220)
         at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
         at java.lang.Thread.run(Thread.java:595)
    The above also appears in the Tomcat cmd prompt window if I use startup in the cmd window.
    The stdout and stderr logs has nothing.
    The jakarta_service log has the following:-----------------------------------------------------------
    [2005-05-05 10:03:46] [info] Service Tomcat5 name Apache Tomcat
    [2005-05-05 10:03:46] [420 service.c] [error] The specified service already exists.
    [2005-05-05 10:03:46] [538 prunsrv.c] [error] Failed installing Tomcat5 service
    [2005-05-05 10:03:47] [info] Procrun finished.
    [2005-05-05 10:04:48] [info] Updating service...
    [2005-05-05 10:04:48] [info] Service Tomcat5 updated
    [2005-05-05 10:04:48] [info] Update service finished.
    [2005-05-05 10:04:48] [info] Procrun finished.
    [2005-05-05 10:04:49] [info] Updating service...
    [2005-05-05 10:04:49] [info] Service Tomcat5 updated
    [2005-05-05 10:04:49] [info] Update service finished.
    [2005-05-05 10:04:49] [info] Procrun finished.
    Thanks a lot for your advice and help!!!

  • Tomcat restarting problem -plz help

    hi,
    Can anybody tell me why do i have to restart the server everytime i change my servlet.
    Kindly help
    Thanks and regards
    neha

    Hi Neha,
    This documentation is from JavaWebServicesDeveloperPack(Evaluation version)
    You will get more details if you can download this pack/tutorial from Java site & install it.
    http://java.sun.com/webservices/webservicespack.html
    Hope this will help you.
    Ajay.
    Manager App HOW-TO
    Introduction
    In many production environments, it is very useful to have the capability to deploy a new web application, or undeploy an existing one, without having to shut down and restart the entire container. In addition, you can request an existing application to reload itself, even if you have not declared it to be reloadable in the Tomcat 4 server configuration file.
    To support these capabilities, Tomcat 4 includes a web application (installed by default on context path /manager) that supports the following functions:
    Deploy a new web application, on a specified context path, from the uploaded contents of a WAR file.
    Install a new web application, which can be anywhere on the server's disks.
    List the currently deployed web applications, as well as the sessions that are currently active for those web apps.
    Reload an existing web application, to reflect changes in the contents of /WEB-INF/classes or /WEB-INF/lib.
    Remove an installed web application.
    Start a stopped application (thus making it available again).
    Stop an existing application (so that it becomes unavailable), but do not undeploy it.
    Undeploy a deployed web application and delete its document base directory.
    Since Manager is itself a web application, it interacts with you using standard HTTP requests and responses. However, it's "user interface" is minimal, because it is intended to be accessed from scripts set up by the system administrator. For this reason, commands are given as part of the request URI, and responses are in the form of simple text that can be easily parsed and processed.
    Future versions of Tomcat 4 will include administrative functionality that is presented in (at least) the following forms:
    As web services, so that Tomcat administration can be easily integrated into remote and/or non-Java mnagement environments.
    As a web application with a nice user interface (built on top of the web services processing layer) for easy Tomcat administration via a web browser.
    In addition to executing Manager commands directly via HTTP, Tomcat 4 includes a convenient set of task definitions for the Ant (version 1.4 or later) build tool. See Executing Manager Commands With Ant for more information.
    Configuring Manager Application Access
    The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 4, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 4 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
    It would be quite unsafe to ship Tomcat with default settings that allowed anyone on the Internet to execute the Manager application on your server. Therefore, the Manager application is shipped with the requirement that anyone who attempts to use it must authenticate themselves, using a username and password that have the role manager associated with them. Further, there is no username in the default users file ($CATALINA_HOME/conf/tomcat-users.xml) that is assigned this role. Therefore, access to the Manager application is completely disabled by default.
    To enable access to the Manager web application, you must either create a new username/password combination and associate the role name manager with it, or add the manager role to some existing username/password combination. Exactly where this is done depends on which Realm implementation you are using:
    MemoryRealm - If you have not customized your $CATALINA_HOME/conf/server.xml to select a different one, Tomcat 4 defaults to an XML-format file stored at $CATALINA_HOME/conf/tomcat-users.xml, which can be edited with any text editor. This file contains an XML <user> for each individual user, which might look something like this:
    <user name="craigmcc" password="secret" roles="standard,manager" />
    which defines the username and password used by this individual to log on, and the role names he or she is associated with. You can add the manager role to the comma-delimited roles attriute for one or more existing users, and/or create new users with that assigned role.
    JDBCRealm - Your user and role information is stored in a database accessed via JDBC. Add the manager role to one or more existing users, and/or create one or more new users with this role assigned, following the standard procedures for your environment.
    JNDIRealm - Your user and role information is stored in a directory server accessed via LDAP. Add the manager role to one or more existing users, and/or create one or more new users with this role assigned, following the standard procedures for your environment.
    The first time you attempt to issue one of the Manager commands described in the next section, you will be challenged to log on using BASIC authentication. The username and password you enter do not matter, as long as they identify a valid user in the users database who possesses the role manager.
    Supported Manager Commands
    All commands that the Manager application knows how to process are specified in a single request URI like this:
    http://{host}:{port}/manager/{command}?{parameters}
    where {host} and {port} represent the hostname and port number on which Tomcat is running, {command} represents the Manager command you wish to execute, and {parameters} represents the query parameters that are specific to that command. In the illustrations below, customize the host and port appropriately for your installation.
    Most commands accept one or more of the following query parameters:
    path - The context path (including the leading slash) of the web application you are dealing with. To select the ROOT web application, specify a zero-length string. NOTE - It is not possible to perform administrative commands on the Manager application itself.
    war - URL of a web application archive (WAR) file, or pathname of a directory, that contains the web application. You can use URLs in any of the following formats:
    file:/absolute/path/to/a/directory - The absolute path of a directory that contains the unpacked version of a web application. This directory will be attached to the context path you specify without any changes.
    file:/absolute/path/to/a/webapp.war - The absolute path of a web application archive (WAR) file. This is valid only for the /deploy command, and is the only acceptable format to that command.
    jar:file:/absolute/path/to/a/warfile.war!/ - The URL to a local web application archive (WAR) file. You can use any syntax that is valid for the JarURLConnection class for reference to an entire JAR file.
    jar:http://hostname:port/path/to/a/warfile.war!/ - You can also deploy web applications from a remote JAR file. You can use any syntax that is valid for the JarURLConnection class for reference to an entire JAR file.
    Each command will return a response in text/plain format (i.e. plain ASCII with no HTML markup), making it easy for both humans and programs to read). The first line of the response wil begin with either OK or FAIL, indicating whether the requested command was successful or not. In the case of failure, the rest of the first line will contain a description of the problem that was encountered. Some commands include additional lines of information as described below.
    Internationalization Note - The Manager application looks up its message strings in resource bundles, so it is possible that the strings have been translated for your platform. The examples below show the English version of the messages.
    Deploy A New Application
    http://localhost:8080/manager/deploy?path=/foo
    Upload the web application archive (WAR) file that is specified as the request data in this HTTP PUT request, install it into the appBase directory of our corresponding virtual host, and start it on the context path specified by the path request parameter. The application can later be undeployed (and the corresponding application directory removed) by use of the /undeploy.
    NOTE - Since this command requires an HTTP PUT request, it is usable only from tools (such as the custom Ant tasks described below). To install a new web application without copying, consider the /install command described below. This command is the logical opposite of the /undeploy command.
    If installation and startup is successful, you will receive a response like this:
    OK - Deployed application at context path /foo
    Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
    Application already exists at path /foo
    The context paths for all currently running web applications must be unique. Therefore, you must either remove or undeploy the existing web application using this context path, or choose a different context path for the new one.
    Encountered exception
    An exception was encountered trying to start the new web application. Check the Tomcat 4 logs for the details, but likely explanations include problems parsing your /WEB-INF/web.xml file, or missing classes encountered when initializing application event listeners and filters.
    Invalid context path was specified
    The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
    No context path was specified
    The path parameter is required.
    Install A New Application
    http://localhost:8080/manager/install?path=/foo&war=file:/path/to/foo
    http://localhost:8080/manager/install?path=/bar&war=jar:file:/path/to/bar.war!/
    Install and start a new web application, attached to the specified context path (which must not be in use by any other web application). The war parameter specifies a URL (including the file: scheme) for either a directory or a web application archive (WAR) file. The supported syntax for a URL referring to a WAR file is described on the Javadocs page for the java.net.JarURLConnection class. Use only URLs that refer to the entire WAR file. This command is the logical opposite of the /remove command.
    If installation and startup is successful, you will receive a response like this:
    OK - Installed application at context path /foo
    Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
    Application already exists at path /foo
    The context paths for all currently running web applications must be unique. Therefore, you must either remove or undeploy the existing web application using this context path, or choose a different context path for the new one.
    Document base does not exist or is not a readable directory
    The URL specified by the war parameter must identify a directory on this server that contains the "unpacked" version of a web application, or the absolute URL of a web application archive (WAR) file that contains this application. Correct the value specified by the war parameter.
    Encountered exception
    An exception was encountered trying to start the new web application. Check the Tomcat 4 logs for the details, but likely explanations include problems parsing your /WEB-INF/web.xml file, or missing classes encountered when initializing application event listeners and filters.
    Invalid application URL was specified
    The URL for the directory or web application that you specified was not valid. Such URLs must start with file:, and URLs for a WAR file must end in ".war".
    Invalid context path was specified
    The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
    No context path was specified
    The path parameter is required.
    List Currently Deployed and Installed Applications
    http://localhost:8080/manager/list
    List the context paths, current status (running or stopped), and number of active sessions for all currently deployed and installed web applications. A typical response immediately after starting Tomcat might look like this:
    OK - Listed applications for virtual host localhost
    /webdav:running:0
    /examples:running:0
    /manager:running:0
    /:running:0
    Reload An Existing Application
    http://localhost:8080/manager/reload?path=/examples
    Signal an existing application to shut itself down and reload. This can be useful when you've recompiled classes on an application that is not configured with the reloadable="true" attribute in its <Context> entry in $CATALINA_HOME/conf/server.xml, or when you've made other changes (such as to conf/web.xml) that are not automatically recognized by Tomcat.
    If this command succeeds, you will see a response like this:
    OK - Reloaded application at context path /examples
    Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
    Encountered exception
    An exception was encountered trying to restart the web application. Check the Tomcat 4 logs for the details.
    Invalid context path was specified
    The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
    No context exists for path /foo
    There is no deployed or installed application on the context path that you specified.
    No context path was specified
    The path parameter is required.
    Reload note supported on WAR deployed at path /foo
    Currently, application reloading (to pick up changes to the classes or web.xml file) is not supported when a web application is installed directly from a WAR file. It only works when the web application is installed from an unpacked directory. If you are using a WAR file, you should remove and then install the application again to pick up your changes.
    Remove an Existing Application
    http://localhost:8080/manager/remove?path=/examples
    Signal an existing application to gracefully shut itself down, and then remove it from Tomcat (which also makes this context path available for reuse later). This command is the logical opposite of the /install command.
    If this command succeeds, you will see a response like this:
    OK - Removed application at context path /examples
    Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
    Encountered exception
    An exception was encountered trying to remove the web application. Check the Tomcat 4 logs for the details.
    Invalid context path was specified
    The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
    No context exists for path /foo
    There is no deployed or installed application on the context path that you specified.
    No context path was specified
    The path parameter is required.
    Session Statistics
    http://localhost:8080/manager/sessions?path=/examples
    Display the default session timeout for a web application, and the number of currently active sessions that fall within ten-minute ranges of their actual timeout times. For example, after restarting Tomcat and then executing one of the JSP samples in the /examples web app, you might get something like this:
    OK - Session information for application at context path /examples
    Default maximum session inactive interval 30 minutes
    30 - <40 minutes:1 sessions
    Start an Existing Application
    http://localhost:8080/manager/start?path=/examples
    Signal a stopped application to restart, and make itself available again. Stopping and starting is useful, for example, if the database required by your application becomes temporarily unavailable. It is usually better to stop the web application that relies on this database, rather than letting users continuously encounter database exceptions.
    If this command succeeds, you will see a response like this:
    OK - Started application at context path /examples
    Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
    Encountered exception
    An exception was encountered trying to start the web application. Check the Tomcat 4 logs for the details.
    Invalid context path was specified
    The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
    No context exists for path /foo
    There is no deployed or installed application on the context path that you specified.
    No context path was specified
    The path parameter is required.
    Stop an Existing Application
    http://localhost:8080/manager/stop?path=/examples
    Signal an existing application to make itself unavailable, but leave it deployed or installed. Any request that comes in while an application is stopped will see an HTTP error 404, and this application will show as "stopped" on a list applications command.
    If this command succeeds, you will see a response like this:
    OK - Stopped application at context path /examples
    Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
    Encountered exception
    An exception was encountered trying to stop the web application. Check the Tomcat 4 logs for the details.
    Invalid context path was specified
    The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
    No context exists for path /foo
    There is no deployed or installed application on the context path that you specified.
    No context path was specified
    The path parameter is required.
    Undeploy an Existing Application
    http://localhost:8080/manager/undeploy?path=/examples
    WARNING - This command will delete the contents of the web application directory if it exists within the appBase directory (typically "webapps") for this virtual host . If you simply want to take an application out of service, you should use the /remove command instead.
    Signal an existing application to gracefully shut itself down, and remove it from Tomcat (which also makes this context path available for reuse later). In addition, the document root directory is removed, if it exists in the appBase directory (typically "webapps") for this virtual host. This command is the logical opposite of the /deploy command.
    If this command succeeds, you will see a response like this:
    OK - Undeployed application at context path /examples
    Otherwise, the response will start with FAIL and include an error message. Possible causes for problems include:
    Encountered exception
    An exception was encountered trying to undeploy the web application. Check the Tomcat 4 logs for the details.
    Invalid context path was specified
    The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string.
    No context exists for path /foo
    There is no deployed or installed application on the context path that you specified.
    No context path was specified
    The path parameter is required.
    Executing Manager Commands With Ant
    In addition to the ability to execute Manager commands via HTTP requests, as documented above, Tomcat 4 includes a convenient set of Task definitions for the Ant (version 1.4 or later) build tool. In order to use these commands, you must perform the following setup operations:
    Download the binary distribution of Ant from http://jakarta.apache.org/ant. You must use version 1.4 or later.
    Install the Ant distribution in a convenient directory (called ANT_HOME in the remainder of these instructions).
    Copy the file server/lib/catalina-ant.jar from your Tomcat 4 installation into Ant's library directory ($ANT_HOME/lib).
    Add the $ANT_HOME/bin directory to your PATH environment variable.
    Configure at least one username/password combination in your Tomcat user database that includes the manager role.
    To use custom tasks within Ant, you must declare them first with a <taskdef> element. Therefore, your build.xml file might look something like this:
    <project name="My Application" default="compile" basedir=".">
    <-- Configure the directory into which the web application is built -->
    <property name="build" value="${basedir}/build"/>
    <-- Configure the context path for this application -->
    <property name="path" value="/myapp"/>
    <-- Configure properties to access the Manager application -->
    <property name="url" value="http://localhost:8080/manager"/>
    <property name="username" value="myusername"/>
    <property name="password" value="mypassword"/>
    <-- Configure the custom Ant tasks for the Manager application -->
    <taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/>
    <taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
    <taskdef name="list" classname="org.apache.catalina.ant.ListTask"/>
    <taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
    <taskdef name="remove" classname="org.apache.catalina.ant.RemoveTask"/>
    <taskdef name="start" classname="org.apache.catalina.ant.StartTask"/>
    <taskdef name="stop" classname="org.apache.catalina.ant.StopTask"/>
    <taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask"/>
    <-- Executable Targets -->
    <target name="compile" description="Compile web application">
    ... construct web application in ${build} subdirectory ...
    </target>
    <target name="install" description="Install web application"
    depends="compile">
    <install url="${url}" username="${username}" password="${password}"
    path="${path}" war="file://${build}"/>
    </target>
    <target name="reload" description="Reload web application"
    depends="compile">
    <reload url="${url}" username="${username}" password="${password}"
    path="${path}"/>
    </target>
    <target name="remove" description="Remove web application">
    <remove url="${url}" username="${username}" password="${password}"
    path="${path}"/>
    </target>
    </project>
    Now, you can execute commands like ant install to install th applcation to a running instance of Tomcat, or ant reload to tell Tomcat to reload it. Note also that most of the interesting values in this build.xml file are defined as replaceable properties, so you can override their values from the command line. For example, you might consider it a security risk to include the real manager password in your build.xml file's source code. To avoid this, omit the password property, and specify it from the command line:
    ant -Dpassword=secret deploy

  • Tomcat webserver problem

    I have a java servlet based project which I ma trying to run using tomcat 4.1.18 web server. But am facing some problems if somebody could guide me here I would be greatly obliged.
    I have a jar file name TCP.jar I have placed that in directory
    C:\jakarta-tomcat-4.1.18\webapps\TCP\webApp\WEB-INF\lib
    The jsp files have been placed in
    C:\jakarta-tomcat-4.1.18\webapps\TCP\webApp\Render
    In the server.xml file I have added
    <Context path="/mmcp"
         docBase="webapps/TCP/webApp"
         crossContext="false"
         debug="0"
         reloadable="true" >
    </Context>
    </Host>
    </Engine>
    </Service>
    The web.xml file has been modified to
    <servlet>
    <servlet-name>getImage</servlet-name>
    <servlet-class>com.app.TCP.rendering.getImage</servlet-class>
    and
    <servlet-mapping>
    <servlet-name>getImage</servlet-name>
    <url-pattern>/GetImage</url-pattern>
    </servlet-mapping>
    This setup used to work in Tomcat 3.2.4 but with 4.1.18 when I try to get to url
    http://localhost:8080/TCP/GetImage
    I get
    [bold]
    description The requested resource (/mmcp/Controller) is not available.
    [bold]
    Any body out there with any explanations
    </servlet>

    There was a typo in my original post instead of
    <Context path="/mmcp"
    it is
    <Context path="/TCP"

  • Remote Delta link setup problem with Bean / Access Service

    Hello,
    I am trying to setup Remote Delta Link (RDL) between two portals. (Both portals same version - EP 7.0 EHP1 SP 05 - are in the same domain)
    I already have the Remote Role Assignment working without any issues.
    The following have been done successfully:
    1. Same user repository has been setup for both the portals
    2. Setup trust between producer and consumer (SSO working fine)
    3. Producer added and registered succesfully on consumer
    4. Permissions setup on producer and consumer
    4. pcd_service user with required UME actions setup
    I am able to see all the remote content in the Consumer portal.
    When I try to copy the remote content and paste it as local content, I am getting the following error:
    Could not create remote delta link to object 'page id'. Could not connect to the remote portal. The remote portal may be down, there may be a network problem, or your connection settings to the remote portal may be configured incorrectly.
    After increasing the log severity, I am able to see the following in Default Trace:
    com.sap.portal.fpn.transport.Trying to lookup access service (P4-RMI) for connecting to producer 'ess_int' with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
    com.sap.portal.fpn.transport.Unable to lookup access service (P4-RMI) with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
    AbstractAdvancedOperation.handleDirOperationException
    [EXCEPTION]
    com.sap.portal.pcm.admin.exceptions.DirOperationFailedException: Could not retrieve the bean / access service to connect with producer
    Could not retrieve the bean / access service to connect with producer
    Like you can see above, there is some bean / access service which is not retrieved successfully. I am not sure if this is a permission problem on the consumer.
    I have checked that the P4 ports are configured correctly (standard - not changed) and I am able to telnet from producer to consumer (and vice versa) on the P4 port.
    I am stuck at this point and am not able to find any information on this.
    I would really appreciate if some one can point me in the right direction.
    Thank you for reading.
    - Raj

    Hi Raj,
    Please check your config of the P4 port on the producer.  Is it really 50004 (check SystemInfo of the producer)?
    I do think there's a problem with the P4 communication since RDL requires P4 connection.
    Do you have load balanced consumer-producer connection? Please refer to this blog for further details
    Little known ways to create a load balanced Consumer – Producer connection in a FPN scenario
    Regards,
    Dao

  • VPN setup problem

    I have installed Snow Leopard Server on a new XServe. I have updated to 10.6.2.
    Other services are working Related to VPN I have configured the VPN Service using L2TP.
    I have no additional network routing defined.
    Every time I try to setup a connection (from my macbook pro --> running snow leopard 10.6.2) I get the following log messages:
    2009-11-15 14:44:41 CET Incoming call... Address given to client = 192.168.1.160
    Sun Nov 15 14:44:41 2009 : Directory Services Authentication plugin initialized
    Sun Nov 15 14:44:41 2009 : Directory Services Authorization plugin initialized
    Sun Nov 15 14:44:41 2009 : L2TP incoming call in progress from '192.168.1.15'...
    Sun Nov 15 14:44:41 2009 : L2TP received SCCRQ
    Sun Nov 15 14:44:41 2009 : L2TP sent SCCRP
    Sun Nov 15 14:44:41 2009 : L2TP received SCCCN
    Sun Nov 15 14:44:41 2009 : L2TP received ICRQ
    Sun Nov 15 14:44:41 2009 : L2TP sent ICRP
    Sun Nov 15 14:44:41 2009 : L2TP received ICCN
    Sun Nov 15 14:44:41 2009 : L2TP connection established.
    Sun Nov 15 14:44:41 2009 : using link 0
    Sun Nov 15 14:44:41 2009 : Using interface ppp0
    Sun Nov 15 14:44:41 2009 : Connect: ppp0 <--> socket[34:18]
    Sun Nov 15 14:44:41 2009 : sent [LCP ConfReq id=0x1 <asyncmap 0x0> <auth eap> <magic 0x7dd4d1cd> <pcomp> <accomp>]
    Sun Nov 15 14:44:41 2009 : rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1e217556> <pcomp> <accomp>]
    Sun Nov 15 14:44:41 2009 : lcp_reqci: returning CONFACK.
    Sun Nov 15 14:44:41 2009 : sent [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x1e217556> <pcomp> <accomp>]
    Sun Nov 15 14:44:41 2009 : rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <auth eap> <magic 0x7dd4d1cd> <pcomp> <accomp>]
    Sun Nov 15 14:44:41 2009 : sent [LCP EchoReq id=0x0 magic=0x7dd4d1cd]
    Sun Nov 15 14:44:41 2009 : sent [EAP Request id=0x1 Identity ]
    Sun Nov 15 14:44:41 2009 : rcvd [LCP EchoReq id=0x0 magic=0x1e217556]
    Sun Nov 15 14:44:41 2009 : sent [LCP EchoRep id=0x0 magic=0x7dd4d1cd]
    Sun Nov 15 14:44:41 2009 : rcvd [LCP EchoRep id=0x0 magic=0x1e217556]
    Sun Nov 15 14:44:41 2009 : rcvd [EAP Response id=0x1 Identity <"]
    Sun Nov 15 14:44:47 2009 : LCP terminated by peer (Failed to authenticate ourselves to peer)
    Sun Nov 15 14:44:47 2009 : sent [LCP TermAck id=0x2]
    Sun Nov 15 14:44:47 2009 : L2TP received CDN
    Sun Nov 15 14:44:47 2009 : Connection terminated.
    Sun Nov 15 14:44:47 2009 : L2TP disconnecting...
    Sun Nov 15 14:44:47 2009 : L2TP sent CDN
    Sun Nov 15 14:44:47 2009 : L2TP sent StopCCN
    Sun Nov 15 14:44:47 2009 : L2TP disconnected
    2009-11-15 14:44:47 CET --> Client with address = 192.168.1.160 has hungup
    What does that mean:
    "Failed to authenticate ourselves to peer" ???
    Are there some configurations which can solve this problem ???
    Best regards
    Andreas

    This are the related client side log entries:
    Sun Nov 15 14:44:40 2009 : L2TP connecting to server '192.168.1.10' (192.168.1.10)...
    Sun Nov 15 14:44:40 2009 : IPSec connection started
    Sun Nov 15 14:44:40 2009 : IPSec phase 1 client started
    Sun Nov 15 14:44:40 2009 : IPSec phase 1 server replied
    Sun Nov 15 14:44:41 2009 : IPSec phase 2 started
    Sun Nov 15 14:44:41 2009 : IPSec phase 2 established
    Sun Nov 15 14:44:41 2009 : IPSec connection established
    Sun Nov 15 14:44:41 2009 : L2TP sent SCCRQ
    Sun Nov 15 14:44:41 2009 : L2TP received SCCRP
    Sun Nov 15 14:44:41 2009 : L2TP sent SCCCN
    Sun Nov 15 14:44:41 2009 : L2TP sent IRCQ
    Sun Nov 15 14:44:41 2009 : L2TP received ICRP
    Sun Nov 15 14:44:41 2009 : L2TP sent ICCN
    Sun Nov 15 14:44:41 2009 : L2TP connection established.
    Sun Nov 15 14:44:41 2009 : using link 0
    Sun Nov 15 14:44:41 2009 : Using interface ppp0
    Sun Nov 15 14:44:41 2009 : Connect: ppp0 <--> socket[34:18]
    Sun Nov 15 14:44:41 2009 : sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x1e217556> <pcomp> <accomp>]
    Sun Nov 15 14:44:41 2009 : rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <auth eap> <magic 0x7dd4d1cd> <pcomp> <accomp>]
    Sun Nov 15 14:44:41 2009 : lcp_reqci: returning CONFACK.
    Sun Nov 15 14:44:41 2009 : sent [LCP ConfAck id=0x1 <asyncmap 0x0> <auth eap> <magic 0x7dd4d1cd> <pcomp> <accomp>]
    Sun Nov 15 14:44:41 2009 : rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x1e217556> <pcomp> <accomp>]
    Sun Nov 15 14:44:41 2009 : sent [LCP EchoReq id=0x0 magic=0x1e217556]
    Sun Nov 15 14:44:41 2009 : rcvd [LCP EchoReq id=0x0 magic=0x7dd4d1cd]
    Sun Nov 15 14:44:41 2009 : sent [LCP EchoRep id=0x0 magic=0x1e217556]
    Sun Nov 15 14:44:41 2009 : rcvd [EAP Request id=0x1 Identity ]
    Sun Nov 15 14:44:41 2009 : sent [EAP Response id=0x1 Identity <"]
    Sun Nov 15 14:44:47 2009 : Connection terminated.
    Sun Nov 15 14:44:47 2009 : rcvd [EAP Request id=0x2 EAP KRB <00003f000001000101>]
    Sun Nov 15 14:44:47 2009 : L2TP disconnecting...
    Sun Nov 15 14:44:47 2009 : L2TP sent CDN
    Sun Nov 15 14:44:47 2009 : L2TP sent StopCCN
    Sun Nov 15 14:44:47 2009 : L2TP disconnected

  • Setup problem - Extreme no longer found by Mac

    I'm trying to set up an Extreme base station and extend the network with an Express (and use airtunes). I had successfully set up airtunes, but the range was not being extended. After trying to change to a WDS arrangement, I now have a flashing amber light and the base stations are not found by my computer. I've unplugged everything but they are still not recognized.
    Any suggestions? When I get home from work tonight, I'm going to reset to factory default and start over.
    If anyone has an easy step-by-step to set up the network I described above, that would be great too.
    Thanks!!
    ibook g4   Mac OS X (10.4.3)  

    but the range was not being extended.
    WiFi speed will also have been slower over network.
    The speed wasn't the problem, it was the physical range of the network. I was one room away from the Express and had a lousy signal. As I moved closer to the Extreme the signal got stronger. That was when I tried to change to WDS and lost everything.
    I had originally setup the Extreme, then told the Express to "Join an existing network." That worked for Airtunes, but did not extend the range. So I screwed something up when changing to WDS.
    This time, I'll set up the Extreme, then manually configure the Express, both for WDS mode. Hopefully, that will work.
    Yes, the setup guide has point by point instructions,
    but the Airport Utility is a pretty seamless gui for
    the process.
    Not totally seamless - but I'll take some of the blame there!
    ibook g4   Mac OS X (10.4.3)  

  • Setup problem with WRT55AG

    I just got this router today, and I have been trying to set it up for the past 6 hours now and I am vary frustrated.
    I put the CD in and follow the directions step by step.
    I get all the way up to step 9 and it wont go any further.
    At step 9, it says its configuring the router.
    During this time, the router and my connection go on and off sevral times before it ends with no internet connection was detected.
    Just to maybe find an idea of what the problem may be, I went out and got the wireless adapter for my xbox360 and checked to see if it could connect.
    It found the router over the wireless feature.
    It was given an IP by the router, it was also given a subnet mask, and a gateway.
    I ran a test on the network connection and it detected it as wireless, it found the router and was given an IP, but when it got to the DNS checker, it failed.
    Why, I do not know.
    How to fix this, I do not know.
    Note, this is not about the xbox, I just used it as a tool to test the network.
    If anyone know how to get past this step, I would like that vary much.
    Note:
    Since the setup prosess was not compleated.
    I can not accsess the router or any of its features or config pages yet.
    Message Edited by data960 on 09-24-200601:22 AM

    ok 14 hours is quite a bit ...here is what you do .
    unplug the modem from the router. kepp the power to the router turned on. Then hold down the reset buootn for 1 Minute. release the reset after a min and unplug the power from the router as well.
    Now turn on the modem first.wait for 1 min and then turn on the router.restart your PC.
    Once the PC is back up, check if you are able to go online.if yes,cool. if not ....open the router page using http://192.168.1.1 the password is "admin" (no need for the cd....keep it someplace safe) ....
    once in the setup, click on the status page and check if you have an "internet IP address" ( you have not mentioned if you are using a cable or a DSL connection , who is your ISP ? )
    be as it may....lets try and config your XboX ....click on the setup page of the router and look for "MTU" ...change to manual and put in 1365 as the value.
    This should help you....in case this does not , let me know who you ISP is and what model modem you have.

Maybe you are looking for

  • Everytime i try to go to the apps part of itunes to sync my phone it says itunes has stopped working. how do i fix this?

    I just got the new iPhone 5 c. i want to be able to sync all of my stuff an so far it all has except my rintones an text tones. when i try to do it using iTunes it says iTunes has stopped working closes an then just repeats each time i try. i have tr

  • No XML file for VO listed in AM, possible to extend?

    In the AM oracle.apps.ar.hz.components.account.contact.server.HzPuiActContRoleAM the VO HzPuiActRoleListVO exists however there is no XML file for this VO - what am I missing? Is it possible to extend the VO? - Resolved Edited by: user602400 on Jun 1

  • PS elements 12 PS Installation error

    I am unable to install PS elements 12 in my laptop with win 8.1. When I was 1st time installing it, it was appeared a windshield error and rolled back the installation. When I am trying to install it again, I am getting an error 2343: specified path

  • If I have to reset?

    I connected my linksys E1000 21 months ago and after resolving a set up error I made never have had to make a change. I have added a printer, second laptop and three Kindles with no problem. It always has excellent signal strength. When I set the rou

  • 64 bit windows on Mac Pro

    If I use Bootcamp to install a 64 bit version of windows xp pro on a Mac will that allow windows to make full use of the ram installed? I understand that 32 bit versions of win xp only allow access to 4 gigs or so of ram? I take it that the processor