Jump to content

caintgetrite

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About caintgetrite

caintgetrite's Achievements

0

Reputation

  1. Microsoft Tech Support admits it's a bug. I spoke with the next level of tech support today at Microsoft, and the guy basically told me that it is in fact a bug in Vista that will be addressed with SP1, scheduled for release in November. He specifically referenced this article: http://arstechnica.com/news.ars/post/20070...n-expected.html With the highlight being this paragraph: "Other enhancements expected in SP1 include improved performance when copying files and shutting down the computer, support for SD Advanced Direct Memory Access, support for the Windows flash file system ExFat, the ability to boot using EFI instead of BIOS on 64-bit x86 machines, and improved connections for MeetingSpace and Remote Assistance when behind firewalls." So I suppose that I will have to wait a while until SP1 is released and see if it resolves this issue. I did put in a request if I could participate in beta testing this one particular patch or hotfix, should it become available before the SP1 release. I'm supposed to be contacted by Chris Boyce of Microsoft sometime tomorrow, who is a tech support supervisor, with an answer to this request. To answer mercury 22's post, yes, I have tried (on both ends) the Live Messenger 8.5 beta release, and it fared no better. So yes, that option was tried. The one commonality between all three machines (two running Vista Ultimate, one running XP Pro) is that we are all running Avast Antivirus. We all tried disabling the On-Access Scanning feature, thinking that may have something to do with it, but it still didn't work. My machine and the XP machine are only using Windows Firewall, with Remote Assistance checked in the Exceptions list. The other Vista machine is running Kapersky, which was disabled when we were trying to connect, and it still didn't work. From what I gather: Until the SP1 update is released, I have two options: either use CrossLink's software, or have each party disconnect their router and plug their broadband modem straight into their ethernet jack. I probably will settle for using CrossLink for now, as I'd rather not have people on the other end unplugging and replugging and rebooting etc. etc.
  2. You know, I thought that was it, so I went out to Best Buy and purchased a brand new "Vista Compatible" Linksys WRT54GS router and thought it would solve the problem. It didn't. Still couldn't connect. After that, I did a complete reformat and reinstall of Vista Ultimate, thinking maybe I would try it from scratch. Didn't help. Remember, this is with two different people, at two different locations, one with Vista, the other with XP. Two different ISP's, too (one DSL based, the other Cable). Both worked before. Neither work now. I've seen some weird Windows glitches over the years, but this one really has me stumped. Microsoft Tech Support is supposed to call me back today between 8 and 10, I'll see what they have to say. I would think that it could be my hardware, yet everthing worked just fine in XP when I was using RA. Searching through various forums online, and particularly Microsoft's own Vista support forums, it appears that I'm not the only one having these problems: http://windowshelp.microsoft.com/communiti...amp;m=1&p=1 http://windowshelp.microsoft.com/communiti...amp;m=1&p=1 http://windowshelp.microsoft.com/communiti...&sloc=en-us I have discovered the freeware program "CrossLink" on CNET's download.com, which apparently is some type of VNC for Dummies...pretty simple interface, and it appears to work for me for now. And this is with the original D-Link router put back into place (I'm probably going to return the Linksys...$70 and still no Vista Remote Assistance working.) The CrossLink software just works, no ports to be set up in the router, just the one checkbox to be enabled in Windows Firewall exceptions, and it's off and running. Which in my estimation is how Remote Assistance is supposed to work in Vista. The same way that it worked in XP Pro...real simple through Windows Messenger. Why doesn't it?? I seem to recall that part of Vista's advertising noted that Remote Assistance would be greatly improved and easier than ever...I have to wonder.
  3. Looking to see if the experts here can help me figure this one out. A little over a week ago I upgraded my machine from Windows XP Professional to Vista Ultimate. One of the tools that I used often, without fail, in XP Pro was Remote Assistance to help out friends and family with their minor computer issues. I had always used the Windows Live Messenger (8.1) method of having them request remote assistance from me, and it worked every time. Since the Vista Ultimate upgrade (clean install), I could never get Remote Assistance to work. It would make the connection and get up all the way to them entering a password for me, then the Remote Assistance window would come up...then nothing. Just a white screen instead of their desktop, then a time out error. After four different calls to Microsoft Technical support, I was able to get Remote Assistance working just fine (sort of...keep reading). It wasn't without quite a bit of effort though. More details can be found at the thread I start about it at another site...kind of details my trials and tribulations with this situation up to now. www.pro-networks.org/forum/about96338.html Anyway, after all the edits I had to make to the Vista Group Policy section as suggested by the Microsoft PRO support tech guy, Remote Assistance will work, BUT...only if I bypassed the DI-624. As soon as I hooked the router back up, problems resumed. No connection. I double checked and I do have Version 2.76 firmware installed in the router. I have tried the whole "Open Port 3389" thing, but that didn't do any good. I tried giving myself a static IP in the router, then opening myself up in the DMZ. Still nothing. I tried creating a dyndns account in case that would work, but it didn't. I spoke with D-Link technical support this afternoon and told them the same thing. They think that it could be that the DI-624 isn't completely compatible with Vista, and perhaps that could be causing the error. Does anyone here have any *specific* ideas on how this can be resolved? I will freely admit that I probably don't have a clue as to what I'm doing here, or what I need to do. If I need to open specific ports that I haven't tried already, where and how exactly? Would the whole dyndns service thing help me at all? And if so, once I have my URL, how exactly should I go about setting it up to make Remote Assistance work? Remember, this is about Remote Assistance, **not** Remote Desktop. Messenger 8.1 chat and simple file transfers work fine, but Remote Assistance does not. NOTE: I'd rather not go into moving over to the whole "VNC" software thing (Tight, Ultra, etc. etc.), as I want to keep this as simple and trouble free for the people I'm trying to help over a great distance. They're used to Remote Assistance, and I'd rather keep it that way. I would certainly appreciate any help and/or guidance that any of you here could provide. Thanks very much in advance for your time. --EDIT TO ADD-- D-Link DI-624 Rev. C router "emulator" setup: http://support.dlink.com/emulators/di624_revc/ Perhaps this could be useful in guiding me exactly where and how to open particular ports on this router. Thanks.
×
×
  • Create New...