Screen sharing preferences problem
When I upgraded to Yosemite, it seems to have changed my sharing preferences. I want to restrict sharing to certain users. I have 2 sharing only users set up. They work as they always have for file sharing. But they no longer appear in my users list for screen sharing, and if I click the + to add a user, they don't appear in the list of users I can select. Apple's instructions for setting this up say:
If you selected “Only these users,” click Add at the bottom of the users list, then do one of the following:
Select a user from Users & Groups, which includes all the users of your Mac. - but it doesn't display my sharing only users
Select a user from Network Users or Network Groups, which includes everyone on your network. - this option doesn't even appear
Does screen sharing not work with sharing only users? Is there some other setting I need to change?
My dad has always used his full username, including domain, so there's nothing to change in terms of that.
According to AT&T's support website, his FastAccess DSL username/password should be unchanged and still work. That said, I believe I need to try changing the settings of his DSL modem to use bridge mode and then try the PPPoE configuration on the AEBSn again.
I think I remember my dad saying an AT&T service tech came out and tested his DSL line and may have done something to the modem which my dad claims he didn't. Reading about the specs of the DSL modem and the accounts of a few AT&T techs, the modem is supposed to be in bridge mode in order to work with a router that uses a PPPoE configuration for single NAT.
Thanks for your input!
Similar Messages
-
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. -
I am seeing graphical redraw problems when I try screen sharing with another Mac 10.8 computer, Mac Mini mid 2011. For example, when switching menus, the old ones remain. This always worked just fine in Lion. I tried turning adaptive and scaling off and on, but no difference.
Don't know whether I found the problem, but I did manage to get Screen Sharing working reasonably again.
Things had gotten so bad that even mouse moves and keystrokes were getting mangled and delayed, so I decided to try a VNC client (Chicken of the VNC) to see whether things were better. I had to set the host machine to accept VNC connections, so you could say I "touched" the screen sharing panel in System Preferences. I also shut down the Screen Sharing app on the client side so I could use the VNC. The VNC worked OK but would not display the entre screen, so I quit. Then I restarted the Screen Sharing client, and--hey presto--it worked! Response to mouse & keyboard were back, and video was good enough to watch a video.
So, I guess folks could try (1) jiggling something in the Screen Sharing prefs on the host machine, and (2) restarting the Screen Sharing client.
-- rick -
Screen Sharing viewing problem
I am using Skype Version 4.3.0.37 on a desktop using Ubuntu 12.04. Using Screen Sharing in full screen mode there are huge blocks of filler surrounding the screen sharing image making the screen sharing image much smaller and much harder to read. Is there a solution? Is anyone working on the problem? It seems as if linux problems are ignored.
Here's a couple things you can try:
Cntl-Shift-Eject will put the displays into sleep mode. Then space bar will bring them back out of sleep. See if that results in a screen on the Sony. If not, then try this one:
Hit the power button on the MB. This will pop a screen up (which you can't see because the Sony is black) but if you hit the S key, the MB will go into sleep mode. After it goes to sleep, hit space bar to awaken the MB and see if the screen comes back on the Sony. -
IChat Screen Sharing mouse problems
I just bought a new iMac 20" for my mom for xmas with the thought that the iChat screen sharing will help me to remotely configure her system.
I am finding that once I have initiated the screen share I am have erratic mouse behavior. When I am sharing her screen and moving the mouse the cursor will jump around the screen. this happens even worse if I am click-dragging a window around.
Is there any way to improve this performance? At work I use Windows remote desktop with no issues such as this, and I would expect the same performance from OSX.
ThanksMy first thought is that your mother is also trying to control the mouse.
I presume though you have exclude this.
iChat Screen Sharing does include an Audio component so the computer is doing an Audio chat at the same time effectively. This will have a impact on the processor usage particularly over the way iChat A/V chats use the processor. (they tend to dip in and out to spread the load and not hog the processor).
10:11 PM Friday; January 9, 2009 -
Screen Sharing Capital Problems
I have a PowerBook G4 (OS 10.5.8) that activates screen sharing on my MacBook Pro (OS 10.6.7) The Powerbook cannot successfully type capital letters on the MacBook Pro's screen. Any help would be appreciated.
My first thought is that your mother is also trying to control the mouse.
I presume though you have exclude this.
iChat Screen Sharing does include an Audio component so the computer is doing an Audio chat at the same time effectively. This will have a impact on the processor usage particularly over the way iChat A/V chats use the processor. (they tend to dip in and out to spread the load and not hog the processor).
10:11 PM Friday; January 9, 2009 -
Screen Sharing, recent problem seeing two monitors, anyone else?
I have a G5 running dual 20"monitors on the G5 dual DVI video card. I used to be able to screen share back to the G5 with my macbook pro and I would get to view the two screens. I could see them both or select on or the other.
Recently, I can only view the one monitor (the one set as the main monitor on the right) and I cannot see them both or switch between them.
Not sure if this is a bug in of the recent OS updates or what?
Thoughts
TomCORRECTION #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. -
Heya, when i go into system preference, and click on Sharing, it opens and there is nuthin inside it.
i have tried disk repair and repair disk permissions
can anyone tell me what to do?
mac pro 13 inch
os x 10.7.3When starting the system hold down the Command+r keys and it will boot you to the Recovery HD partition of your hard drive. From there you can reinstall OS X Lion. Have the computer connected by Ethernet cable to your router.
No installing over the top will not delete your files. But as always it is best to have a backup on an external drive. -
Problems connecting video and screen sharing
see the leopard iChat forum, I moved it to there. thanks, its called Another Video and screen sharing connection problem
Message was edited by: wishiwasmtbinHi,
Welcome to the Discussions
IS this Linksys doing UPnP ?
This is set in the Administration page of the set up pages.
Also in the Security Page disable the Anonymous Ping Blocking.
If you set UPnP then make sure any Port Forwarding, Port Triggering and DMZ is disabled.
These last three use NAT more strongly than UPnP and NAT can be an Issue.
The Appleu3test accounts are effectively on Public IP address so Lees/no NAT
1:52 PM Sunday; December 9, 2007 -
Remote Desktop & Screen Sharing not working??
Hello all,
I am trying to connect to a friends computer via the Finder's Screen Sharing, I enabled the screen sharing preferences under the System Preferences, put the password, etc and had him do the same and I am not able to connect to his system. I'm sure there is something else I have to do in order to get this to work. In the Windows world I had to use the VNC. But, I remeber reading in a Snow Leopard book that this is all that had to be done in order for this to work.
Best Regards,
freesparksI know I could never get this working between two macs of the same OS (10.5.8) over the internet with the appropriate Sharing settings set up....
Im guessing both Screen Sharing and Remote Access through iChat DO NOT work anywhere but in a LAN? -
I cant get screen sharing to work on my home network
I am trying to connect my macbook pro to screen sharing so i can access it at my school computers, which are all iMacs running 10.6.6. When i was at school, and connected to the wireless network at my school i could screen sharing through the finder>go>connect to server. Once screen sharing was enabled i just entered the vnc address and it connected flawlessly. When i got home, and i set my netgear router( wireless-n 150 model: wnr100v2) for port forwarding start port: 5900 end port:5900 server name vnc, and set the ip address to my computer, and when i tried to screen share from another macbook within my network through the finder>go>connect to server, i could not connect. Oddly when i connected my mobile me, i cold screen share over the network. I want to do a WAN screen sharing and i cannot figure out how do do it. I would appreciate any help because it is very important that i enable this feature.
I'm a little confused by your explanation (it's late), so I am going to say what I think I read:
You want to set up your home computer so you can access it via screen sharing from school.
The home computer needs sys prefs sharing screen sharing enabled, and sys prefs security firewall must allow it, too. You port forward port 5900 through your home router to that home computer, which may or may not require that you use a static "192.168.x.x" (or "10.x.x.x" -- whatever the router's LAN subnet is) LAN IP address on that computer -- some routers require that computers acting as servers have static IPAs -- some routers don't.
You need to find out what is the public (internet-facing) WAN IP address that your ISP has assigned to your router; it is not the 192.168.x.x (or 10.x.x.x) address given to your home computer by your home router. You can find that by going to http://checkip.dyndns.com on your home computer. Unless you pay extra for a static public IP address from your ISP, ISPs may (and do) change it periodically on you without warning. So vnc://123.45.67.89 may work one day but not the next.
Some routers have a built-in feature to work around this by allowing the router to advise dynamic DNS servers of any changes in the public-facing IP address of the router. Of course, you need to have established an account with a dynamic DNS provider so you have a host name (like lomberg.noip.com or lomberg.dyndns.com). These are generally free accounts unless you want a special name that doesn't have the dynamic DNS provider as part of your host name.
If your router does not have this capability, these dynamic DNS providers have a piece of software that you will need to install on your home computer (the "VNC server") that reports changes in your public-facing IP address to their DNS servers.
Once this is done, then from afar, you can ⌘k to vnc://lomberg.dyndns.com (or whatever you set up your host name to be with dyndns or equivalent outfit) and you don't need to worry about what your ISP has done to you with regards to your public-facing WAN IP address du jour.
Note that with some (most?) routers, when you are on your home network, you will not be able to vnc to the host name or numeric WAN IPA in this manner. I don't know why it doesn't work, it just doesn't. I've had modems both ways -- my current ISP rental modem doesn't while the previous one (which broke so I had to replace it with my current POS modem) did. So in such case, you have to vnc://192.168.x.x of the "vnc server" computer when you are on the same LAN.
You are aware that on the client (school) machine, screen sharing preferences can be set to encrypt all data on the connection, not just the username/password negotiation piece, right? I don't know whether that setting persists across sessions or only persists for the duration of the current session. I wouldn't want my client mouse/keyboard and "server" screen video to be transmitted in the clear; that's why I bring this up.
Does that answer your question? Or did I totally misunderstand what you were asking? -
HELP: Problem accessing host Mac MSL Mini using "Screen Sharing"
I have screen sharing enabled on my mother-in-law's Mac Mini so I can access it with Chicken of the VNC.
There are 2 user accounts, one Admin and the other regular. The problem is that when Chicken Of the VNC connects and I choose one of the accounts and log-in the connection terminates and I have to close Chicken of the VNC and re-connect.
Is there something in Sharing/screen sharing that needs to be set so the connection will not terminate when switching account .From Finder help on screen sharing...
-=-=-=-
If you can’t share computer screens
If you’re having problems sharing your screen with another computer, or sharing the screen of another computer, there are several things to check.
Here are things to try if you can’t share screens:
Make sure screen sharing is turned on and you have set up sharing permissions on the computer whose screen you want to share.
Sharing your screen with other computer users
If you’re trying to share the screen of another computer, open Sharing preferences on that computer and make sure you’re in the list of users who have been given permission to share that computer’s screen.
Make sure neither computer is in sleep mode. A computer can’t share its own screen or share the screen of another computer if it’s in sleep. Adjust the computer’s settings using Energy Saver preferences.
If you’re using Back to My Mac to share screens, make sure it’s turned on on both computers.
Sharing your computer’s screen using Back to My Mac
Make sure both computers are connected to the same network, or if you’re sharing screens using Back to my Mac, make sure they’re both connected to the Internet. -
No audio/video/screen-sharing problem in iChat 4.0
I've been using iChat for years (since its original release) and since upgrading to 10.5 I can no longer audio or video chat; and the new screen-sharing option doesn't work either.
I connect to the net through an AirPort wireless network, which is connected to an ADSL Nation X-Modem/Router. I have a 2Mbps connection. As far as I know all the required ports are open on the router. My friend has the same ISP as me (Force9) and has made sure he has the same ports open on his router too.
I've adjusted my iChat settings to port 443 with no SSL and a Bandwidth limit of 500 Kbps in iChat; and QuickTime settings to 1.5 Mbps in System Preferences. I've read other discussions on this forum suggesting these options.
However, nothing seems to work. I can't even get audio and video to work across Bonjour on my home network any more. I'd be grateful for any help anyone can offer.
Below is my error report:
Date/Time: 2007-12-27 23:38:05.737 +0000
OS Version: 10.5.1 (Build 9B18)
Report Version: 4
iChat Connection Log:
2007-12-27 23:37:16 +0000: AVChat started with ID 1971558074.
2007-12-27 23:37:16 +0000: [email protected]: State change from AVChatNoState to AVChatStateWaiting.
2007-12-27 23:37:16 +0000: 0x1c023ad0: State change from AVChatNoState to AVChatStateInvited.
2007-12-27 23:37:27 +0000: 0x1c023ad0: State change from AVChatStateInvited to AVChatStateConnecting.
2007-12-27 23:37:27 +0000: [email protected]: State change from AVChatStateWaiting to AVChatStateConnecting.
2007-12-27 23:38:03 +0000: 0x1c023ad0: State change from AVChatStateConnecting to AVChatStateEnded.
2007-12-27 23:38:03 +0000: 0x1c023ad0: Error -8 (Did not receive a response from 0x1c023ad0.)
2007-12-27 23:38:03 +0000: [email protected]: State change from AVChatStateConnecting to AVChatStateEnded.
2007-12-27 23:38:03 +0000: [email protected]: Error -8 (Did not receive a response from 0x1c023ad0.)
Video Conference Error Report:
56.475488 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
63.478531 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
239.541694 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
246.544032 @SIP/SIP.c:2719 type=4 (900A0015/0)
[SIPConnectIPPort failed]
Video Conference Support Report:
6.263009 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
[Connection Data for call id: 1 returns 1
10.836896 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
[Connection Data for call id: 2 returns 1
39.051949 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
[Connection Data for call id: 3 returns 1
43.450824 @VCChannel/VCChannel.m:252 type=2 (00000000/0)
[VCChannel prepareConnectionWithRemoteConnectionData - remote VCConnectionData: 1]
43.453466 @Video Conference/VCInitiateConference.m:1597 type=2 (00000000/0)
[Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
43.455651 @Video Conference/VCInitiateConference.m:1701 type=2 (00000000/0)
[Initiate Conference To User: u0 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
54.474920 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1c92401a6e250ccf
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=1537014430
Call-ID: 4860ab94-b4d4-11dc-92ee-be9358c74012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 399
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3253226420
54.975547 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1c92401a6e250ccf
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=1537014430
Call-ID: 4860ab94-b4d4-11dc-92ee-be9358c74012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 399
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3253226420
55.976046 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1c92401a6e250ccf
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=1537014430
Call-ID: 4860ab94-b4d4-11dc-92ee-be9358c74012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 399
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3253226420
61.478080 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:50431 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1cc0b6ce6e567e1e
Max-Forwards: 70
To: "u0" <sip:user@rip:50431>
From: "0" <sip:user@lip:16402>;tag=1593623839
Call-ID: 4c8d2436-b4d4-11dc-92ee-eb3fab0f4012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 399
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3253226420
61.978667 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:50431 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1cc0b6ce6e567e1e
Max-Forwards: 70
To: "u0" <sip:user@rip:50431>
From: "0" <sip:user@lip:16402>;tag=1593623839
Call-ID: 4c8d2436-b4d4-11dc-92ee-eb3fab0f4012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 399
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3253226420
62.979288 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:50431 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK1cc0b6ce6e567e1e
Max-Forwards: 70
To: "u0" <sip:user@rip:50431>
From: "0" <sip:user@lip:16402>;tag=1593623839
Call-ID: 4c8d2436-b4d4-11dc-92ee-eb3fab0f4012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 399
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3253226420
221.875355 @Video Conference/VCInitiateConference.m:1582 type=2 (00000000/0)
[Connection Data for call id: 5 returns 1
226.522875 @Video Conference/VCInitiateConference.m:1597 type=2 (00000000/0)
[Prepare Connection With Remote Data - remote VCConnectionData: 1, local VCConnectionData: 1
226.527478 @Video Conference/VCInitiateConference.m:1701 type=2 (00000000/0)
[Initiate Conference To User: u0 with Remote VCConnectionData: 1 with Local Connection Data: 1 conferenceSettings: 1]
237.541363 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK7c8b8e053141eae8
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=538595231
Call-ID: b57cadae-b4d4-11dc-92ee-d6e5d2954012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 734
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3830094153
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16402
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16402 VIDEO 16402
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:196956011
238.041987 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK7c8b8e053141eae8
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=538595231
Call-ID: b57cadae-b4d4-11dc-92ee-d6e5d2954012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 734
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3830094153
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16402
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16402 VIDEO 16402
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:196956011
239.042442 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:16402 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK7c8b8e053141eae8
Max-Forwards: 70
To: "u0" <sip:user@rip:16402>
From: "0" <sip:user@lip:16402>;tag=538595231
Call-ID: b57cadae-b4d4-11dc-92ee-d6e5d2954012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 734
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3830094153
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16402
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16402 VIDEO 16402
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:196956011
244.543484 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:50468 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK47f51d1236ccf090
Max-Forwards: 70
To: "u0" <sip:user@rip:50468>
From: "0" <sip:user@lip:16402>;tag=289044260
Call-ID: b9a91160-b4d4-11dc-92ee-a8a976dd4012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 734
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3830094153
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16402
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16402 VIDEO 16402
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:196956011
245.044025 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:50468 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK47f51d1236ccf090
Max-Forwards: 70
To: "u0" <sip:user@rip:50468>
From: "0" <sip:user@lip:16402>;tag=289044260
Call-ID: b9a91160-b4d4-11dc-92ee-a8a976dd4012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 734
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3830094153
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16402
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16402 VIDEO 16402
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:196956011
246.044704 @SIP/Transport.c:2353 type=1 (00000000/0)
[INVITE sip:user@rip:50468 SIP/2.0
Via: SIP/2.0/UDP lip:16402;branch=z9hG4bK47f51d1236ccf090
Max-Forwards: 70
To: "u0" <sip:user@rip:50468>
From: "0" <sip:user@lip:16402>;tag=289044260
Call-ID: b9a91160-b4d4-11dc-92ee-a8a976dd4012@lip
CSeq: 1 INVITE
Contact: <sip:user@lip:16402>;isfocus
User-Agent: Viceroy 1.3
Content-Type: application/sdp
Content-Length: 734
v=0
o=howardberry 0 0 IN IP4 lip
s=0
c=IN IP4 lip
b=AS:2147483647
t=0 0
a=hwi:17412:2:2330
a=iChatEncryption:NO
a=bandwidthDetection:YES
m=audio 16402 RTP/AVP 110 121 12 3 0
a=rtcp:16402
a=rtpmap:121 speex/16000
a=rtpmap:122 speex/8000
a=rtpmap:113 X-AAC_LD/44100
a=rtpmap:110 X-AAC_LD/22050
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpID:3830094153
m=video 16402 RTP/AVP 123 126 34
a=rtcp:16402
a=rtpmap:123 H264/90000
a=rtpmap:126 X-H264/90000
a=rtpmap:34 H263/90000
a=fmtp:34 imagesize 1 rules 30:352:288
a=framerate:30
a=RTCP:AUDIO 16402 VIDEO 16402
a=fmtp:126 imagesize 0 rules 20:640:480:640:480:20
a=fmtp:123 imagesize 0 rules 20:640:480:640:480:20
a=rtpID:196956011
Video Conference User Report:
0.000000 @:0 type=5 (00000000/16402)
[Local SIP port]
0.000017 @:0 type=5 (00000000/16402)
[Local SIP port]
0.000032 @:0 type=5 (00000000/16402)
[Local SIP port]
0.000064 @:0 type=5 (00000000/16402)
[Local SIP port]
0.000080 @:0 type=5 (00000000/16402)
[Local SIP port]
252.557643 @Video Conference/VideoConferenceMultiController.m:1476 type=5 (00000000/0)
[IP And Port Data With Caller IP And Port Data: Obtained 400 bytes of local IP and port data (10 entries). Remote data was 0 bytes (0 entries).
[]Hi,
Technically it should not matter if you are using AIM or @Mac names.
However you have solved that bit.
The Screen Sharing part uses three ports.
Two randomly picked ports for the Screen Sharing and the same A/V port for the Audio component. As the Airport is normally set to Share An IP and does NAT on the fly so to speak this also should not be a problem
The ADSLNAtion site is a bit behind on it's Airport page
http://www.adslnation.com/support/knowledgebase/ht007.php as it shows the older Firmware pics.
I found the new page
http://www.adslnation.com/knowledgebase/xmodem+airport-11n.php
This says that the DNS server info in the Airport needs to be removed.
It is not clear if this is a variation for the X-Modem M3
Very few of the posts here http://forum.adslnation.com/viewforum.php?f=3 are after Leopard came out and nothing appears to be about iChat.
So it would somewhat depend if the Airport is Sharing and IP or is Static to the computer and Port Mapping used.
1:56 PM Saturday; December 29, 2007 -
Screen sharing Lion- Lion problem
I am trying to set up screen sharing in my local network.
I am using a MacBook with latest Lion as server to which I am trying to connect.
I am connecting with a Powerbook 12" 10.5.8 without problems and controlling the MacBook via Screen Sharing.
I am unable to connect to the MacBook using a MacBook Pro with same Lion installed.
Before that I used the same setup to try out RealVNC. Again, the Powerbook connected to the MacBook without problems, but the MacBook Pro is unable to connect.
Any suggestions?
Thanks.This thought just occurred to me. Do you have the Macbook Pro Firewall enabled? System Preferences -> Security & Privacy -> Firewall. Is it enabled? If it is, try disabling it.
Time to ask a question about your network setup. Wild Goose Chase questions.
You mentioned an Airport Extreme. Is that the ONLY router in the house? The reason I ask, is that if you have multiple WiFi routers (for example because your house is so large, you need more than one WiFi router to cover the entire house, or your house has has 4 floors you need to cover and the structure interferes betwen the basement to the converted attic), you could have multiple subnets which could affect the ability to connect to devices on the other subnet. If you do have multiple subnets, there are ways to address this.
I would like you to download and run "Bonjour Browser"
<http://www.macupdate.com/app/mac/13388/bonjour-browser>
Run Bonjour Browser on the Macbook Pro (and any other Macs you like). I want you to look for "Remote Frame Buffer" entries (VNC Servers - aka Screen Sharing servers). Click the triangle to show all the systems offering VNC server.
Assuming you see your Macbook listed, click on its triangle to show the IP address and port number. It should be something like 10.0.1.nn:5900. Hopefully you see the same IP address as you think your Macbook has assigned to it (which you can see via Macbook -> System Preferences -> Network -> Advanced -> TCP/IP.
If you are not seeing your Macbook via Bonjour Browser from your Macbook Pro, then there is something affecting your ablity to see the Macbook. -
I cannot connect to the server – screen sharing, Server Preferences,...
hello
I have a problem with xserver. Everything seems to be working ok, however, one day system started to break down.
I cannot connect to the server through *screen sharing* neither through internet, nor through local net. Even after restart login wont shows up.
I cannot also connet to the *Server Preferences* (Unable to authenticate to the Open Directory master.)
Sometimes I cannot also connect to the *Server Admin* (but after restart it works, however, Server Preferences are unavailable).
SSH works ok.
Nor repair permission, neither verify disk, or update for OS X server 10.6.4 worked.
system log periodicaly enters this message:
Jul 14 23:24:35 xserve WindowServer[5091]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Jul 14 23:24:35 xserve com.apple.WindowServer[5091]: Wed Jul 14 23:24:35 xserve.sk WindowServer[5091] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Jul 14 23:24:36 xserve com.apple.launchd[1] (com.apple.RemoteDesktop.agent[5096]): posix_spawn("/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Content s/MacOS/ARDAgent", ...): No such file or directory
Jul 14 23:24:36 xserve com.apple.launchd[1] (com.apple.RemoteDesktop.agent[5096]): Exited with exit code: 1
Jul 14 23:24:36 xserve com.apple.launchd[1] (com.apple.RemoteDesktop.agent): Throttling respawn: Will start in 10 seconds
Jul 14 23:24:36 xserve loginwindow[5085]: Login Window Started Security Agent
Jul 14 23:24:36 xserve loginwindow[5085]: Login Window - Returned from Security Agent
Jul 14 23:24:36 xserve loginwindow[5085]: AuthorizationRef returned errAuthorizationDenied. Exiting.
Jul 14 23:24:36 xserve com.apple.loginwindow[5085]: AuthorizationRef returned errAuthorizationDenied. Exiting.
Jul 14 23:24:36 xserve com.apple.launchd[1] (com.apple.loginwindow): Throttling respawn: Will start in 3 seconds
Jul 14 23:24:36 xserve com.apple.ReportCrash.Root[4982]: 2010-07-14 23:24:36.505 ReportCrash[4982:350b] Saved crash report for ManagedClient[5099] version ??? (???) to /Library/Logs/DiagnosticReports/ManagedClient2010-07-14-232436localhost.crash
can you advice me?
thanksHi Shannon McLain,
Kindly let us know if there is any specific error message that you are getting while installing it.
Here is what you can try:
Creative Cloud Help | Download, install, update, or uninstall apps
https://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
https://helpx.adobe.com/creative-cloud/kb/error-downloading-cc-apps.html
Kindly share the results once done.
Thanks,
Atul Saini
Maybe you are looking for
-
Windows 7, I-920 processor, 12GB ddr3 memory, ATI 5770 video, multiple, 1 TB, 7200 rpm drives for images and backups. CS6 13.0.1 X64 I've had this periodically ever since going to CS6, but it's rare and seemingly random. I'm editing, I open a Nikon
-
I installed the release version of Windows 8 Pro, available through Microsoft DreamSpark Premium, on my late-2011 15" MacBook Pro through BootCamp. I had problems with the monitor and network communications, but after reinstalling the drivers from th
-
Can't Replace (Relink) AIFF files with anything.
Hi there, using FCPx 10.0.9 on 64 bit iMac which runs like a top. I used some AIFF's in a session before experiencing and confirming here that even when using optimized media, they upset our finicky FCPX. I converted the files to WAVs used relink
-
Backup across multiple DVD's (Deja Vu and Roxio Toast)
Can anyone suggest software in order to do this? I need to get some information off my internal and external drives to free up some room. I'm running Deja Vu and they suggest "backing up to Roxio Toast" to do this but I'm not very familiar with this
-
Raw Image Plug-Ins for Elements 12
I have Photoshop Elements 12 running on Windows 7 Home Premium, which I assume is 32 bit. I need to be able to edit RAW (NEFF format) image files from a Nikon D4s camera. I do not see a 32 bit version of Camera Raw 8.5, 8.4 or 8.3 that can handle thi