Remote Desktop Connection ok on work wireless but not from home

I've succesfully logged into the Win 2003 SBS (Terminal Services) from within the wireless connection at work using Mircrosoft's "Remote Desktop Connection". However when I try to do this from home I get the following error message "Either remote connections are not enabled, the computer is too busy to accept new connections, or network problems are preventing your connection. Try connecting again later or contact your administrator."
I've got the firewall on the mac on.
Now what I can't work out is why it works when at work and not from home. I have been searching for ages and can't work this out - annoying as I am sure it is very simple!
One thing I can think of is that the first time others connect via PCs they have to download the connection manager from the company web site which installs a security certificate. However this is an .exe file so cannae work on the Mac.
Do all I need to do is ask the IT administrator to email me the certificate and drop it into the keychain?
Thanks in advance.

"Now what I can't work out is why it works when at work and not from home."
Probably because, if your work is smart, they have a firewall in place, blocking external access to the ports needed for use with RDC.

Similar Messages

  • "remote desktop connection has stopped working" When printing from remote desktop connection

    I have been having a issue when using a windows 7 machine. I have Remote Desktop to a session on Windows2008 R2, I am using the local printer resources to redirect the printing. However everytime i try to print it crashes the remote desktop application.
    Gives me "remote desktop connection has stopped working." I have 4 other computers connected and printing with no issues what so ever. This only happens when i print. It does print by the way just the application crashes.
    -I have also updated the printer drivers to newest possible thru the manufactorer website. The printer is a Brother MFC-8890DW. Windows 2008 R2 is up to date for the RDS server. 3 other machines are able to Remote in and print. The user is able to print using
    diffrent machines just not the Windows 7 machine.

    Hi,
    Happy to hear that you resolved your issue. For another issue which you are facing here trying to provide some suggestion.
    As you have commented that you are facing issue with second screen resolution on wide screen. The setting which I am suggesting can only applies when you are using multi-monitor Remote Desktop connections.  If you are making Connections using a single
    monitor do not use this setting. 
    So for this you can try to apply “Limit maximum display resolution” setting in group policy, where you can mention the width & height for the screen to display. The setting can be applied on below mentioned
    path.
    Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
    Meanwhile sharing article with you for more information.
    Remote Session Environment
    http://technet.microsoft.com/en-us/library/ee791847(v=ws.10).aspx
    Hope it helps!
    Thanks.

  • Any suggestions on how to get wifi to work?  I have a multitech router and can connect with a computer wirelessly but not the ipad.

    Any suggestions on how to get wifi to work?  I have a multitech router and can connect with a computer wirelessly but not the ipad.

    iOS: Troubleshooting Wi-Fi networks and connections
    http://support.apple.com/kb/TS1398

  • Why will my I phone 5 connect to bt open zone but not bt home hub?

    Why will my I phone 5 connect to bt open zone but not bt home hub?

    ConnorATY wrote:
    Why will my I phone 5 connect to bt open zone but not bt home hub?
    It means your iPhone Wi-Fi is working.
    You might need to download/update your router firmware and do a router reboot.

  • Remote Desktop Connection no longer working

    Hi, I really hope someone can please help me.   I just switched from Comcast to FIOS and I can no longer remote desktop to work - so I'm not getting paid until I can get it fixed.
    The way that I was doing it before was to connect with a regular Microsoft VPN (I have Windows XP Professional), and then I would use Remote Desktop Connection to log into the work PC.  Since I switched to FIOS it no longer works on either my laptop with wireless or my desktop which is connected to the router. 
    The VPN seems to be connecting OK; it says it is and it is sending/receiving a small bit of data.  But when I open the the RDC and try to connect using the PC name it says that the computer cannot be found.  I tried to connect to the IP address of it (after connecting through the VPN) and then it says it's found but cannot connect.
    There is another location to which I log in using a Cisco VPN and then Remote Desktop - that still works just fine.  Nothing at work has changed; everyone else can log in with no problems, including everyone else with FIOS.
    I honestly have no ideas at all; this is not my area of expertise to say the least.  If anyone could help I would REALLY appreciate it!
    Thanks much!
    Solved!
    Go to Solution.

    It is a new Actiontec router. 
    I finally got it resolved; one of my coworkers suggested checking to make sure that the IP addresses were not in conflict, and they were.  So, if anyone else has this problem, what happened was that the new router was assigning IP addresses to my PC's at home in the 192.168.1.x range, which was also the server at work's IP address.
    So the really dumbed down version (for people like me!) is to open a command prompt on your desktop, run ipconfig /all, and then it will tell you your internal IP address.  (I was getting thrown off because the ROUTER'S IP address, which is the one you can look up online, was different).  If the PC's IP is almost the same as the server IP address, then you have to change the IP range on your router to something like 192.168.114.x.  There's directions if you google the router specs; I had to change it in three places on the router software; the router IP, the begin range and the end range.
    Thank you, jumpin68ny, for starting to help me.  Hopefully now this may help someone else!

  • Remote Desktop Connection no longer works.

    After verifying that all Remote Desktop Connection settings and firewall settings match the requirements, I cannot connect to the host computer running Windows 8.1 Pro with Media Center from a client computer running Windows 7 Home Premium SP1 over my
    home (private) network. I was previously able to connect these same two computers when the host computer was running Windows XP Pro, but now that I have upgraded its operating system to Win 8.1 Pro the connection no longer works. The Windows Troubleshooter
    cannot find the problem. What is wrong?

    If you turn off a firewall in a router it is still using NAT which will also act like a firewall. In my experience its better to let your router be the firewall.
    On most routers that have an SPI firewall you have to setup 2 rules to allow remote connections. One would be the firewall rule and other would be the port forwarding(NAT) rule.
    Are you forwarding the correct ports to your mac from the router? Does your Mac have a fixed IP address?

  • Remote Desktop Connection has stopped working

    Using Build 10041. Occurs on 2 separate systems I have when trying to use Remote Desktop Connection through a 2012 R2 RDS Gateway. I am able to connect to the remote systems and access the environment for a short period prior to MSTSC.EXE
    crashing. "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
    Eventlog has the following:
    Log Name:      Application
    Source:        Application Error
    Date:          3/25/2015 2:50:21 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Faulting application name: mstsc.exe, version: 10.0.10041.0, time stamp: 0x5503b1a7
    Faulting module name: mstscax.dll, version: 10.0.10041.0, time stamp: 0x5503b315
    Exception code: 0xc0000005
    Fault offset: 0x000000000046d78c
    Faulting process id: 0x2164
    Faulting application start time: 0x01d06734abf028a0
    Faulting application path: C:\WINDOWS\system32\mstsc.exe
    Faulting module path: C:\WINDOWS\system32\mstscax.dll
    Report Id: 2b084e37-d328-11e4-ab40-7c7a9191e005
    Faulting package full name:
    Faulting package-relative application ID:
    JW

    Tried this with no luck.  I have the same issue as the OP.  It was failing on 10041 and is still failing with an AV on 10049.  See below event log entry after registering mstscax.dll and rebooting.  Still failing.
    Log Name:      Application
    Source:        Application Error
    Date:          4/11/2015 12:18:21
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Chuck1
    Description:
    Faulting application name: mstsc.exe, version: 10.0.10049.0, time stamp: 0x55137bff
    Faulting module name: mstscax.dll, version: 10.0.10049.0, time stamp: 0x55137d3f
    Exception code: 0xc0000005
    Fault offset: 0x000000000046d74c
    Faulting process id: 0x1870
    Faulting application start time: 0x01d0748c29e55e06
    Faulting application path: C:\WINDOWS\system32\mstsc.exe
    Faulting module path: C:\WINDOWS\system32\mstscax.dll
    Report Id: 83921b7c-e07f-11e4-960f-40f02f7ad3a4
    Faulting package full name:
    Faulting package-relative application ID:
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-04-11T19:18:21.000000000Z" />
        <EventRecordID>73626</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Chuck1</Computer>
        <Security />
      </System>
      <EventData>
        <Data>mstsc.exe</Data>
        <Data>10.0.10049.0</Data>
        <Data>55137bff</Data>
        <Data>mstscax.dll</Data>
        <Data>10.0.10049.0</Data>
        <Data>55137d3f</Data>
        <Data>c0000005</Data>
        <Data>000000000046d74c</Data>
        <Data>1870</Data>
        <Data>01d0748c29e55e06</Data>
        <Data>C:\WINDOWS\system32\mstsc.exe</Data>
        <Data>C:\WINDOWS\system32\mstscax.dll</Data>
        <Data>83921b7c-e07f-11e4-960f-40f02f7ad3a4</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

  • Remote Desktop Connection won't work from Leopard to Windows XP

    Hi, folks:
    I'm unable to connect to my work XP computer via my home iMac (Leopard 10.5.7) using Microsoft's Remote Desktop Connection for Mac. The XP settings are correct, I'm connected on my work network VPN, and I don't believe I have any router firewalls causing the problem --- the reason I know this is because I also have an MacBook running Tiger (10.4.11) and it has been connecting to my work PC without any problems. So, this must be a Leopard firewall setting?
    As far as that goes, on my iMac I've got Screen Sharing, Remote Login and Internet Sharing turned on. Again, work network VPN is on.
    I'm getting this error from Remote Desktop Connection:
    "The Mac cannot connect to the Windows-based computer
    This problem can occur if:
    - The Windows-based computer is not set up to accept remote connections
    - The Windows-based computer is not turned on
    - The Mac, or the Windows-based computer is experiencing network problems
    Try connecting to the Windows-based computer again, or contact your administrator"
    Anyone know of a fix? I'd greatly appreciate it!
    Thanks.

    What Firewall setting do you have on your Mac? Try setting it to allow all connections. At least as an experiment.
    Do you have any Proxies set in System Preferences -> Network -> Advanced -> Proxies? If yes, then is it possible that "Bypass" list is not covering the XP system.

  • "Remote Desktop connection has stopped working." problem in Windows 8

    here is the event log.  Only happens on a few of our servers
    Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
    Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505ab405
    Exception code: 0xc0000005
    Fault offset: 0x0000000000002acd
    Faulting process id: 0x13c4
    Faulting application start time: 0x01cdbd0d09091fcd
    Faulting application path: C:\Windows\System32\mstsc.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 4d923a55-2900-11e2-be73-cc52af4d02a3
    Faulting package full name:

    Your Ricoh printer drivers cause the crashes:
    * Exception Analysis *
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for RC5BE130.DLL -
    FAULTING_IP:
    ntdll!memcpy+21a
    000007f8`1fed2acd f30f6f4402f0 movdqu xmm0,xmmword ptr [rdx+rax-10h]
    EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 000007f81fed2acd (ntdll!memcpy+0x000000000000021a)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 00000000bd9e440c
    Attempt to read from address 00000000bd9e440c
    DEFAULT_BUCKET_ID: INVALID_POINTER_READ
    PROCESS_NAME: mstsc.exe
    ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 00000000bd9e440c
    READ_ADDRESS: 00000000bd9e440c
    FOLLOWUP_IP:
    RC5BE130!PrinterProperties+2a1ea
    00000000`71c4c46a 8b442430 mov eax,dword ptr [rsp+30h]
    DETOURED_IMAGE: 1
    NTGLOBALFLAG: 0
    APPLICATION_VERIFIER_FLAGS: 0
    APP: mstsc.exe
    FAULTING_THREAD: 0000000000001198
    PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ
    BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ
    LAST_CONTROL_TRANSFER: from 0000000071c4c46a to 000007f81fed2acd
    STACK_TEXT:
    000000bb`ba9cf248 00000000`71c4c46a : 000000bb`00000040 000000bb`ba9cf618 000000bb`bd7a1458 00000000`00000000 : ntdll!memcpy+0x21a
    000000bb`ba9cf250 00000000`71c4bf68 : 000000bb`b45ccc40 000000bb`bae6e7c8 000000bb`bd7a1458 00000000`00000000 : RC5BE130!PrinterProperties+0x2a1ea
    000000bb`ba9cf2a0 00000000`71c4b2f9 : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`71c10000 : RC5BE130!PrinterProperties+0x29ce8
    000000bb`ba9cf380 00000000`71c2a08a : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`02000000 : RC5BE130!PrinterProperties+0x29079
    000000bb`ba9cf3d0 00000000`71c283de : 000000bb`ba9cf618 000000bb`badfb050 000000bb`00000000 00650074`00730079 : RC5BE130!PrinterProperties+0x7e0a
    000000bb`ba9cf440 00000000`71c2209d : 00000000`00000000 000000bb`ba9cf618 00007989`001a0019 000007f8`169fafa0 : RC5BE130!PrinterProperties+0x615e
    000000bb`ba9cf550 000007f8`169e5ea0 : 00000000`00000000 000000bb`ba9cf618 000000bb`bd7a1458 000000bb`bd7a1458 : RC5BE130!DrvDocumentPropertySheets+0x1d
    000000bb`ba9cf580 000007f8`169e6b9f : 000000bb`00000000 000000bb`ba9cf670 00000000`00000000 00000000`00000004 : winspool!DocumentPropertySheets+0xb0
    000000bb`ba9cf5f0 000007f8`169e6aa5 : 00000000`00000002 000007f8`ffffffff 00000000`00000000 00000000`00000000 : winspool!DocumentPropertiesWNative+0xcf
    000000bb`ba9cf680 000007ff`f4f3dc32 : 00000000`00000000 000000bb`b93f3990 00000000`000004d4 000000bb`ba9cf790 : winspool!DocumentPropertiesW+0x7d
    000000bb`ba9cf6e0 000007ff`f4f9a09b : 00000000`00000000 000000bb`ba9cf7b0 00000000`00000000 000000bb`b93c7530 : mstscax!CTSClientPrintDriver::DocumentPropertiesW+0x37e
    000000bb`ba9cf730 000007ff`f4f994d4 : 000000bb`b93c7530 000007f8`00000000 00000000`00000000 000000bb`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Invoke_DocumentPropertiesW+0x12b
    000000bb`ba9cf7e0 000007ff`f4f8ff0c : 000000bb`b93c7530 000000bb`b93f29e0 000000bb`b94060d0 00000000`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Dispatch_Invoke+0x68
    000000bb`ba9cf840 000007ff`f4f95a84 : 000000bb`b93c7530 00000000`00000000 000000bb`b93c7530 000000bb`b93cccc0 : mstscax!CStub<IMMClientNotifications>::Invoke+0x64
    000000bb`ba9cf8b0 000007ff`f4f94310 : 000000bb`b93cccc0 000000bb`b93c7530 000000bb`ba9cf930 000000bb`b693b3c0 : mstscax!CRIMStreamStub::OnDataReceived+0x98
    000000bb`ba9cf8e0 000007ff`f4f18c5a : 000000bb`b93cccc0 000000bb`b93f4cd8 000000bb`b93f4b10 000000bb`b93f4cd8 : mstscax!CRIMObjManager::OnDataReceived+0x150
    000000bb`ba9cf960 000007ff`f4f20132 : 000000bb`b93c6908 00000000`00000000 000000bb`b93c6908 00000000`00000e28 : mstscax!CDynVCChannel::HandleAsyncCall+0x12e
    000000bb`ba9cf9b0 000007ff`f4ed94e7 : 000000bb`b93f36a0 000000bb`b93c68c0 00000000`00000000 000000bb`b93f40d0 : mstscax!CDynVCThreadPoolThread::ThreadPoolEntry+0x102
    000000bb`ba9cfa00 000007ff`f4c5aba9 : 000000bb`b7ddeb58 00000000`00000000 000007ff`f4b50000 00000000`00000000 : mstscax!CTSThread::TSStaticThreadEntry+0x33b
    000000bb`ba9cfa90 000007f8`1e41167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!PAL_System_Win32_ThreadProcWrapper+0x25
    000000bb`ba9cfac0 000007f8`1fef3501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
    000000bb`ba9cfaf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    SYMBOL_STACK_INDEX: 1
    SYMBOL_NAME: rc5be130!PrinterProperties+2a1ea
    FOLLOWUP_NAME: wintriag
    MODULE_NAME: RC5BE130
    IMAGE_NAME: RC5BE130.DLL
    DEBUG_FLR_IMAGE_TIMESTAMP: 4bd67428
    STACK_COMMAND: ~18s; .ecxr ; kb
    FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_RC5BE130.DLL!PrinterProperties
    BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_DETOURED_rc5be130!PrinterProperties+2a1ea
    WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/ntdll_dll/6_2_9200_16420/505ab405/c0000005/00002acd.htm?Retriage=1
    Followup: wintriag
    0:018> lmvm RC5BE130
    start end module name
    00000000`71b00000 00000000`71cdd000 RC5BE130 (export symbols) RC5BE130.DLL
    Loaded symbol image file: RC5BE130.DLL
    Image path: C:\Windows\System32\spool\drivers\x64\3\RC5BE130.DLL
    Image name: RC5BE130.DLL
    Timestamp: Tue Apr 27 07:20:40 2010 (4BD67428)
    CheckSum: 001E2D52
    ImageSize: 001DD000
    File version: 0.3.0.0
    Product version: 1.0.0.0
    File flags: 1 (Mask 3F) Debug
    File OS: 40004 NT Win32
    File type: 2.1 Dll
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: RICOH CO., LTD.
    ProductName: RICOH RPCS Printer Driver
    InternalName: RC5BE130.DLL
    OriginalFilename: RC5BE130.DLL
    ProductVersion: 1.0.0
    FileVersion: 7.6.9
    FileDescription: RICOH RPCS Printer Driver
    LegalCopyright: Copyright(C) 1999-2010 RICOH CO., LTD.
    so check for a printer driver update and what you can also do is to avoid mapping your printer to the Remote Desktop. Maybe this also fixes the issue.
    "A programmer is just a tool which converts caffeine into code"

  • Remote Desktop Connection - cannot proceed because authentication is not enabled

    Hello,
    I try to connect via RDP from a Windows Server 2008 R2 to another 2008 R2 Server.
    I always get the error message.
    The connection cannot proceed because authentication is not enabled and the remote computer requires than authentication be enabled to connect.
    On the target machine the Remote Settings are set to:
    Allow connections from computers running any version of Remote Desktop.
    Firewall is disabled on both servers.
    Therefor I do not understand why I get an error message, that authentication is required.
    The target box is a nearly fresh syspreped machine with all current Hotfixes installed.
    I already found a lot of people having that problem by using XP (old RDP client), but no one seems to have this problem when connecting from 2008 R2 to 2008 R2.
    Thank you very much in advance for every hint.
    BR
    Matthias

    Hi Matthias,
    First I would like to confirm if you have deployed RDS (Remote Desktop Services) and you got the error, if so, please check this option
    TS Configuration, >> RDP-Tcp Properties >> change the Security Layer to "Negotiate"
    Then Recycle the TS Gateway service.
    Refer to:
    Unable to connect to Server using the Remote Web Workplace (RWW) Small Business Server 2008
    If this issue has nothing to do with RDS, and I suppose you used the cmd "mstsc" to remote access. This issue may also occur because of the version of mstsc, please make sure it has been upgraded to the new version.
    In addition, Did you have another newer server available like Server 2012? So we can test and try to use Server 2012 to remote access Server 2008 R2, and check if the issue persists.
    If there is anything else regarding this issue, please feel free to post back.
    If you have any feedback on our support, please click here.
    Best Regards,
    Anna Wang
    TechNet Community Support

  • Error 500 from Microsoft Remote Desktop for Mac and for iOS but not for Windows

    I am running Windows Server Standard 2012 as a basic File server and Remote Access Server.  I am able to log into to Server remotely using Windows Remote Desktop Client on Windows 7 and 8 machines without problems
    When I try to log in using outside the local network using MRD version 8.0.24308 using OS X 10.9.1 or using iOS 7.0.4, I get the following error:
    " The gateway failed to connect with the message: 500 Internal Server Error"
    I can also log in remotely WITHIN the local network on a Mac or iOS device, it works without getting an error
    Any Ideas?

    My IT person has tried all these and I still get a 500 error when I log in from Microsoft Remote Desktop 8.5.  
    Here is part of the MRD log dump (not clear where to send the log since MRD doesn't provide an address when you dump the log into email):
    [2014-Mar-27 19:48:56] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Mar-27 19:48:56] RDP (0): lo0 af=18  addr= netmask=
    [2014-Mar-27 19:48:56] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Mar-27 19:48:56] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
    [2014-Mar-27 19:48:56] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-27 19:48:56] RDP (0): gif0 af=18  addr= netmask=
    [2014-Mar-27 19:48:56] RDP (0): stf0 af=18  addr= netmask=
    [2014-Mar-27 19:48:56] RDP (0): en0 af=18  addr= netmask=
    [2014-Mar-27 19:48:56] RDP (0): en1 af=18  addr= netmask=
    [2014-Mar-27 19:48:56] RDP (0): en1 af=30 (AF_INET6)  addr=fe80::226:bbff:fe00:c3d7%en1
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-27 19:48:56] RDP (0): en1 af=2 (AF_INET)  addr=192.168.0.89 netmask=255.255.255.0
    [2014-Mar-27 19:48:56] RDP (0): fw0 af=18  addr= netmask=
    [2014-Mar-27 19:48:56] RDP (0): p2p0 af=18  addr= netmask=
    [2014-Mar-27 19:48:56] RDP (0): utun0 af=18  addr= netmask=
    [2014-Mar-27 19:48:56] RDP (0): utun0 af=30 (AF_INET6)  addr=fe80::e1eb:119:5ad9:da9%utun0
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-27 19:48:56] RDP (0): utun0 af=30 (AF_INET6)  addr=fdce:4b1d:30c:78f8:e1eb:119:5ad9:da9
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-27 19:48:56] RDP (0): --- END INTERFACE LIST ---
    [2014-Mar-27 19:48:56] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Mar-27 19:48:56] RDP (0): client version: 8.0.24428
    [2014-Mar-27 19:48:56] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Mar-27 19:48:56] RDP (0): Resolved '10.1.10.11' to '10.1.10.11' using NameResolveMethod_DNS(1)
    [2014-Mar-27 19:49:04] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Mar-27 19:49:04] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Mar-27 19:49:04] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Mar-27 19:49:04] RDP (0): lo0 af=18  addr= netmask=
    [2014-Mar-27 19:49:04] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Mar-27 19:49:04] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
    [2014-Mar-27 19:49:04] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-27 19:49:04] RDP (0): gif0 af=18  addr= netmask=
    [2014-Mar-27 19:49:04] RDP (0): stf0 af=18  addr= netmask=
    [2014-Mar-27 19:49:04] RDP (0): en0 af=18  addr= netmask=
    [2014-Mar-27 19:49:04] RDP (0): en1 af=18  addr= netmask=
    [2014-Mar-27 19:49:04] RDP (0): en1 af=30 (AF_INET6)  addr=fe80::226:bbff:fe00:c3d7%en1
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-27 19:49:04] RDP (0): en1 af=2 (AF_INET)  addr=192.168.0.89 netmask=255.255.255.0
    [2014-Mar-27 19:49:04] RDP (0): fw0 af=18  addr= netmask=
    [2014-Mar-27 19:49:04] RDP (0): p2p0 af=18  addr= netmask=
    [2014-Mar-27 19:49:04] RDP (0): utun0 af=18  addr= netmask=
    [2014-Mar-27 19:49:04] RDP (0): utun0 af=30 (AF_INET6)  addr=fe80::e1eb:119:5ad9:da9%utun0
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-27 19:49:04] RDP (0): utun0 af=30 (AF_INET6)  addr=fdce:4b1d:30c:78f8:e1eb:119:5ad9:da9
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-27 19:49:04] RDP (0): --- END INTERFACE LIST ---
    [2014-Mar-27 19:49:04] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Mar-27 19:49:04] RDP (0): client version: 8.0.24428
    [2014-Mar-27 19:49:05] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Mar-27 19:49:05] RDP (0): Resolved 'javpeds.com' to '70.88.173.126' using NameResolveMethod_DNS(1)
    [2014-Mar-27 19:49:05] RDP (0): Resolved 'javpeds.com' to '70.88.173.126' using NameResolveMethod_DNS(1)
    [2014-Mar-27 19:49:07] RDP (0): Exception caught: Exception in file '../../librdp/private/httpendpoint.cpp' at line 209
        User Message : The gateway failed to connect with the message:
    500 Internal Server Error
    [2014-Mar-27 19:49:07] RDP (0): Exception caught: Exception in file '../../librdp/private/httpendpoint.cpp' at line 209
        User Message : The gateway failed to connect with the message:
    500 Internal Server Error
    [2014-Mar-27 19:49:07] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
    [2014-Mar-27 19:49:07] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Mar-27 19:49:07] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Mar-27 19:49:15] RDP (0): *** Application terminated ***
    [2014-Mar-29 12:03:43] RDP (0): Final rdp configuration used: gatewayhostname:s:javpeds.com
    screen mode id:i:2
    use multimon:i:0
    session bpp:i:24
    full address:s:10.1.10.11
    audiomode:i:2
    username:s:javpeds\ptraquair
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:1
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com"font-family:'SF Cartoonist Hand';font-size:18px;line-height:normal;" />bookmarktype:i:3
    use redirection server name:i:0
    [2014-Mar-29 12:03:43] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Mar-29 12:03:43] RDP (0): lo0 af=18  addr= netmask=
    [2014-Mar-29 12:03:43] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Mar-29 12:03:43] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
    [2014-Mar-29 12:03:43] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:03:43] RDP (0): gif0 af=18  addr= netmask=
    [2014-Mar-29 12:03:43] RDP (0): stf0 af=18  addr= netmask=
    [2014-Mar-29 12:03:43] RDP (0): en0 af=18  addr= netmask=
    [2014-Mar-29 12:03:43] RDP (0): en1 af=18  addr= netmask=
    [2014-Mar-29 12:03:43] RDP (0): en1 af=30 (AF_INET6)  addr=fe80::226:bbff:fe00:c3d7%en1
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:03:43] RDP (0): en1 af=2 (AF_INET)  addr=192.168.1.29 netmask=255.255.255.0
    [2014-Mar-29 12:03:43] RDP (0): fw0 af=18  addr= netmask=
    [2014-Mar-29 12:03:43] RDP (0): p2p0 af=18  addr= netmask=
    [2014-Mar-29 12:03:43] RDP (0): utun0 af=18  addr= netmask=
    [2014-Mar-29 12:03:43] RDP (0): utun0 af=30 (AF_INET6)  addr=fe80::c852:1a8d:126a:a88a%utun0
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:03:43] RDP (0): utun0 af=30 (AF_INET6)  addr=fdce:4b1d:30c:78f8:c852:1a8d:126a:a88a
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:03:43] RDP (0): --- END INTERFACE LIST ---
    [2014-Mar-29 12:03:43] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Mar-29 12:03:43] RDP (0): client version: 8.0.24428
    [2014-Mar-29 12:03:44] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Mar-29 12:03:44] RDP (0): Resolved '10.1.10.11' to '10.1.10.11' using NameResolveMethod_DNS(1)
    [2014-Mar-29 12:03:52] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Mar-29 12:03:52] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Mar-29 12:03:52] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Mar-29 12:03:52] RDP (0): lo0 af=18  addr= netmask=
    [2014-Mar-29 12:03:52] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Mar-29 12:03:52] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
    [2014-Mar-29 12:03:52] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:03:52] RDP (0): gif0 af=18  addr= netmask=
    [2014-Mar-29 12:03:52] RDP (0): stf0 af=18  addr= netmask=
    [2014-Mar-29 12:03:52] RDP (0): en0 af=18  addr= netmask=
    [2014-Mar-29 12:03:52] RDP (0): en1 af=18  addr= netmask=
    [2014-Mar-29 12:03:52] RDP (0): en1 af=30 (AF_INET6)  addr=fe80::226:bbff:fe00:c3d7%en1
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:03:52] RDP (0): en1 af=2 (AF_INET)  addr=192.168.1.29 netmask=255.255.255.0
    [2014-Mar-29 12:03:52] RDP (0): fw0 af=18  addr= netmask=
    [2014-Mar-29 12:03:52] RDP (0): p2p0 af=18  addr= netmask=
    [2014-Mar-29 12:03:52] RDP (0): utun0 af=18  addr= netmask=
    [2014-Mar-29 12:03:52] RDP (0): utun0 af=30 (AF_INET6)  addr=fe80::c852:1a8d:126a:a88a%utun0
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:03:52] RDP (0): utun0 af=30 (AF_INET6)  addr=fdce:4b1d:30c:78f8:c852:1a8d:126a:a88a
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:03:52] RDP (0): --- END INTERFACE LIST ---
    [2014-Mar-29 12:03:52] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Mar-29 12:03:52] RDP (0): client version: 8.0.24428
    [2014-Mar-29 12:03:52] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Mar-29 12:03:52] RDP (0): Resolved 'javpeds.com' to '70.88.173.126' using NameResolveMethod_DNS(1)
    [2014-Mar-29 12:03:52] RDP (0): Resolved 'javpeds.com' to '70.88.173.126' using NameResolveMethod_DNS(1)
    [2014-Mar-29 12:03:53] RDP (0): Exception caught: Exception in file '../../librdp/private/httpendpoint.cpp' at line 209
        User Message : The gateway failed to connect with the message:
    500 Internal Server Error
    [2014-Mar-29 12:03:53] RDP (0): Exception caught: Exception in file '../../librdp/private/httpendpoint.cpp' at line 209
        User Message : The gateway failed to connect with the message:
    500 Internal Server Error
    [2014-Mar-29 12:03:53] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
    [2014-Mar-29 12:03:53] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Mar-29 12:03:53] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Mar-29 12:04:24] RDP (0): *** Application terminated ***
    [2014-Mar-29 12:53:47] RDP (0): Final rdp configuration used: gatewayhostname:s:javpeds.com
    screen mode id:i:2
    use multimon:i:0
    session bpp:i:24
    full address:s:10.1.10.11
    audiomode:i:2
    username:s:javpeds\ptraquair
    disable wallpaper:i:0
    disable full window drag:i:0
    disable menu anims:i:0
    disable themes:i:0
    alternate shell:s:
    shell working directory:s:
    authentication level:i:2
    connect to console:i:0
    gatewayusagemethod:i:1
    disable cursor setting:i:0
    allow font smoothing:i:1
    allow desktop com"font-family:'SF Cartoonist Hand';font-size:18px;line-height:normal;" />bookmarktype:i:3
    use redirection server name:i:0
    [2014-Mar-29 12:53:47] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Mar-29 12:53:47] RDP (0): lo0 af=18  addr= netmask=
    [2014-Mar-29 12:53:47] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Mar-29 12:53:47] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
    [2014-Mar-29 12:53:47] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:53:47] RDP (0): gif0 af=18  addr= netmask=
    [2014-Mar-29 12:53:47] RDP (0): stf0 af=18  addr= netmask=
    [2014-Mar-29 12:53:47] RDP (0): en0 af=18  addr= netmask=
    [2014-Mar-29 12:53:47] RDP (0): en1 af=18  addr= netmask=
    [2014-Mar-29 12:53:47] RDP (0): en1 af=30 (AF_INET6)  addr=fe80::226:bbff:fe00:c3d7%en1
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:53:47] RDP (0): en1 af=2 (AF_INET)  addr=10.59.1.176 netmask=255.255.255.0
    [2014-Mar-29 12:53:47] RDP (0): fw0 af=18  addr= netmask=
    [2014-Mar-29 12:53:47] RDP (0): p2p0 af=18  addr= netmask=
    [2014-Mar-29 12:53:47] RDP (0): utun0 af=18  addr= netmask=
    [2014-Mar-29 12:53:47] RDP (0): utun0 af=30 (AF_INET6)  addr=fe80::e590:f4:e6f3:79ee%utun0
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:53:47] RDP (0): utun0 af=30 (AF_INET6)  addr=fdce:4b1d:30c:78f8:e590:f4:e6f3:79ee
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:53:47] RDP (0): --- END INTERFACE LIST ---
    [2014-Mar-29 12:53:47] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Mar-29 12:53:47] RDP (0): client version: 8.0.24428
    [2014-Mar-29 12:53:47] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Mar-29 12:53:47] RDP (0): Resolved '10.1.10.11' to '10.1.10.11' using NameResolveMethod_DNS(1)
    [2014-Mar-29 12:53:55] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Mar-29 12:53:55] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Mar-29 12:53:55] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Mar-29 12:53:55] RDP (0): lo0 af=18  addr= netmask=
    [2014-Mar-29 12:53:55] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Mar-29 12:53:55] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
    [2014-Mar-29 12:53:55] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:53:55] RDP (0): gif0 af=18  addr= netmask=
    [2014-Mar-29 12:53:55] RDP (0): stf0 af=18  addr= netmask=
    [2014-Mar-29 12:53:55] RDP (0): en0 af=18  addr= netmask=
    [2014-Mar-29 12:53:55] RDP (0): en1 af=18  addr= netmask=
    [2014-Mar-29 12:53:55] RDP (0): en1 af=30 (AF_INET6)  addr=fe80::226:bbff:fe00:c3d7%en1
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:53:55] RDP (0): en1 af=2 (AF_INET)  addr=10.59.1.176 netmask=255.255.255.0
    [2014-Mar-29 12:53:55] RDP (0): fw0 af=18  addr= netmask=
    [2014-Mar-29 12:53:55] RDP (0): p2p0 af=18  addr= netmask=
    [2014-Mar-29 12:53:55] RDP (0): utun0 af=18  addr= netmask=
    [2014-Mar-29 12:53:55] RDP (0): utun0 af=30 (AF_INET6)  addr=fe80::e590:f4:e6f3:79ee%utun0
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:53:55] RDP (0): utun0 af=30 (AF_INET6)  addr=fdce:4b1d:30c:78f8:e590:f4:e6f3:79ee
    netmask=ffff:ffff:ffff:ffff::
    [2014-Mar-29 12:53:55] RDP (0): --- END INTERFACE LIST ---
    [2014-Mar-29 12:53:55] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
    [2014-Mar-29 12:53:55] RDP (0): client version: 8.0.24428
    [2014-Mar-29 12:53:55] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Mar-29 12:53:55] RDP (0): Resolved 'javpeds.com' to '70.88.173.126' using NameResolveMethod_DNS(1)
    [2014-Mar-29 12:53:55] RDP (0): Resolved 'javpeds.com' to '70.88.173.126' using NameResolveMethod_DNS(1)
    [2014-Mar-29 12:53:56] RDP (0): Exception caught: Exception in file '../../librdp/private/httpendpoint.cpp' at line 209
        User Message : The gateway failed to connect with the message:
    500 Internal Server Error
    [2014-Mar-29 12:53:56] RDP (0): Exception caught: Exception in file '../../librdp/private/httpendpoint.cpp' at line 209
        User Message : The gateway failed to connect with the message:
    500 Internal Server Error
    [2014-Mar-29 12:53:56] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
    [2014-Mar-29 12:53:56] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Mar-29 12:53:56] RDP (0): ------ END ACTIVE CONNECTION ------
    [2014-Mar-29 12:54:05] RDP (0): *** Application terminated ***

  • X11 works locally but not from remote clients because DISPLAY is /tmp/...

    I've used X11 plenty of times before, but not in a little while. Now, when I start X11 on two different accounts, the DISPLAY variable is /tmp/launch-*/org.x:0 . When I telnet to a remote host and set the DISPLAY variable to my hostname:0 (ie. graphe:0), xterm says it can't connect to the display.
    If I set DISPLAY to localhost:0 and start a local xterm it complains too:
    xterm Xt error: Can't open display: localhost:0
    From scanning this forum, I believe this may have something to do with ssh, but on one of the accounts where I have this problem I don't even have ssh configured.
    What's the deal?

    ssh -X (or -Y) exports your local host DISPLAY environment over a secure ssh tunnel to the remote system, where it creates a local X11 port pointing at the remote end of the secure ssh tunnel, and it creates the DISPLAY environment variable to specify the secure tunnel port.
    It is a much (MUCH) more secure way to use X11 than previous methods, speaking as someone that has been using X11 since the early '90s. I did it the xhosts way for years, but about 6 years ago, I switched over to ssh -X and have never looked back.
    Oh yea, several of my machines are about 2,000 miles away (all inside the company network, but still a long way away).
    Message was edited by: BobHarris

  • Access AFP, email, Remote Desktop via VPN and local network but NOT web

    How can I do this? Right now I can set up all these services where I can access them via VPN only, but not on the local network or via the web. If I want to access them via the local network I have to open up the ports in the firewall, however this opens up access via the web (not requiring VPN) which I do NOT want. How do I remedy this?

    How can I do this? Right now I can set up all these services where I can access them via VPN only, but not on the local network or via the web. If I want to access them via the local network I have to open up the ports in the firewall, however this opens up access via the web (not requiring VPN) which I do NOT want. How do I remedy this?

  • Email @me and gmail work fine, but not from iPhoto

    e-mail works fine, checked all connections, PWs etc., but not when sending photos from iPhoto; error message is :The email server didn't recognize your username/password combination.  I've checked both in email accounts and reset both.

    What are you settings in the iPhoto Preferences > General?
    If you have set "Email photos using iPhoto", change this to "Email photos using Mail". This works more reliably.

  • IChat AV 4 works wireless but not wired

    I've got iChat AV 4 on an iMac running Leopard. When I connect the iMac to my net with Airport, then iChat has no trouble contacting the Apple test accounts (like appleu3test03). When I connect to the net with the iMac's ethernet, then iChat AV fails to make audio or video connections (note, everything else continues to work, including Skype AV if I launch it). It complains that there was a "communication error" and it "did not receive a response" from the other side.
    Both the wire and wireless are controlled by the same router. I've tried two, with the same results in each case. When using a Netgear WGR614v6 I let the Netgear handle DHCP. When using a USR8054 I told it to act dumb and let my DSL modem (Actiontec M1000 from Qwest) handle DHCP duties. Again, in both cases the wireless connection to the router allowed iChat AV to connect properly while the wired connection ended in an error message.
    What could be going wrong here? Why might the wired connection be failing to allow AV chats?
    Thanks for any insights,
    ...Eric

    I would try one thing (this worked for me, thanks to you for telling me that wireless worked)
    goto system preferences >> Network
    delete the wired connection
    create another of the same type with a DIFFERENT NAME (ie. Eth1 instead of Ethernet)
    type in the same settings as you had previously (manual IP/DHCP, etc)
    try iChat again.
    Like i said, it worked for me.

Maybe you are looking for

  • How do I remove the background from a movie / sound problems

    Apologies, not really sure what I'm doing- How do I remove the background from a movie I made? I imported a QT movie at 368/272 pixels, but for whatever reason the HTML jumps up to 550/400. The movie is still 368/272 but there is a background border

  • Whitebook custom bios logo

    Hey all,    I bought a MS-1733 whitebook. So far I love it, have it running with 2 SSD's, core i5, and running Win7-32bit. But I am bored with the blank logo screen on boot and would like to add my own. Is this possible? I have built a bunch of PC's

  • How to run a 32-bit plugin on 64-bit Mac in PS CS5?

    Hi... I have developed an automation plugin for PS CS 3,4 & 5 using CS4 SDK in 32-bit Mac processor. Problem with this is that the plugin works for CS5 in 32-bit mode, but the plugin doesn't load when tried with CS5 on 64-bit mode. I made changes in

  • My mac/Safari keeps shutting down and asks if I want to relaunch or report this to apple.  I copied the report:

    This is a copy of the report.  Can anyone tell me what to do? Process:         Safari [889]  Path:            /Applications/Safari.app/Contents/MacOS/Safari Identifier:      com.apple.Safari Version:         5.0 (5533.16) Build Info:      WebBrowser-

  • Unknown Error Code 1418

    I just got my 80GB iPOD Classic yesterday. I downloaded the latest version of iTunes, transfered about 1.43GB of songs to realize that: 1. My iPOD has frozen, I can't even switch it off 2. I can only re-set it and it goes back to the iPOD menu screen