wireless remote desktop connection 1

[newkidontheblock]

Everytime I try to login from my win 2k3 server to my wireless xp pro desktop i am able to get to the login screen of the laptop but as soon as login takes place i lose connection. it appears that as remote desktop allows only one connection for xp and that in a wired scenario the rdp runs as a service one can login to remote desktop ok. With this wireless connection it appears the wireless service can only run when the laptop is logged on locally Is this the case? if anyone knows how i can connect via remote desktop to my wireless-only laptop using remote desktop it would be appreciated.

 

[bcastner]

The wireless connection is irrelevant, there is no reason it will not work related to it being wireless.

Other factors are at issue. You description sounds like one or both sides are using NVIDIA display adapters or chipsets.

Upgrade the NVIDIA driver, or disable the NVIDIA helper services using services.msc

 

[newkidontheblock]

No there is no nvidia.

It is a intel pro 2100 3a wireless adapter in laptop and linksys wrt54g router. The video card is 128mg ati radeon 9600 pro turbo. I can consistently recreate the scenario each time so some required service is not running. If i connect to my server from the laptop via wireless rdp there is no issue as the server is hard wired to the router. it is only the other way that i get this error.

 

[bcastner]

What is the error message?

I assure you it is not a service issue with your wireless.

 

[newkidontheblock]

The error is the system freezes after login and the connection is lost. If i goto the laptop and login locally , the wireless card reestablishes its network connection. i am running sp2 on the laptop.

 

[newkidontheblock]

i run wireless locally in my lan and only on my laptop. the isp feed is fibre through a wall jack. some additional info needed. i can usually get to the desktop of laptop for about ten seconds and then then connection drops. desktop is frozen and i must goto laptop and login locally. i am able to re establish connection with wireless card once i do that

 

[bcastner]

Are you at Service Pack 2 on the laptop?

 

[newkidontheblock]

I stated that i am running sp2 on the laptop which i think is a very poor effort from ms personally. I do not like the way it now establishes a network connection.

i am an IT admin and we have had had numerous issues with deploying it.

 

[bcastner]

You did state that in your third post, my apologies.
Second question: do you have your Win2003 server set as a terminal services server?

 

[newkidontheblock]

good question. no i do not have terminal services installed on windows 2003 server service pack 1 rc 1.

 

[bcastner]

on windows 2003 server service pack 1 rc 1."

Okay. Time to elevate this so you do not waste any more time. I have racked my brain trying to remember if I did exactly your scenario: RD from Console (0) to workstation client running XP SP2 wireless.

I note the following:

. Intel has revised since early-December the ProSet and wireless drivers at least twice; but as I mentioned above it is not a service issue per se. The RD client does not host a service in making the connection. This is all Level-3 stuff in the OSI model.

. There are at times odd driver issues. But if they did not surface with workstation --> Windows2003 RD connection, then they are not in play.

. If have SP1 rc1b running on my Win2003 server, but it is not a production server. I have not tried to duplicate your experience, perhaps this weekend I can try. My notebook with the Intel 2100 is in the Virgin Islands at the moment. I honestly want to RD into the server, and never want to use it as a client machine. But it should work.

. Now the elevation: see my notes here: thread779-923312

 

[newkidontheblock]

look forward to your results. i will be bugging others in my community to test this scenario elsewhere. it drives me crazy but would not be the first time ms overlooked something.

 

[cdogg]

Apologize if I missed it, but did you try to hard-wire the laptop into the router over ethernet? I wonder if in that configuration whether or not there would still be an issue with the server connecting to the laptop.

If not, then at least you'd have ruled out an OS conflict between the two, narrowing it down to either the wireless network settings on the router or within the OS.


~cdogg
[tab]"All paid jobs absorb and degrade the mind";
[tab][tab]- Aristotle
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884

 

[newkidontheblock]

guess what. afer uninstalling service pack 2 on xp pro and reverting to 1a the issue is gone. guess ms and intel have some work to do. thanks for all your help. feel free to send any more info you discover.

 

[bcastner]

Surely you had:
. an exception in the firewall for Remote Desktop
. an exception for uPnP
. a port forward through your router for TCP 3389

 

[newkidontheblock]

answer to your questions are all yes. hardwired no prob. im an mcsa 2003 with n+ and a+ and go through all the nightmare scenarios. thanks for the help. in fact i am responding to you throught the laptop via my server rdp connection

 

[caravelle]

HI, so if and understand correctly the solution is to go back to SP1? I have a Acer Travelmate 8006MLi with SP2 PRO and ATI 9600 and Intel Pro 2200 and a PIV 2.8 Go. with D-link PCI DWL 520,router Dlink DI-624 and I have exactly the same problem.I have tried from diffrents pc and the problem is the same with the Acer.

 

[newkidontheblock]

I would have to say yes if you want to be able to use wireless networking from a wired workstation to the wireless laptop. roll back to sp1a and enjoy.

 

[bcastner]

I duplicated I think exactly this original posters hardware setting, and have no issue under Service Pack 2.

 

[caravelle]

Well anyway I can not roolback to sp1 the pc was delivered with windows xp pro sp2 pre installed, so back to square1