5punk

Right, this is a weirdy. whenever I use the gonk to connect to another machine via remote desktop, the gonk freezes, hangs, goes to shit and needs the extra memory button pressing. this is a bad thing™


I've tried updating drivers (as I saw something mentioning that borked drivers can cause the issue)

Windows is up to date. Problems started recently (proflan), so I dunno if something fettled there did it.


Ideas?

Dr. kitteny berk wrote:the gonk freezes, hangs, goes to shit and needs the extra memory button pressing. this is a bad thing™

I take it that "the extra memory button" is your reset button? i.e. a total freeze?
I take it that it's freezing whenever you connect to any machine via RDP?

Dr. kitteny berk wrote:Windows is up to date. Problems started recently (proflan), so I dunno if something fettled there did it.

Between alcohol and sleep deprivation, can you remember frigging with anything, anything at all?

Dr. kitteny berk wrote:Ideas?

Yes, lots, always.

Yes, total freeze.

Yes, any machine, VNC works fine.

Only thing that got fucked with was fettling to make shares work.

Tried furtling with the RDP settings? Run mstsc /console[*] manually, disable the local resources, reduce the experience threshold and lower the colours.

* for servers

Hmmm, as you know, total freezing does indicate hardware or some other nasty Ring 0 problem, maybe video, maybe TCP/IP, maybe something else entirely.


i) What happens if you telnet to that RDP server/port?

ii) What happens if you replace the RDP client? (here's visionapp Remote Desktop (vRD 1.5))

iii) System Restore to ProfLAN tiem? (I know, I know, the faaabulous way out)

Tricky though Berk, tricky... (s'pose if it wasn't it wouldn't be on the forum )

cheeseandham wrote:i) What happens if you telnet to that RDP server/port?

Doesn't seem to not work (doesn't exactly seem to work either, but that might just be bukkake being a bitch)

cheeseandham wrote:ii) What happens if you replace the RDP client? (here's visionapp Remote Desktop (vRD 1.5))

Same problem.

cheeseandham wrote:iii) System Restore to ProfLAN tiem? (I know, I know, the faaabulous way out)

System restore?

Verdict: Summat is very, very fucked.

I guess since the other client didn't work, my suggestions won't help either. Tried changing the RDP port?

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

Given it's the RDP client that's fucked, no.

also, the same issue exists connecting to bukkake and local machines (bukkake uses a weird RD port already)

Nothing on the interwebs, save checking the remote host has up-to-date video drivers.

Here's mstsc 5.1 - http://www.microsoft.com/downloads/deta ... layLang=en
and 6.0 - http://www.microsoft.com/downloads/deta ... laylang=en
should a reinstall help.

Could workaround with a virtual PC inside your client - but that's perhaps rather extreme.

Changing the mstsc probably won't work since the alternative RDP client didn't work.. but worth a go.

Since berks last ghost/image was FAIL, along with System Restore being disabled (FAIL), and yet all games and everything else works (NOT FAIL) then it looks like one of the rare instances when a launch and nuke may be the only viable alternative.(KILL)

I've also suggested that checking it out via a different install e.g. a BartPE CD might be a good move.

cheeseandham wrote:I've also suggested that checking it out via a different install e.g. a BartPE CD might be a good move.

I'll probably give that a try at some point.

I'm not too keen on nuking as this is a nice well behaved install. (apart from the rdp issue)

Fire it out of a cannon!

Are you using the old RDP client or the new one?
And have you tried reinstalling RDP?

Would changing workgroups at ProfLan fuck this up in any way?
I seem to remember something like this happening once before in work, but I'm buggered if I can remember how we resolved it (probably nuked it)

/unhelpful

I have a simple and yet massively overkill solution (which is why I think it may appeal to you) and my plan runs like this:

Get hold of VMWare Server if you don't have it already
Install a virtual XP machine on it
Use that whenever you need to Remote Desktop into things

I think that was suggested already.

fabyak wrote:I have a simple and yet massively overkill solution (which is why I think it may appeal to you) and my plan runs like this:

Get hold of VMWare Server if you don't have it already
Install a virtual XP machine on it
Use that whenever you need to Remote Desktop into things

Needs more desktop fans, and marbles running down intricate pathways to flick a switch.

Dr. kitteny berk wrote:I think that was suggested already.

So it was! Would work though

[edit] bollocks, that reminds me that I need to set up a Fista VM