Jump to content

cucolinwin

Member
  • Posts

    59
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About cucolinwin

cucolinwin's Achievements

0

Reputation

  1. 1. when I do netstat at my PC I get the desired results: TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING Whe I do netstat at the server I DO NOT get anything. 2. I'm able to RD from the server to any other computer in the LAN. 3. We are NOT running any anti-virus at the Server. 4. I have NOT try RD while server is at Safe-mode with networking. 5. Have NOT try VNC. thanks
  2. I went to the registry to see if the port number was changed and its set to 3389. not sure what to do anymore. thanks
  3. thanks AO3, I re-installed it ,but still NOT able to RD to the server.
  4. I only see the update. Do you have a link to download the thing? thanks
  5. This is why: "Remote Desktop Client 6.0 (KB925876) does not appear in the "Add or Remove Programs" item in Control Panel on the Windows Server 2003 Service Pack 2-based computer. Therefore, you cannot uninstall Remote Desktop Client 6.0 (KB925876)."
  6. I just did the upgrade at the server and still the same issue. I'm trying to un-install and re-install, but I cannot see the option at Add/Remove programs. thanks
  7. 1. None of the clients can RD to the server.-(Everyone was able to connect before installing SP2) 2. Terminal service IS running on the server. 3. Remote desktop is enable on the server. 4. I CANNOT telnet on port 3389. 5. Windows firewall is OFF & we don't have any other third party firewall settings on the server. IP and subnet mask are the same as before installing SP2. thanks
  8. After finally installing Server 2003 SP2 we are not able to Remote Desktop to the server. I installed all the updates including updates the NIC cards. I keep getting: "The client could not connect to the remote computer". I'm able to ping the server and connect to the shares. I also tried RDC using the IP instead of name and no luck. Does anyone had the same issue, any suggestions? thanks
  9. Well that config did not work for me. This worked: 1) Run %windir%\framework\v2.0.50727\aspnet_regiis -u <-- uninstalls the 32 bit edition of asp.net 2.0 2) Run "cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 0" from the cmd prompt <--this disables 32 bit mode in IIS 3) Run %windir%\framework64\v2.0.50727\aspnet_regiis -i <-- note the 64 at the end of framework. Personally, I've installed asp.net so many times in the 32 bit world that I didn't even know a framework64 folder existed. 4) Enable asp.net 2.0 in the web services extensions list. 5) Install MOSS.
  10. the correct syntax is: aspnet_regiis -i without the .exe extension. I found the solution which I will post on Monday. If you're trying to install Sharepoint server 2007 on a 64-bit server you should install the 64-bit version of it (it worked for me) and leave the IIS in 64-bit as well. I re-install asp.net v2 but the 64-bit version. Everything works fine now. Thanks guys
  11. and that command: aspnet_regiis.exe -i is not working for me. When I run it just gives me a list of options which I think it means did nothing. thanks
  12. I'm running IIS in 32-bit mode as instructed in the url I provided.
  13. This is the error message: this product requires asp.net v2.0 to be set to 'Allow' in the list of internet information services (IIS) web server extensions. If it is not available in the list, re-install asp.net v2.0 asp.net is set to 'Allow' and I followed these specific instructions: http://office.microsoft.com/en-us/winshare...0211591033.aspx http://office.microsoft.com/en-us/winshare...px#Spec2command We have a Windows Server R2 2003 (64bit). Installing Sharepoint 2007 in Server 2003 is not a problem, but seems complicated at the 64bit version. thanks..
  14. I have to do some work from home to our server 2003. This requires me to reboot into safe mode. I did this the other day, but i was not able to RDC to the server. I went to run>msconfig> at the general tab I selected> Diagnostic Startup-load basic devices and services only. I was not able to connect after this. Is the correct option at the BOOT.INI tab? by selecting /SAFEBOOT with the NETWORK radio button selected? Any help is appreciated. thanks
×
×
  • Create New...