MI client on local PC

Hello guys,
I'm a very new MI user and I have a trouble. I would like to install MI client on my local PC and I don't know how to do it. I have downloaded MI25SP16_0-10002889 file from SAP Market Place. I can see two .jar files (JSP and AWT) in the installer folders. How can I install them?
Thanks all.

Hi,
you just downloaded a delta to upgrade from a lower sp to SP 16.
SAP also ships full builds of the client. PLease refer to the following forum thread (4th message):
Re: MI2.5 SP16 full version
It describes how to download the latest Fullbuild.
Current SP for NW04 is SP18.
Rgds THomas

Similar Messages

  • SharePoint Designer 2013 after installation getting error with runtime i.e. error writing to file Microsoft.SharePoint.Client.Runtime.Local.Resources.dll Verify that you have access to that directory

    SharePoint Designer 2013 after installation getting error with runtime i.e. error writing to file Microsoft.SharePoint.Client.Runtime.Local.Resources.dll Verify that you have access to that directory
    after retry..again SharePoint Designer requires the following component require to install Microsoft.NET framework version 4 i have downloaded and try to installed but fail not work please answer what to do?
    Thanks and Regards, Rangnath Mali

    Hi Rangnath,
    For running SharePoint Designer 2013, you need to install Microsoft .NET 4.0 Framework or higher.
    Please uninstall the Microsoft .NET 4.0 Framework, and install it again. After that, reboot your machine.
    Best Regards,
    Wendy
    Wendy Li
    TechNet Community Support

  • Add-On in client Machine (Local Machine) could not be connected when changed in the Server

    Hi ,
    Add-On Could not be automatically connected in the Client Machine (Local Systems) once if am changing the Add-On in the Server.
    for this am uninstalling the previous version of the SAP Add-On that is installed in the Client Machine and Installing the Add-On Separately in all the other Local Client Machines.
    What could be the reason for this problems?
    Thanks

    Hi,
    Please check this thread:
    http://scn.sap.com/thread/3215229
    Thanks & Regards,
    Nagarajan

  • How to download file from server to client's local ??

    How to download a file from the server to the client's local machine in a particular folder without users intervention ie. 'Save As" prompt of the browser should be avoided and if the client clicks on "Download" button, the file should get automaticaly downloaded to say, "c:/reports/' on his/her local machine. This is for Java based web appliaction.

    http://jguru.com/faq/view.jsp?EID=10646

  • Problem using application client for local stateful session bean

    Hi,
    I have deployed a local stateful session bean in Sun J2EE 1.4 application server.
    On running the applclient for the stateful session bean application client i get the following error:
    Warning: ACC006: No application client descriptor defined for: [null]
    cant we use application client for local stateful session beans. becoz the application runs smoothly when i changed the stateful sesion bean to remote.

    Hi,
    No, an ejb that exposes a local view can only be accessed by an ejb or web component packaged within the same application. Parameters and return values for invocations through the ejb local view are passed by reference instead of by value. That can't work for an application client since it's running in a separate JVM.
    --ken                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Deploying Batch Client in Local Mode (Tutorial problem)

    I'm trying to go through the example in JDev help of "deploying
    the Batch Client in Local Mode"
    I'm using the OrderEntryforClients.JWS file to run this tutorial
    on. I have did everything step by step and when I get to the
    "set the classpath and run your application" part.
    I get the following error when I enter jre javagui.Test
    C:\jdev\batchclient>jre javagui.testclient
    Warning: JIT compiler "symcjit" not found. Will use interpreter.
    Class not found: javagui.testclient
    C:\jdev\batchclient>jre javagui.testclient2
    Warning: JIT compiler "symcjit" not found. Will use interpreter.
    Class not found: javagui.testclient2
    I don't know what to do about this.

    Might be worth having a look at the following post -Where do I find the Instance Name for EPM Batch Script Utility?
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Jabber client using local TMS/VCS account

    I have TMS configured for both AD and local accounts for Jabber accounts. Once I added the AD accounts i could no longer authenticate using the local accounts. Is there a way to use both local and AD authencation for jabber?
    Thanks
    RB                  

    Thanks for the response.
    You are correct.  The error occurs over time after a user has logged into the client.  We've had a variety of issues with with out VCS/TMS/Jabber deployment so it's hard to pinpoint exactly when this started to occur, but it was working at one point.  If i recall corrrectly, this started to crop up after we had to rebuild our provisioning database after an OpenDS failure on the TMS server.  TMS agent diagnostics (both local and for VCSc) complete without error currently.  The error received by a client when searching for an entry that is known to exist is 'no exact match in phonebook'.  Here is a screenshot of all settings we are currently provisioning.....

  • CANNOT_LOAD_BUNDLE_ERR from remote client (same local network).

    Hello,
    We're having problems (as many other people) with remotely connecting (but on same network) Server Monitor (1.8(5)) from a 10.6.4 client to the LOM IP (or FQDN) of our Xserve (model Xserve3,1)(early 2009)(running under 10.6.4)(LOM revision 1.1.8)(Boot ROM versionXS31.0081.B06).
    Although connections of Server Monitor on that Xserve via localhost work fine, connections from the client (a Macbook Pro running 10.6.4) give the infamous CANNOTLOAD_BUNDLEERR.
    Note that connections from the client to our OTHER Xserve (early 2008)(model Xserve2,1)(LOM revision 1.1.2)(Boot ROM Version XS21.006C.B06) work fine (both via localhost and non localhost).
    Please help!
    shawn
    p.s. Here's a list of what didn't help:
    Our LOM Firmware does seem to be up-to-date on both the working Xserve (the one that does allow remote connections) and the not-willing-to-do-remote Xserve. http://support.apple.com/kb/HT3539 (trying to install a LOM updater tells us we're already up to date.. and anyway, the LOM Firmware update should only be for Early2008 Xserves).
    This unsolved archived discussion did not help:
    Server Admin/Monitor Issues (MrHoffman)
    http://discussions.apple.com/thread.jspa?threadID=2325127
    Nor did reading "LOM it up!" (MacTroll) or the discussion that followed.
    http://www.afp548.com/article.php?story=20070211101829496&query=120
    Using Network Utility > Lookup from the client machine shows that the IP address does indeed point to the correct FQDN and vice versa.
    Running, from the client, dig server2.epfl.ch showed the expected IP addresses.
    Running, from the client, dig -x with the returned IP address, showed the expected FQDN.
    Pinging the LOM's FQDN gives me successful ACKs of .200ms.
    Running changeip -checkhostname on the server shows the non-LOM ip address and correct non-LOM FQDN. How do I use changeip to check the LOM hostname and IP address (which is different) ??
    We're not mixing 10.5 and 10.6; Both server and client are using 10.6.4.
    Running ServerMonitor directly on the server (using localhost) works fine.
    ConfigureLocalMachine on the not-working Xserve (call it Xserve2) shows LOM using Ethernet PORT2 (but switching to PORT1 doesn't help). The Subnet-mask and Router values are configured identically to the working Xserve (call it Xserve1) where the config does allow remote access. The version of ServerMonitor on both Xserves and on the clientMacs is 1.8(5). Every machine is 10.6.4.
    The command "ipmitool lan print 2" on Xserve2 reveals the correct IP address and other infos. But the command "ipmitool lan print 1" says that Channel 1 is not a LAN Channel. Is this important? If so, what do I do with this info?
    Ideas from reading LOM No Workie (Faby) don't help.
    http://lists.apple.com/archives/Macos-x-server/2006/Dec/msg00620.html
    I've also uselessly read:
    Xserve User's Guide : http://www.apple.com/support/xserve/
    OS X Server Manuals : http://www.apple.com/server/macosx/resources/documentation.html
    HT2773 document - Xserve (Late 2006 and later): Configuring Lights-Out Management (LOM) : http://support.apple.com/kb/HT2773

    I'm going to skim over some details of IP and IP routing.
    My IP for that NIC on which the LOM is running is 128.178.100.87.
    If I'm reading you correctly, I should NOT have an IP for my LOM (if you say 'correct' then I'm really confused).
    Your LOM needs its own unique IP address.
    This can be a little confusing if you're looking at the hardware, but it's entirely possible to have several separate IP hosts (devices) on one network jack, and each needs its own (unique) address. You're not assigning IP addresses to cables, you're assigning addresses to hosts.
    And if I read you to say that yes 128.178.100.87 should be assigned to the LOM but not the NIC,.. then to what is the LOM attached/configured?
    Well, if two hosts (or even two network controllers on the same host) have the same address (and the LOM is a host), then (best case) the IP traffic on the second host controller to start detects the address collision and won't allow the host to go online. Worst case, traffic gets snarled.
    Finally, it seems that this setup on XserveBAD (an XServe3,1) is the same on XserveGOOD (and Xserve2,1) in terms of IPs NICs and LOMs. The only diff seems to be Xserve versions.
    There was a brief kerfuffle with the Xserve3,1 boxes and the tools back when those boxes first arrived, but that all settled down with current tools and firmware.
    *2. 2nd dual-port NIC*
    YES indeed! You're good! From the Preferences>Network panel I see we have a PCI ethernet with two ports (both XserveBAD & XserveGOOD have this) link-aggretated. To that bond, we've assigned the IP address that people use to ssh into the machines. LOM is not there. XserveBAD's LOM is configured to say +LOM uses ethernet Port 1+ and XserveGOOD's LOM is set to +uses Network1+ (the GUI looks different on the two machines).
    Two networks (also) means you'll have to consider IP routing; which NIC is used to respond to traffic. Inbound IP packet traffic might well arrive at the box, but if the box doesn't have its routing configured "correctly" then the IP packets "outbound" in response might not be sent out the expected controller; the inbound IP traffic and the IP responses don't automatically use the same controller. Those routing determinations are made separately, based on the local subnet, available local static routes, and the rest of the packets get sent to the default router to deal with.
    For both XserveBAD and XserveGOOD, the Preferences>Network panel shows the IP that we configured for the LOM to be the one on 'Ethernet 1" with subnet mask of 255.255.255.0. And in both cases the IP address used for sshing (the one used on the PCI ethernet bonded ports) is on 'Ethernet 0' with subnet mask 255.255.255.0.
    The subnet masks tells IP where the IP packet is going to be set. In the most general of terms, that mask tells IP routing where to send the packet, and that decision (and specifically with the 255.255.255.0 mask) says that if the first three bytes are the same, it's a local address and the messages get sent directly. If the first three bytes differ (and it's not an established route), it goes to the designated "gateway" router.
    p.s. FWIW, I almost went with SadLOM and HappyLOM but I'm still pretending to be a serious mac admin-wannabe here.
    Uh-huh. You'll get over that.
    p.p.s. I didn't catch your drift concerning public/private subnets.. but I'm googling, I'm googling and reading here http://articles.techrepublic.com.com/5100-10878_11-6089187.html
    Your network uses IP addresses in the public static IP space, and IP addresses in one of the private address spaces. (The same would apply if you had IP addresses in different subnets in any of the private IP address blocks, though the use of a public space implies there's a "public" LAN and a private LAN.)
    That looks reasonable as far as it goes, albeit a little stale, and it unfortunately lacks the associated discussion of routing; of why you'd be interested in subnets, and what happens with the packets. The class stuff discussed there is replaced with what's called "CIDR" - classless routing -- and is long gone. (I've been around long enough that the class A, B and C stuff is second nature and old habit, but that "classful" scheme has been replaced with the far more flexible "classless" CIDR scheme.) And the article lists 17 years for IPv4, and the last of the available IPv4 blocks are likely to be handed out within the next few years; we're all dealing with IPv6 now, and its likely that IPv4 addresses are going to get harder to get and probably also more expensive.
    when next you're in Switzerland, I owe you free beers.
    Danke. Der Ratskeller in Zürich war ziemlich gut. Quite a pretty walking area around there too, and with a beautiful view of the river.

  • JDBC thin client downloads locally, not through internet

    Using same code, environment, server, etc,:
    the thin client will download successfully if the server is accessed as part of the internal network. Access with the server outside the local network (via internet) does not seem to download all the parts of the thin client.
    I have tried with the thin client jars (both), and with classess rather than jar (so I can see where it stops).
    The environment is O8iEnterprise, NT server4 (SP6), IIS, JRUN 2.3x, IE5, java 1.2x/applets, 1.3 plugin
    What am I missing for the internet access setup? Thx.

    are you using latest drivers - http://www.oracle.com/technology/tech/java/sqlj_jdbc/index.html
    you may want to check some options reducing jdbc connection cost from the otn samples - http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/index.html

  • WiFi problems - Wireless clients with .local extension?!

    Hi,
    I'm using a Time Capsule with Firmware 7.6.4. Since a few weeks it noticed droputs in my WiFi. It mostly noticeable when I stream videos using my Apple TV and once every 10 minutes the stream stops and needs a minute to buffer again.
    I used the Aiport utility tool as well as WiFi diagnostics and the only thing I noticed is that I have a few wireless clients being listed with a .local extension. Could that be the cause of the problem? How can I resolve this?
    Thanks!

    I am not really sure - I found this doing a quick browse and thought you may find it helpful:
    http://macmost.com/ipad-file-sharing.html
    Rick

  • Support DirectAccess Clients from local lan?

    We've implemented DirectAccess 2012 R2 and are trying to use remote desktop and SCCM remote assistance to support offsite systems connected by DirectAccess.
    I can use a DirectAccess remote client to remote desktop to a local windows system, but I cannot use that same local system to connect to the same remote resource.  I believe this may be a routing issue on our LAN.
    I can Remote Desktop from the direct access server to a DirectAccess remote client.
    Pings fail with "Ping request could not find host testhost01. Please check the name and try again."
    Tracert fails with "Unable to resolve target system name"
    NSlookup returns 3 IPv6 addresses for the host
    This is the last piece of the puzzle to have DA working 100%
    Any pointers?  Places to look?
    Thanks!!

    Hi,
    Do you use IPv6 in your internal network?
    If no, it should not be an issue.
    If the intranet is only using IPv4, NAT64 and DNS64 will be enabled on the DirectAccess server.
    Similar to NAT, the DirectAccess clients are hidden by the NAT64. We can't access a machine behind NAT.
    Best Regards.
    Steven Lee
    TechNet Community Support

  • Can't Connect To Client On Local Network

    I am trying to connect to an iBook that has activated ARD in the Sharing Prefs and cannot get in. I can send messages back and forth, but that is all.
    ARD is 2.2

    Why is the modem connected to the switch? Does it have a dhcp server?
    The box said windows xp or better... So I installed Linux!

  • Local admin priveleges required for Mobile Client

    Anyone overcome a problem with the mobile client requiring local admin priveleges to run?

    hi peter,
    pls see the below urls.......
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/953928ff-0701-0010-43a0-b18b5e6ffeed
    The Passwords Control Panel has a "Remote Administration" tab that
       works only if you have networking installed. If you use a central
       server, you can assign administrative privilege to a SUPERVISOR or
       Domain Admin.
       First, install File & Print Sharing for either MS networks (for a pure
       Win95 or NT domain network) or NetWare (For NetWare networks). If you
       use FPS for NetWare, keep SAP advertising OFF. In addition, install
       the Remote Registry service from Network Control Panel, as a Service
       (in ADMINNETTOOLSREMOTREG on the CD-ROM) on the remote machines. You
       can do this (and even enforce this) when you install Win95 as well.
       Now, if the workstations use User level security (highly
       advisable on NT Domains and NetWare networks), Setup will
       automatically enable remote administration for ADMIN and SUPERVISOR
       (NetWare) or DOMAIN ADMINS (NT Domain). If the stations use passwords
       instead of user lists (Share level security), or you don't have a
       central server, you will need to manually enable Remote Administration
       and supply a password to each station. Remote Administration settings
       will differ with each type of network client installed.
       Once done, you (the administrator) can control computers via Network
       Neighborhood. Right-click on any Win95 station and select
       "Properties". You will see a "Tools" tab that lets you edit the
       Registry, view network activity, or even browse the hard drives, on
       the remote computer. REGEDIT and POLEDIT also works on these stations.
       Of the tools listed, Remote Registry service is the biggest service
       (250 KB). To free up memory so you don't slow down the machines, check
       out How to Prevent Random Hard Drive Access, which also frees
       lots of memory for these services.
    7.6.3.1. ...on a Windows NT network?
       Install FPS for MS networks, install Remote Registry service, and
       enable User level security. Remote Admin privileges are
       automatically given to anyone in the Domain Admins group on the domain
       controller. Re-boot. Then, go to another Win95 station, log in as
       Administrator (or anyone else in Domain Admins) and get properties on
       the remote station from Network Neighborhood.
       WARNING: This service will allow you to remotely edit an NT Server's
       Registry! I was able to get in to several (but not all) Registry keys
       on my own NT server by logging in as a member of Domain Admins. I'd
       hate to think what could happen to my poor server if someone ran
       REGEDIT on this network with malicious intent!
       WARNING: Remember the NetWare C$ bug? It's back, this time in FPS for
       Microsoft networks! Now if you perform a Remote Admin session on a
       Win95 station and view its hard drives, the Admin shares
    machinec$) remain active, available for read-only viewing when a
       user types
    machinec$ from Start Menu/Run. This bug may have always
       been around, but I suspect it emerged with Service Pack 1.
    7.6.3.2. ...on a Peer Win95 network?
       You don't need to install Remote Registry service on the workstations
       to use peer to peer remote administration. You only need a file and
       print sharing service. When you use the Admin tools, the target
       computer will prompt you for a password.
       Be sure to set this password on all the workstations you want to
       administer remotely.
       NOTE: According to the Remote Registry readme files, Remote Registry
       service only works if you use User Level Security from a central
       server.
    7.6.4. ...user level access?
       User Level access spares us the potential of lost passwords and
       multiple, security-killing, cached passwords, because the passwords
       remain on the central security provider. You need only log in once and
       type your password once, and you have access to any resources shared
       on the network that have you on their access list.
       Enable User Level security from Network Control Panel, in Access
       Control. Pick a security provider (the name of an NT domain, NetWare
       server, or other central server if your client/service software allows
       for it). The next time you re-boot, all your share requesters and
       password requesters will have user list requesters in their place. You
       could also enforce user level security via system policies.
       If the server is a NetWare 4.x server, you will need to set a Bindery
       context on it. This will allow all NDS clients access to any Win95
       stations sharing resources via FPS for NetWare.
       Unusual combinations to avoid:
    FPS for MS networks, using a NetWare server as security provider
           (WFWG stations can't get access then! Win95 machines could get
           access, however)
    FPS for NetWare, using an NT server as a security provider (Quite
           impossible, as the NCP server doesn't recognize NT security)
    FPS for NetWare, using Share level security (It won't let you; NCP
           servers don't allow separate logins)
    7.6.5. ...server-based setup and MSBATCH.INF
    thanks
    karthik

  • Jabber for Windows 9.2.5 Local Contacts

    Hi Guys,
         By default, Jabber for Windows 9.2.5, when searching for contacts, it first lists the local Outlook contacts, and then it shows the list of Corportate Directory Contacts.
         Is there a way to show only LDAP contacts?? I don't want the list of local contacts to be available.
    Best Regards,

    In jabber 9.2 you should be able to change this behavior from the client as well.
    http://tools.cisco.com/squish/c5cB2
    Local Contacts in Microsoft Outlook
    Cisco Jabber for Windows lets users search for and add local contacts in Microsoft Outlook.
    To search for local contacts in Microsoft Outlook with the client, users must have profiles set in Microsoft Outlook. In addition, users must do the following:
        Select File > Options.
        Select the Integration tab.
        Select either None or Microsoft Outlook.
    To add local Microsoft Outlook contacts to contact lists in the client, local contacts must have instant message addresses in Microsoft Outlook.
    To show contact photos in the client interface, local contacts in Microsoft Outlook must have instant message addresses.
    To communicate with local contacts in Microsoft Outlook using the client, local contacts must have the relevant details. To send instant messages to contacts, local contacts must have an instant message address. To call contacts in Microsoft Outlook, local contacts must have phone numbers.
    An additional step if needed. If you add this line to the XML and the Outlook contacts still show, you may want to delete the cache in order to remove locally cached contacts.
    This cache can be found under:
    %USER_PROFILE%\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\
    Hope this helps as well!

  • Subnet mask 255.255.255.255 assigned to VPN client - can't ping LAN

    Hi,
    I configured PIX 501 with PPTP VPN to connect to the small office (PIX FW, Win 2000 Server, several Win clients, LAN IP 10.0.0.X/24):
    ip local pool mypool 10.0.0.101-10.0.0.105
    vpdn group mygroup accept dialin pptp
    vpdn group mygroup ppp authentication mschap
    vpdn group mygroup ppp encryption mppe 128 required
    vpdn group mygroup client configuration address local mypool
    vpdn group mygroup client configuration dns 10.0.0.15
    vpdn group mygroup pptp echo 60
    vpdn group mygroup client authentication local
    vpdn username xxxx password *********
    vpdn enable outside
    I can connect to the office using Win VPN client, but I can't ping any hosts in the office network. I suspect that the reason for that is subnet mask assigned to the VPN client: 255.255.255.255. ipconfig of the VPN client:
    PPP adapter Office:
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 10.0.0.101
    Subnet Mask . . . . . . . . . . . : 255.255.255.255
    Default Gateway . . . . . . . . . :
    Default GW is missing too, but I think this is not the main problem.
    Any way, what is wrong with my config? How to fix subnet mask assigned to clients? Or may be my assumption is wrong and this mask is ok? What is wrong then?
    Any input will be greatly appreciated!
    George

    Thanks for the prompt reply.
    Here it does:
    PIX Version 6.3(4)
    interface ethernet0 auto
    interface ethernet1 100full
    nameif ethernet0 outside security0
    nameif ethernet1 inside security100
    enable password xxxxxxxxxxxxxx encrypted
    passwd xxxxxxxxxxxxxx encrypted
    hostname OSTBERG-PIX
    fixup protocol dns maximum-length 512
    fixup protocol ftp 21
    fixup protocol h323 h225 1720
    fixup protocol h323 ras 1718-1719
    fixup protocol http 80
    fixup protocol rsh 514
    fixup protocol rtsp 554
    fixup protocol sip 5060
    fixup protocol sip udp 5060
    fixup protocol skinny 2000
    fixup protocol smtp 25
    fixup protocol sqlnet 1521
    fixup protocol tftp 69
    names
    access-list 80 permit ip 10.0.0.0 255.255.255.0 10.0.20.0 255.255.255.0
    access-list inbound permit icmp any any
    access-list inbound permit tcp any any eq pptp
    access-list inbound permit gre any any
    pager lines 24
    mtu outside 1500
    mtu inside 1500
    ip address outside 66.189.xxx.xxx 255.255.252.0
    ip address inside 10.0.0.23 255.255.255.0
    ip audit info action alarm
    ip audit attack action alarm
    ip local pool mypool 10.0.0.101-10.0.0.105
    pdm location 10.0.0.0 255.255.255.0 inside
    pdm location 10.0.0.15 255.255.255.255 inside
    pdm logging informational 100
    pdm history enable
    arp timeout 14400
    global (outside) 1 interface
    nat (inside) 1 0.0.0.0 0.0.0.0 0 0
    access-group inbound in interface outside
    route outside 0.0.0.0 0.0.0.0 66.189.yyy.yyy 1
    timeout xlate 0:05:00
    timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
    timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
    timeout uauth 0:05:00 absolute
    aaa-server TACACS+ protocol tacacs+
    aaa-server TACACS+ max-failed-attempts 3
    aaa-server TACACS+ deadtime 10
    aaa-server RADIUS protocol radius
    aaa-server RADIUS max-failed-attempts 3
    aaa-server RADIUS deadtime 10
    aaa-server LOCAL protocol local
    http server enable
    http 192.168.1.0 255.255.255.0 inside
    no snmp-server location
    no snmp-server contact
    snmp-server community public
    no snmp-server enable traps
    floodguard enable
    sysopt connection permit-ipsec
    sysopt connection permit-pptp
    telnet 10.0.0.23 255.255.255.255 inside
    telnet 10.0.0.0 255.255.255.0 inside
    telnet timeout 5
    ssh timeout 5
    console timeout 0
    vpdn group mygroup accept dialin pptp
    vpdn group mygroup ppp authentication mschap
    vpdn group mygroup ppp encryption mppe 128 required
    vpdn group mygroup client configuration address local mypool
    vpdn group mygroup client configuration dns 10.0.0.15
    vpdn group mygroup pptp echo 60
    vpdn group mygroup client authentication local
    vpdn username ********* password *********
    vpdn enable outside
    dhcpd lease 3600
    dhcpd ping_timeout 750
    dhcpd auto_config outside
    terminal width 80
    Cryptochecksum:xxx
    : end
    There are remnants of old config, I just recently took over this network, some lines look odd to me, but I did not touch what works. VPN config is all mine.
    PIX internal 10.0.0.23 - is a gateway for the network. DNS server in LAN - 10.0.0.15.
    I've been reading about the problem and came across several posts that this subnet mask is normal, but it puzzles me - how can this host communicate with anyone else if there is no room for other hosts in this network (according to the mask)?!
    Thanks again!
    George

Maybe you are looking for