GaRFIELD Posted May 14, 2004 Report Share Posted May 14, 2004 Hi AllI have a very special problem.When i connect throo RDP in an Intranet 100Mbit network to a Windows 2003 Termianl Server, typing special characters like: @£$€ works fine. BUT when i connect throo this connection to a 2nd Windows 2003 Terminal server (these 2 servers has 1Gbit coonection between eachother) we sometimes experience that these special characters (all ALT GR+ keys) will not be typed in. all other characters works fine.. even the SHIFT+ keys....All help is very Apreciated. Quote Link to comment Share on other sites More sharing options...
Agent Smith Posted May 14, 2004 Report Share Posted May 14, 2004 Hello GaRFIELD, and welcome to the Forum :D .Initially I cannot think of any reasons as to why this is happening other than to check the obvious like having the same language and keyboard settings on both machines (and this may extend to actually having the same keyboard layout as well).Is it possible to make a connection from your client direct to both servers, and verify that you can get the characters on both servers with a direct connection? If this is so, then perhaps you need to look at the way the connection is made or forwarded from the first server to the second.Whilst having a look around the Knowledgebase, I came accross this M$ Kb282055 which although seems to be relating to "shortcut" keys, may have some relevance to your problem.Are both servers running the same version of the RDP? I believe that M$ have a download for the Advanced Client which you may find better to use than the mmc module (if that is what you are using).Finally, what happens if you make a connection directly from one server to the other? Does the RDP work correctly then?I work on a Novell network, and I know that some of the keyboard combinations (ctrl/alt/delete for example) don't work correctly with the Novell client, but Novell have actually corrected this by building in the key combinations, so they can be used with a screen mouseclick instead. It may be possible, that this is a similar issue.Please post back with any other information you think useful, and I will give it some more thought.Regards. Mr. Mouse. Quote Link to comment Share on other sites More sharing options...
Agent Smith Posted May 14, 2004 Report Share Posted May 14, 2004 I have been having a further look at this.Are you by any chance making the connection which causes problems from a device running Windows CE ?There seems to be a few issues where the ALT key is being mapped to another function, thus causing similar problems to yours.Mr. M. Quote Link to comment Share on other sites More sharing options...
GaRFIELD Posted May 15, 2004 Author Report Share Posted May 15, 2004 HiThanks for the reply.This problem don't occure when you connect directly to the 2 terminal servers. It only occures when you first go to one of them and then connect futher on to the next one. Both servers uses the standard Remote Desktop Client that comes with the windows 2003 server, and also the computer i/we sitt on has the same client. (the one we find easy by searching on M$ pages on the words "remote Desktop Client")The source systems are all from OLD win95, win98 to Win2K and WinXP, and all have experienced the same problem.We often use this way of connecting for rremote access from home, and as the system only has 1 accesspoint, we have to connect futher on to other computers. This makes the problem occure often when we f.eks. try to write a simple mail on the end computer.. hehe.. and are not able to write the @ :( Due to the Liberation day May 17th on Monday i will not be able to test any of your suggestions before Tuesday, but atlest you have given me more hints then even M$ was able to on theire supportline.. Any more information you need?Eksample on a standard conneciton:Win98 Terminal -> Windows 2003 Terminal Server -> Windows 2003 Terminal Server.BR,GaRFIELD Quote Link to comment Share on other sites More sharing options...
Agent Smith Posted May 15, 2004 Report Share Posted May 15, 2004 I will give this some extra thought GaRFIELD, but I would like you to check what happens when you sit at the first server and manually open a connection to the next server.What protocols are you running on the network? I assume it is just IP. Is it at all possible you have some form of security device (firewall, router or a switch capable of working at layer 3) between the servers which may be having an effect?As a work around, have you looked into the possibility of creating a VPN tunnel between the two servers, so that it may be possible to open an RDP session directly with the second server?Mr. M. Quote Link to comment Share on other sites More sharing options...
GaRFIELD Posted May 15, 2004 Author Report Share Posted May 15, 2004 The 2 servers are on the same HP switch with 1Gbit connection. It is a managed switch tho, but has no limits in any form enabled. As you understand the 2 servers are in the same net on the same switch and there should not be any reason for this to happend. Also all the computers that normaly are connecting to them are on the same switch. Only when we connect from home it goes throo the net and not localy.When i sit on the first server and connect to the second (tested yesterday :D ) it always work fine. The problem must be in some way the solution with remote desktop throo another Remote desktop. I was told from M$ that this should not be a problem, tho it was not realy designed for this. (What a supprise.. making something working for once.. hehe)GaRFIELD Quote Link to comment Share on other sites More sharing options...
Agent Smith Posted May 15, 2004 Report Share Posted May 15, 2004 How, may I ask, do you make the external connections? Do you use a modem/isdn, or direct to an external ip address? Does the network have an external gateway for general use at all?Mr. M. Quote Link to comment Share on other sites More sharing options...
GaRFIELD Posted May 15, 2004 Author Report Share Posted May 15, 2004 External connections are normaly throo an ADSL connection, but a couple employees has ISDN (nothing less) from home to a Fixed IP SDSL line.The "GW" into the company is a FW with redirect on a specific port to a specific server (standard), and works fine as long as you only connect to the first server. Sometimes when you connect futher, the special characters don't want to be typed. This happens both internaly inside the same net and from external connections. GaRFIELD Quote Link to comment Share on other sites More sharing options...
Agent Smith Posted May 15, 2004 Report Share Posted May 15, 2004 Ok, so how about using the FW to redirect different ports to different servers?Then you could connect to whichever server you required.Mr. M. Quote Link to comment Share on other sites More sharing options...
GaRFIELD Posted May 15, 2004 Author Report Share Posted May 15, 2004 Well.. we have 1 server only that is accecible from the Internet, so employees has to go throo this to access the other one. (VPN has not yet been installed here...) When we are localy on the net, we can ofcourse connect direcly to both servers, but ofcouse again... some employees don't do this... "Easier to do it throo the other one.. " and that is why i am trying to find a solution on this problem.GaRFIELD Quote Link to comment Share on other sites More sharing options...
Agent Smith Posted May 15, 2004 Report Share Posted May 15, 2004 No problems, I am going to have to do some more research. I will really need to wait till monday, when I will run it past some of the other guys in the office.In the meantime, if you discover anything else that may be relevant to the problem, then please let me know.Mr. M. Quote Link to comment Share on other sites More sharing options...
Agent Smith Posted May 19, 2004 Report Share Posted May 19, 2004 Hi GaRFIELD, this is becoming interesting. I got one of the guys at work yesterday to use PC Anywhere to try and recreate the double connection (we don't have the RDP stuff installed). Guess what, we get the same problem with the second connection :( I am beginning to suspect that this is due to the way the keyboard stroke is submitted to the transmission. When I get some time, I am going to get a list of the key breakdowns and see if I can find a common denominator for the problem.Mr. M. Quote Link to comment Share on other sites More sharing options...
GaRFIELD Posted May 19, 2004 Author Report Share Posted May 19, 2004 Any luck yet?I have now also tested to connect from and XP Pro to the first TS and futher to an standard XP Pro PC and experienceing the same problem. It looks to me that there are a small "bug" in the Remote Desktop Client that causes this to happend, atleast that is the only thing i can see as a solution atm.GaRFIELD :( Quote Link to comment Share on other sites More sharing options...
GaRFIELD Posted May 19, 2004 Author Report Share Posted May 19, 2004 HiJust talked to one of the guys on M$ Proffessional Support, and he has now reported an official "Possible Bug" to the developement team. As soon as i recieve the copy of this, i will post it on this Forum.GaRFIELD Quote Link to comment Share on other sites More sharing options...
Agent Smith Posted May 19, 2004 Report Share Posted May 19, 2004 Thanks for the news GaRFIELD. It's nice to know that the boys at M$ occasionally have to earn their money :D Mr. M. Quote Link to comment Share on other sites More sharing options...
GaRFIELD Posted May 21, 2004 Author Report Share Posted May 21, 2004 :censored: Did it suprise us at all that i have not revieved any email confirmation from M$ yet? Well.. guess we have to find a solution ourself... :( GaRFIELD Quote Link to comment Share on other sites More sharing options...
GaRFIELD Posted June 16, 2004 Author Report Share Posted June 16, 2004 status: 1 more month went by... and still no answer or confirmation from M$..Did we realy think they had improved ?-----------------------------GaRFIELD Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.