Shared Comment Problems!

Hi, all! My company has been using the Adobe Shared Comments feature for some time now with a lot of success but for the past month or two, we've been having a number of odd problems.
The issue that i'm looking at now is that i have a few users that can see SOME comments but other comments are not showing up in the document. Other users can see all of the comments just fine. The users that are having the problem can see the comment placeholder icon but when they hover over it or try to click it, nothing happens. While on other comments, it works just fine. To make matters worse, it's not even confined to comments from a particular user. The people experiencing the issues can see some of "John's" comments in a particular document but not all of them.
Most of my users are still using a Acrobat 8.x Pro, although some of them are using more up to date versions. Also, the users computer OS's vary from Windows XP to Windows 7 (i don't know if that's important but i figured i'd throw it out there).
Has anyone out there seen this before? As this has been an ongoing problem for some time now, i'd really love to get it resolved.
Thanks!

Hi, Priyanja. Once again, thanks for continuing to follow up. I'll try to answer as best i can:
This is happening on ALL reviews.
1. So, it appears that the comments ARE readable from the Comments list. When i hover my mouse over a comment balloon in the doc, nothing shows up but i can see it in the comments list. (didn't even think to look at that, so thanks a lot for pointing that out!)
2. I did this and it compiled all of the comments into the document but i still could not view the problem comments.
3. I'm trying to do this step now but apparently everyone is in a meeting and i can't get access to their computers. i'll try to do this a bit later today and respond.
The computer that i'm working on has Adobe Acrobat XI Pro installed on it. Just FYI, the computer that created the document has Adobe Acrobat 8.1.0 Professional on it.
Thanks!

Similar Messages

Shared Review problem for remote review SME

One of my SMEs works offsite via a VPN connection. When she tries to participate in the shared review process from the PDF location on the network drive, she has display problems (all the text is highlighted in black) and she can't "connect" to see other's comments. The PDF displays fine if she downloads it to her hard drive she can see shared comments but of course is then unable interact with the shared process.
She's developed an elaborate and time consuming work around, but I need a solution for her problem. She's using the current version of Reader and I'm generating PDFs using Acrobat 9 Pro Extended.
This is not an issue for any of my other offsite SMEs.
Thoughts?

What are the instructions for Acrobat Pro v11.0.10?
There is no option to save as "Archive copy" only "PDF-X/A" but that returns an error that it can't be saved.
All instances of Shared Review sessions have been removed from the the "Tracker..." dialog, but I am still getting server pings. By all rights, there should be no more pings to any server. When I am actually in my network where the server is visible, Adobe is connecting without my permission.
How can I get the server pings to completely stop in Acrobat Pro v11.0.10?

Acrobat Shared Review Problem

One of my offsite SMEs cannot view PDFs I generate for Acrobat shared review. None of my other offsite SMEs report the same problem and all access the network using the same VPN. In her case, the PDF displays with the text blacked out (as though it's highlighted) and she's unable to connect to view existing shared comments or to add her comments. She's developed a work around (saving files and opening them from her hard drive), however, this removes her from the shared review process.
She uses the most current version of Acrobat Reader and I generate my PDFs using Acrobat 9 Pro Extended.
Thoughts?

A couple of questions:
1. Is she able to see the file contents if she chooses to work offline in the shared review by selecting 'Work Offline' option from the yellow colored bar on top in the shared review when opened in Reader?
2. Does this occur with every shared review file that she is opening or with some specific PDFs only?
3. Which Reader version does she have?
Thanks,
-Amboo

Is XML Publisher causing shared memory problem..?

Hi Experts,
Since this week, many of the Requisition/PO are erroring out with the below errors or similar to these errors:
- ORA-04031: unable to allocate 15504 bytes of shared memorny ("sharedpool","PO_REQAPPROVAL_INIT1APPS","PL/SQL MPCODE","BAMIMA: Bam Buffer")
ORA-06508: PL/SQL: could not find program unit being called.
-Error Name WFENG_COMMIT_INSIDE
3146: Commit happened in activity/function
'CREATE_AND_APPROVE_DOC:LAUNCH_PO_APPROVAL/PO_AUTOCREATE_DOC.LAUNCH_PO_APPROVAL'
Process Error: ORA-06508: PL/SQL: could not find program unit being called
Few days back we were getting heap memory error for one of the XML Publisher report.
I heard that XML Publisher requires lot of memory for sources/features,So I want to know whether XML Publisher can be one of the cause for memory problem to occur or this shared memory is not related with XML Publisher sources at all.
Please advice.
Many thanks..
Suman
Edited by: suman.g on 25-Nov-2009 04:03

Hi Robert,
Thanks for your quick reply...
Apps version: 11.5.10.2
database version: 9.2.0.8.0
As I am a beginner in this so dont know much about this.. Can you please guide me on this.
DBAs has increased the shared memory and problem has resolved but here I am more concrened whether the XML Publisher was or can be one od the cause for shared memory problem. Is there any way to check that or this occurs randomly and we can not check this.
Please advice something.

Downloaded & Installed Photoshop Elements/Shared Technologies Problem. What do I do?

I downloaded & Installed Photoshop Elements 11. There is a Shared Technologies Problem. What do I do? It says to reinstall the whole program. Do I need to do that?

Refer to this:
Troubleshoot installation | Photoshop Elements, Premiere Elements | Windows
Mylenium

Sharing, commenting, and collaborating

This question was posted in response to the following article: http://help.adobe.com/en_US/story/cs/using/WSc1b83f70210cd10152ae9eb112456822b9f-8000.html

1) An organizational observation:
To view all these topics (and the associated sub-parts) in this "Sharing, commenting, and collaborating" section, requires a lot of link clicking. It would be better to put all or most of these topics on a single page.
2) I think it would be good to clarify the differences between sharing documents and sharing scripts.
Jeff

Please I ask the admins and moderaters delet my comment: "problema en activacion despues de reinstal

Please I ask the admins and moderaters delet my comment: "problema en activacion despues de reinstalar sistema "

Done!

Solution to the "Disappearing Comments" problem with shared reviews

I've been having repeated problems with users losing their comments on shared reviews, hosted on my webDAV server. After tearing my hair out for days, I wanted to share the simple fix to this issue, plus another tip:
DON'T USE PERIODS OR SPACES IN FILE NAMES. Use hyphens and underscores instead.
Illegal characters seem to gradually corrupt the file to the point where potentially every comment can get overwritten with a blank .xml file, permanently losing all your comments.
My wish to Adobe is that they would put a pop-up warning at the time of saving a file for shared reviews, something to the effect of:
"WARNING! saving a shared file with a space or a period could result in data corruption when shared over network drives or webDAV. Do you want to replace illegal characters with underscores?"
My other tip is this:
If using a webDAV server as I am, be sure to use the IP address rather than the domain name when specifying the location of the server.

With all the issues you describe, I would search for something conflicting with Mountain Lion.
Have you booted into Safe Mode and checked to see if it works correctly there? It will take a while to boot, and it will run a bit slow, so just look for the issues you described above. If they don't appear, you've got something installed that is causing the issues.

Sharing network problem - again

Hi, i hoped to avoid posting this problem, but i just can't get internet sharing working!
My setup is this: I have a PC connected directly to a adsl-modem via a netcard, and via a second netcard (and a crossed cable) i have a second PC connected to the first, both are running Archlinux, the first is up to date, but the second is 0.6 (since i can't update...).
The 2 PC's have no problems communicating, ping and ssh is working perfectly both ways.
To share the connection, i have this in the rc.conf:
The one connected to the modem:
lo="lo 127.0.0.1"
eth0="dhcp"
eth1="eth1 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES="lo eth0 eth1"
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
The one needing the connection:
lo="lo 127.0.0.1"
eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255"
#eth0="dhcp"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
And i have this "firewall" installed on the one connected to the internet:
#!/bin/sh
# rc.firewall-2.4
FWVER=0.75
# Initial SIMPLE IP Masquerade test for 2.4.x kernels
# using IPTABLES.
# Once IP Masquerading has been tested, with this simple
# ruleset, it is highly recommended to use a stronger
# IPTABLES ruleset either given later in this HOWTO or
# from another reputable resource.
# Log:
# 0.75 - Added more kernel modules to the comments section
# 0.74 - the ruleset now uses modprobe vs. insmod
# 0.73 - REJECT is not a legal policy yet; back to DROP
# 0.72 - Changed the default block behavior to REJECT not DROP
# 0.71 - Added clarification that PPPoE users need to use
# "ppp0" instead of "eth0" for their external interface
# 0.70 - Added commented option for IRC nat module
# - Added additional use of environment variables
# - Added additional formatting
# 0.63 - Added support for the IRC IPTABLES module
# 0.62 - Fixed a typo on the MASQ enable line that used eth0
# instead of $EXTIF
# 0.61 - Changed the firewall to use variables for the internal
# and external interfaces.
# 0.60 - 0.50 had a mistake where the ruleset had a rule to DROP
# all forwarded packets but it didn't have a rule to ACCEPT
# any packets to be forwarded either
# - Load the ip_nat_ftp and ip_conntrack_ftp modules by default
# 0.50 - Initial draft
echo -e "nnLoading simple rc.firewall version $FWVER..n"
# The location of the iptables and kernel module programs
# If your Linux distribution came with a copy of iptables,
# most likely all the programs will be located in /sbin. If
# you manually compiled iptables, the default location will
# be in /usr/local/sbin
# ** Please use the "whereis iptables" command to figure out
# ** where your copy is and change the path below to reflect
# ** your setup
#IPTABLES=/sbin/iptables
IPTABLES=/usr/sbin/iptables
DEPMOD=/sbin/depmod
MODPROBE=/sbin/modprobe
#Setting the EXTERNAL and INTERNAL interfaces for the network
# Each IP Masquerade network needs to have at least one
# external and one internal network. The external network
# is where the natting will occur and the internal network
# should preferably be addressed with a RFC1918 private address
# scheme.
# For this example, "eth0" is external and "eth1" is internal"
# NOTE: If this doesnt EXACTLY fit your configuration, you must
# change the EXTIF or INTIF variables above. For example:
# If you are a PPPoE or analog modem user:
# EXTIF="ppp0"
EXTIF="eth0"
INTIF="eth1"
echo " External Interface: $EXTIF"
echo " Internal Interface: $INTIF"
#======================================================================
#== No editing beyond this line is required for initial MASQ testing ==
echo -en " loading modules: "
# Need to verify that all modules have all required dependencies
echo " - Verifying that all kernel modules are ok"
$DEPMOD -a
# With the new IPTABLES code, the core MASQ functionality is now either
# modular or compiled into the kernel. This HOWTO shows ALL IPTABLES
# options as MODULES. If your kernel is compiled correctly, there is
# NO need to load the kernel modules manually.
# NOTE: The following items are listed ONLY for informational reasons.
# There is no reason to manual load these modules unless your
# kernel is either mis-configured or you intentionally disabled
# the kernel module autoloader.
# Upon the commands of starting up IP Masq on the server, the
# following kernel modules will be automatically loaded:
# NOTE: Only load the IP MASQ modules you need. All current IP MASQ
# modules are shown below but are commented out from loading.
# ===============================================================
echo "----------------------------------------------------------------------"
#Load the main body of the IPTABLES module - "iptable"
# - Loaded automatically when the "iptables" command is invoked
# - Loaded manually to clean up kernel auto-loading timing issues
echo -en "ip_tables, "
$MODPROBE ip_tables
#Load the IPTABLES filtering module - "iptable_filter"
# - Loaded automatically when filter policies are activated
#Load the stateful connection tracking framework - "ip_conntrack"
# The conntrack module in itself does nothing without other specific
# conntrack modules being loaded afterwards such as the "ip_conntrack_ftp"
# module
# - This module is loaded automatically when MASQ functionality is
# enabled
# - Loaded manually to clean up kernel auto-loading timing issues
echo -en "ip_conntrack, "
$MODPROBE ip_conntrack
#Load the FTP tracking mechanism for full FTP tracking
# Enabled by default -- insert a "#" on the next line to deactivate
echo -en "ip_conntrack_ftp, "
$MODPROBE ip_conntrack_ftp
#Load the IRC tracking mechanism for full IRC tracking
# Enabled by default -- insert a "#" on the next line to deactivate
echo -en "ip_conntrack_irc, "
$MODPROBE ip_conntrack_irc
#Load the general IPTABLES NAT code - "iptable_nat"
# - Loaded automatically when MASQ functionality is turned on
# - Loaded manually to clean up kernel auto-loading timing issues
echo -en "iptable_nat, "
$MODPROBE iptable_nat
#Loads the FTP NAT functionality into the core IPTABLES code
# Required to support non-PASV FTP.
# Enabled by default -- insert a "#" on the next line to deactivate
echo -en "ip_nat_ftp, "
$MODPROBE ip_nat_ftp
#Loads the IRC NAT functionality into the core IPTABLES code
# Required to support NAT of IRC DCC requests
# Disabled by default -- remove the "#" on the next line to activate
#echo -e "ip_nat_irc"
#$MODPROBE ip_nat_irc
echo "----------------------------------------------------------------------"
# Just to be complete, here is a partial list of some of the other
# IPTABLES kernel modules and their function. Please note that most
# of these modules (the ipt ones) are automatically loaded by the
# master kernel module for proper operation and don't need to be
# manually loaded.
# ip_nat_snmp_basic - this module allows for proper NATing of some
# SNMP traffic
# iptable_mangle - this target allows for packets to be
# manipulated for things like the TCPMSS
# option, etc.
# ipt_mark - this target marks a given packet for future action.
# This automatically loads the ipt_MARK module
# ipt_tcpmss - this target allows to manipulate the TCP MSS
# option for braindead remote firewalls.
# This automatically loads the ipt_TCPMSS module
# ipt_limit - this target allows for packets to be limited to
# to many hits per sec/min/hr
# ipt_multiport - this match allows for targets within a range
# of port numbers vs. listing each port individually
# ipt_state - this match allows to catch packets with various
# IP and TCP flags set/unset
# ipt_unclean - this match allows to catch packets that have invalid
# IP/TCP flags set
# iptable_filter - this module allows for packets to be DROPped,
# REJECTed, or LOGged. This module automatically
# loads the following modules:
# ipt_LOG - this target allows for packets to be
# logged
# ipt_REJECT - this target DROPs the packet and returns
# a configurable ICMP packet back to the
# sender.
echo -e " Done loading modules.n"
#CRITICAL: Enable IP forwarding since it is disabled by default since
# Redhat Users: you may try changing the options in
# /etc/sysconfig/network from:
# FORWARD_IPV4=false
# to
# FORWARD_IPV4=true
echo " Enabling forwarding.."
echo "1" > /proc/sys/net/ipv4/ip_forward
# Dynamic IP users:
# If you get your IP address dynamically from SLIP, PPP, or DHCP,
# enable this following option. This enables dynamic-address hacking
# which makes the life with Diald and similar programs much easier.
echo " Enabling DynamicAddr.."
echo "1" > /proc/sys/net/ipv4/ip_dynaddr
# Enable simple IP forwarding and Masquerading
# NOTE: In IPTABLES speak, IP Masquerading is a form of SourceNAT or SNAT.
# NOTE #2: The following is an example for an internal LAN address in the
# 192.168.0.x network with a 255.255.255.0 or a "24" bit subnet mask
# connecting to the Internet on external interface "eth0". This
# example will MASQ internal traffic out to the Internet but not
# allow non-initiated traffic into your internal network.
# ** Please change the above network numbers, subnet mask, and your
# *** Internet connection interface name to match your setup
#Clearing any previous configuration
# Unless specified, the defaults for INPUT and OUTPUT is ACCEPT
# The default for FORWARD is DROP (REJECT is not a valid policy)
echo " Clearing any existing rules and setting default policy.."
$IPTABLES -P INPUT ACCEPT
$IPTABLES -F INPUT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -F OUTPUT
$IPTABLES -P FORWARD DROP
$IPTABLES -F FORWARD
$IPTABLES -t nat -F
echo " FWD: Allow all connections OUT and only existing and related ones IN"
$IPTABLES -A FORWARD -i $EXTIF -o $INTIF -m state --state ESTABLISHED,RELATED -j ACCEPT
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT
$IPTABLES -A FORWARD -j LOG
echo " Enabling SNAT (MASQUERADE) functionality on $EXTIF"
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE
echo -e "nrc.firewall-2.4 v$FWVER done.n"
And to start it:
#!/bin/sh
# chkconfig: 2345 11 89
# description: Loads the rc.firewall-2.4 ruleset.
# processname: firewall-2.4
# pidfile: /var/run/firewall.pid
# config: /etc/rc.d/rc.firewall-2.4
# probe: true
# v05/24/03
# Part of the copyrighted and trademarked TrinityOS document.
# http://www.ecst.csuchico.edu/~dranch
# Written and Maintained by David A. Ranch
# [email protected]
# Updates
# 05/24/03 - removed a old networking up check that had some
# improper SGML ampersand conversions.
# Source function library.
. /etc/rc.d/functions
# Check that networking is up.
[ "XXXX${NETWORKING}" = "XXXXno" ] && exit 0
[ -x /sbin/ifconfig ] || exit 0
# The location of various iptables and other shell programs
# If your Linux distribution came with a copy of iptables, most
# likely it is located in /sbin. If you manually compiled
# iptables, the default location is in /usr/local/sbin
# ** Please use the "whereis iptables" command to figure out
# ** where your copy is and change the path below to reflect
# ** your setup
IPTABLES=/usr/sbin/iptables
# See how we were called.
case "$1" in
start)
/etc/rc.firewall-2.4
stop)
echo -e "nFlushing firewall and setting default policies to DROPn"
$IPTABLES -P INPUT DROP
$IPTABLES -F INPUT
$IPTABLES -P OUTPUT DROP
$IPTABLES -F OUTPUT
$IPTABLES -P FORWARD DROP
$IPTABLES -F FORWARD
$IPTABLES -F -t nat
# Delete all User-specified chains
$IPTABLES -X
# Reset all IPTABLES counters
$IPTABLES -Z
restart)
$0 stop
$0 start
status)
$IPTABLES -L
mlist)
cat /proc/net/ip_conntrack
echo "Usage: firewall-2.4 {start|stop|status|mlist}"
exit 1
esac
exit 0
But it just won't work! If you can spot any problems please let me know!
UPDATE:
Just talked to my ISP, and they tell me that my IP-adress is locked to one PC. Could this be the problem? or does the forwarding handles this as well?

Hey tgc, thank you for posting your problem so generously explained!
I had no idea of how to do it, and I only had to change a small obvious typo to make it work. At least I suppose the typo is the reason for your sharing not to work....
Lets see...did you change the
eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.0.255"
to
eth0="eth0 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255"
just now? I'm sure I had to change that, but I have a strange memory
So, the way the configuraton looks now, works perfectly for sharing my isdn connection with my laptop over wlan.
Desktop: isdn, eth0 -> wireless router / hub
Laptop: wlan0
So, what I'm saying anyway, is that your configuration works for me Thanks!

Acrobat 9.0 Shared Review problem

Hello,
I upgraded to Acrobat 9.0 professional from 8.0 professional, and can no longer create a shared review. I did a complete uninstall of 8.0 prior to the 9.0 installation. I am running Windows XP Professional w/ Service Pack 3 on a Core2 Quad CPU @ 2.40 GHz using 3.25 GB RAM.
I have never had any issues with the shared review on Acrobat 8.0, but now just prior to completing the setup process for the review, I receive a dialog message stating "Status: Could not save the shared review-enabled PDF file". Options include: Retry (non-productive) and Cancel (which does work). "Cancel" terminates the process.
What leads up to this event is similar to the routine I followed under Acrobat 8.0.
1. Save pdf from FrameMaker.
2. Move pdf to publicly accessible folder on network.
3. Open pdf.
4. Select Comments > Send for Shared Review...
5. Select "Automatically collect comments on my own internal server".
6. Click Next.
7. Select "Network folder" radio button.
8. Click Browse to navigate to pdf location. Status confirms that "Shared folder location is valid".
9. Click Next.
10. Select "Send it automatically using Adobe Acrobat" radio button.
11. Select "As a link within the message".
12. Click Next.
13. Type a name for the server profile (e.g. "Test")
14. Click Next.
15. Click To and add addressee(s).
16. Click Send. "Create Shared Review" dialog box states "Status: Could not save the shared review-enabled PDF file".
17. Click Cancel.
I have searched for this message ("Status: Could not save the shared review-enabled PDF file") and only found a TechNote indicating that "...with Acrobat 9.0 you no longer need to Reader-enable a PDF before you send it for Shared Review; this is done automatically." I'm not doing this, so it appears to be unrelated to my problem.
Does anyone have any suggestions? Sorry for the long post and thanks for any help.
Jeff Skogstad
Technical Publications
Cirrus Design Corporation

We are getting this on certain machines and not others. I can't seem to be able to find a rhyme or reason. We are trying to initiate reviews on a shared internal network location.
A few questions for the forum:
Does Owner rights matter on the share that the review file is to be stored in? Currently we have Modify rights for all participants and initiators.
Does it make a difference which updates are installed past 9.0? Does it make a difference if Pro and Reader are installed?
Can someone confirm that the Acrobat.com is required to be installed on the machine? I noticed on the latest installs of reader acrobat.com application is not installed.
I'm posting this now because I haven't seen a clear cut answer to:
Could not save the shared review-enabled PDF file

Shared review problems today?

We've been using Acrobat.com for our shared reviews for a few
weeks now without issue. Today, while one can go to acrobat.com in
the Share area and see/download files, no one is able to connect to
the server once in Acrobat to collaborate reviews.
This is not a local issue. It worked fine for everyone
before. It's just today that folks *in different locations* are
reporting that they are unable to connect from within Adobe Reader
9 or Acrobat Pro. It seems clear that there's a problem on Adobe's
end here, and it's frustrating to have nowhere to go for a status
update on the service.
In the meantime, I've emailed the comment-enabled file around
and have instructed everyone to "work offline" to get me edits. Not
efficient at all.

FYI, I have included an answer in your
other
duplicate posting...
Cheers,
Pete

File sharing network problem

I have an Airport Extreme (G) base station with an Airport Express acting as a WDS extender. I have two client Macs - a 24" iMac (Intel Dual Core) and an iBook (G4). There are a variety of other clients as well - 2 wireless-G tivos, a Win XP laptop, a wireless ethernet bridge serving a slingbox.
My problem is with the two Macs. Using Network browser, from the iMac, I can connect to the iBook just fine via AFP. However, when I try to connect to the iMac from the iBook, it tries to use FTP, then I get the error "unable to find alias." Both macs have AppleTalk enabled and both have File Sharing enabled.
I suspect that the root of the problem may be from the fact that the iMac was set up by copying everything over from an older iMac FP (I've learned my lesson and will not use the Migration Assistant again!). But, I can't figure out how to correct this.
Thanks!

Hi franki, I'm glad those web sites were useful.
Unfortunately I can't advise about your remaining problem because I don't have a suitable Windows computer to try things out on. Maybe somebody else here can.
I'd suggest you give a few more details about exactly how far you get and at which point things get stuck.
Also, if nobody on this board can help then you could try another one. There are several boards here related to networking, of which the Tiger Forums Getting Online & Networking one seems to be the most lively.
MacBook (OS 10.4.8) iMac G4 (OS 10.3.9)

Screen Sharing/network problem seems confined to 1 volume. What's the fix?

I am having a networking problem on one of the volumes of my multi-volumed, three-Mac local area network, and I need a networking guru to identify the specific software file(s), application(s), or system configuration that is the cause of the problem. I have already spent several hours checking and re-checking the various hardware and system preference settings involved, and I have narrowed the problem down to a software corruption issue and/or system configuration issue on one volume.
I now need someone to identify specifically what the nature of the problem is, and how to eliminate it. I am not looking for a sledgehammer solution that says I should re-install all of the Mac OS X software on the problem volume. That may be held in reserve as a last resort. I'm looking for a more elegant approach, one that points out the specific corrupt files to remove without disturbing everything else.
Here's some background to set the context. I have a MacBook Pro laptop; a PowerMac iMac G5; and a PowerMac G4 hooked up in a network. All are running Leopard 10.5.8. All have file sharing and screen sharing enabled. Besides being able to connect to each other using registered users, my goal here is for each of the Macs to be able to share the screen of the others upon my demand. Since each of the 3 Macs can theoretically share the screens of the other 2, that makes a total of six possible connections. Five succeed; one does not. That's the problem. I am trying to determine why the iMac G5 cannot share the screen of the MacBook Pro.
The iMac G5 has no problem sharing the screen of the PowerMac G4. That connection is fast and immediate. But, every time that I hit the Share Screen button on the iMac G5 to try to connect to the MacBook Pro, I get a window with the blue barber pole spinning for two or three minutes as it is allegedly "Connecting to Mac Book Pro," followed by a window with a headline telling me that "Connection Failed to MacBook Pro." The text within that window goes on to say: "Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer to which you are attempting to connect. Also make sure that your network connection is working properly."
Well, as I indicated, the PowerMac G4 has no problem sharing the screen of the MacBook Pro, so the Screen Sharing settings on the laptop are correct; and the iMac G5 can share the screen of the PowerMac G4, so its network connection is working properly in that regard. It is only in regards to sharing the screen of the MacBook Pro that the iMac G5 is not working properly.
The reason why I say that the issue must be unique to the one volume in question, let's call it "iMacG5 Music," is that another Leopard volume on the same computer has no problem whatsoever in sharing the screen of the MacBook Pro. Whenever I boot up in that volume, let's call it "iMacG5 JMB," it makes a network connection with a registered user name immediately, and it is able to share the screen of the MacBook Pro within a second of my issuing the command. In sharp contrast to the success of the iMacG5 JMB volume, the iMacG5 Music is unacceptably slow (several minutes slow!) in making a network connection with the MacBook Pro, and it always fails to share the screen of the MacBook Pro, preferring instead to take about three minutes to attempt the connection, before announcing its failure.
Since the iMacG5 Music volume makes an immediate network connection to the PowerMac G4, as well as sharing the screen of the PowerMac G4 the moment I ask it to, I have concluded that the hardware of the iMac G5 is just fine. The problem seems confined to the system software and/or associated networking files that are unique to the iMacG5 Music volume. I just don't know what those files could be, or where the problem lies, so I've issued this call for help.
Let me add one more little twist to this puzzle which baffles me even more. I use external LaCie Firewire drives as clone backups of my Macs. As part of my trouble-shooting process, I booted up from the cloned versions of the iMacG5 JMB volume and the iMacG5 Music volume. What I learned surprised me!
The iMacG5 JMB clone worked just fine in making a fast network connection to the MacBook Pro, as well as sharing the screen of the MacBook Pro. I expected that. What I did not expect was that the iMacG5 Music clone was also able to make a fast network to the MacBook Pro, as well as share its screen!
Yes, that's right. It's weird! Screen sharing works OK when I start-up from the clone of the iMacG5 Music volume, but it does not succeed when I boot up on the source itself! I was surprised to find that out, but I'm glad I did.
(Over the past few days since I executed the last clone, I did use Drive Genius to de-frag the source volume, and maybe that has contributed to the problem I am now encountering. But it's hard to say, since nothing else seems to be amiss.)
One solution, I suppose, would be to sync the clone back to the source. But, before I do that, I'm just wondering if anyone has a clue as to the nature of this problem on the source volume and what I might do to remedy it—short of re-installing the system software or restoring from the clone. Anyone have any insight to this problem?

CORRECTION #2:
Ignore the previous "CORRECTION" post.
Oops, excuse me, I wrote that sentence correctly the first time.
I was trying to point out that the ability of the iMac G5 computer to connect quickly and effectively to the PowerMac G4 when booted up into the iMacG5 Music volume was an indication (to me, anyway) that there is nothing wrong with the computer's hardware, nor its network connection ability, but that the problem lay somewhere in the files/settings used to connect to the MacBook Pro, which it cannot accomplish.
This is what happens when I get engrossed in one of these technical morasses and it ***** me into its vortex all through the night... time for bed.

IPhone 4S Outlook 2010 shared Calendar problem

Hello all,
There problem to see in Outlook 2010 shared calendar in iPhone 4S. In iPhone 4S there is seen owner calendar of added Exchange Server account, but I need to see other one person shared calendar which is impossible to see. I see in iPhone 4S two calendars as added, but when I open calendar I see entries only for one account.
Where is problem and how to solve it?
Thanks.
Best Regards,
Girts

I had the same problem where I could open a shared calendar in OWA but it would not work in Outlook 2010. When I clicked on the shared folder I got the error message 'outlook cannot open this folder'. The problem ended up being that the person
whose calendar was being shared was hidden on the exchange server ('hide from exchange address lists' had been selected). To resolve the issue we had to unhide the user, update the OAB on the server and then update the OAB on the desktop. We could then share
the calendar, accept the share and then hide the user again.
Sounds like I have the same issue too. Where do I go to do all the resolve part? Where do I unhide the user? I am guessing OAB means offline address book.
Thanks
Paul

Shared library problem

After messing around with fonts i ended up with this problem: i cant start gdm.
here's the message i get:
/usr/sbin/gdm-binary: error while loading shared libraries: libfreetype.so.6: cannot open shared object: no such file or directory
tried to install some fonts - same error.
tried to update font cache - same error.
I open up gdm-binary in Midnight Commander and its all like Greek/Chinese in there.
Any help would be good, thank you for your time
Last edited by nikchris (2008-04-11 15:45:49)

pacman -S freetype2

Shared Comment Problems!

Similar Messages

Maybe you are looking for