|
|
#1 |
|
Junior Member
|
Remote Desktop & Shoutcast Server Problems
ok so this is weird...
i use remote desktop to manage a dedicated windows 2000 server i recently installed shoutcast server and have had good luck with it thus far but since my remote desktop is usually up on my development machine, i didnt notice an odd problem. when i close out of remote desktop on my local machine, the Shoutcast server on the dedicated server shuts down. i am using scripts on my home page to access the xml object for online/offline status so when this occurns, my entire page goes down because there is no XML object when the shoutcast server shuts down and of course there is not station running at this point. closing out of remote desktop should not affect the applications that are open on the server itself. what is the workaround here? thanks! |
|
|
|
|
|
#2 |
|
Alumni
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,108
|
I use Windows Remote Desktop also, but have not experienced the problem you describe.
Are the DNASs visible or hidden when you exit? How do you terminate the session? |
|
|
|
|
|
#3 |
|
Junior Member
|
i have tried it a number of ways. i have tried just closing remote desktop and also logging off. the DNASs gui is visible when i exit.
|
|
|
|
|
|
#4 |
|
Alumni
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,108
|
Try minimizing/hiding the DNAS window beofer closing the session.
Try running a couple command prompts in various stages of visibility and see if those bahave in the same manner. |
|
|
|
|
|
#5 |
|
Junior Member
|
ok so i tried hiding it first..no dice. but if you use remote desktop and it works for you what is your exact procedure?
minimize server and then log off? minimize and just close remote desktop? regardless i gotta get this issue fix because as far as i can tell it should be a non issue. |
|
|
|
|
|
#6 |
|
Alumni
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,108
|
I minimize all running tools, then close the session.
I do not log off. Have you tried (a flavor of) VNC? |
|
|
|
|
|
#7 |
|
Junior Member
|
so u use VNC? not actually remote desktop? is VNC safe to use on the server in terms of password sniffing etc and do i need to install vnc server on the computer or will it ocnnect thru remote deskop..
i cannot belive that this is non fixable issue with remote desktop. |
|
|
|
|
|
#8 | |
|
Alumni
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,108
|
Quote:
|
|
|
|
|
|
|
#9 |
|
Junior Member
|
could the fact that i use port 9100 have anything to do with this? there must be some way around this...
|
|
|
|
|
|
#10 |
|
Junior Member
|
ok so i see now that no matter what app i open gets shut down..outlook, AIM...it seems when i close remote desktop or log off it kills all processes. how do i get around this???
|
|
|
|
|
|
#11 |
|
Alumni
Join Date: Sep 2001
Location: Maui, Hawaii
Posts: 14,108
|
Sounds like it may be time for Windows Remote Desktop assistance.
|
|
|
|
|
|
#12 |
|
Member
|
Use winvnc
http://www.uk.research.att.com/vnc/ or radmin http://www.famatech.com/default.html When using remote desktop with win2k/xp your session gets terminated when loging off or exiting, thus all the apps close. If you ran win2k advanced or win2003 with windows built in remote server for multiple uses concurrently it would not do that. However for win2kpro, winvnc or radmin is the workaround if your not so lucky to have a copy of win2k advanced or win2003 with remote server. I run a win2k pro server colocated in a datacenter and use win vnc, and webcast from there so i dont have to jack with a crappy local cable/dsl provider, runs like champ
Smart Stream Hosting http://www.mediacast1.com |
|
|
|
|
|
#13 |
|
Junior Member
|
ok man i found a hell of a lot simpler way then installing these insecure apps like vnc
first of all if you go into terminal services manager and set it so that sessions dont end then after 2 logins u will end up locked out of your box...dont try it. i set up Shoutcast Server to run as a Service under windows 2000. Another way i found to do it..and a bit simpler is to create an account under the administrator group (regular non admin user wont work) then while logged in as main admin, create a schedule NT task to start Shoutcast server immediately then also set it to run the same task on reboot in case the server is rebooted. either way will work but running shoutcast server as an NT service is cleaner. hope this helps other people who may have this problem. |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|