|
| |
|
|
Light
Posts: 199
Joined: 3/28/2002
From: Earth
Status: offline
 |
Web Remote Access, Win2K Server! - 4/30/2003 16:39:13
Hi there, someone knows how to access a windows 2000 server through web remote?
I installed remote installation services also terminal services but I dont know how to access the server from outside of the network! I tried to install tswebsetup.exe but when tried to access this way, server crashed “blue screen” I know that tswebsetup.exe is not compatible with Win2K server. Thanks for reply
< Message edited by abbeyvet -- 4/30/2003 5:08 PM >
|
|
|
|
storm
Posts: 421
Status: offline
|
RE: Web Remote Access, Win2K Server! - 5/1/2003 8:34:55
Ok, there are two ways you can go. I use both depending on the situation.
On the server you want to remote admin install terminal servcies in remote administration mode. After it is installed go to administrative tool and there will be an option to create a set of terminal services client discs. Create the discs and load the client on the host PC (this is the PC you' ll connect with)
After the client is loaded on your PC create a connection to the server/s you want to connect to. You would make one connection for each server.
Now, when you dial or VPN into your network open the client connect folder and double click the connection you made to the server. [Note]During the process of creating a new connection you' ll have the option to compress/cache bitmaps and enable data connection. Select these options, it will speed things up with dialin.
The other method is to install Terminal Services Advanced Client (TSAC) the most recent version, which you will want to use can be found on the MS site. You install and configure this on a W2k server running IIS 5. This allows you to connect to a remote server running terminal services through internet explorer. The good thing about this is you don' t have to have the client installed for it to work. The requiremnts are you need IE 5.0 or better and you cannot be blocking active X.
The client PCs should be running W2K or XP if you want to avoid licensing issues. If you use NT or Win9x you would have to stand up a licensing server. Reason, W2K and XP already have a built in TS cal.
So, sfter TSAC is installed and configured you would dial or VPN into your network, launch internet exploer and in the address bar type the NETBios name of the server. This will connect you to the TS Web Connect screen. In the server form field type in the name of the server you want to connect to and click connect.
The very first time you connect in this fassion give things a minute or two, the server you have TSAC loaded on scans your PC to see if you have the Active X control (.OCX) and if not you will be presented with a dialog box to install it. Say yes of course. This is a one time deal.
I would intall, configure, and test this inside your network first. When it' s running then try with dialin or VPN. I say this because I do not know your network infrastructure, firewalls config, Ip assignment policy, etc. If it works inside and not out then at least you know where to start looking and you know it' s not in the way TS is set up.
good luck......
_____________________________
storm..." Someone put forth the proposition that you can petition the lord with prayer, petition the lord with prayer, petition the lord with prayer...YOU CANNOT PETITION THE LORD WITH PRAYER"
| |
|
|
|
Light
Posts: 199
Joined: 3/28/2002
From: Earth
Status: offline
|
RE: Web Remote Access, Win2K Server! - 5/1/2003 12:14:37
Thanks a lot storm for reply I let you know soon thanks again.
| |
|
|
|
Light
Posts: 199
Joined: 3/28/2002
From: Earth
Status: offline
|
RE: Web Remote Access, Win2K Server! - 5/1/2003 18:15:28
Hi there, it’s strange but I don’t know why when I try to access the server either with terminal service or tswebsetup.exe from other pc by clicking connect button server stop responding With the blue screen fatal errorand I have to reset the main board. thanks
| |
|
|
|
storm
Posts: 421
Status: offline
|
RE: Web Remote Access, Win2K Server! - 5/2/2003 8:25:18
hmmm, off the top of my head I couldn' t say. I access 40+ servers this way and never had a blue screen or other problem. Lets do this, the next time it blue screens leave the server alone, get a pencil and paper and at the top of the screen write down the hex bits exactly as they appear. they will look something like this:
e000000001x2(another hex number, another hex number, another hex number)
also write down any exceptions, such as
KMODE_MODE_KERNAL or anything similiar.
post it here.
These can be used to troubleshoot the problem. If you don' t know how to troubleshoot using hex, let me know and I' ll teach you...
good luck
_____________________________
storm..." Someone put forth the proposition that you can petition the lord with prayer, petition the lord with prayer, petition the lord with prayer...YOU CANNOT PETITION THE LORD WITH PRAYER"
| |
|
|
|
Light
Posts: 199
Joined: 3/28/2002
From: Earth
Status: offline
|
RE: Web Remote Access, Win2K Server! - 5/2/2003 12:03:12
Thanks Strom, I will
| |
|
|
|
Light
Posts: 199
Joined: 3/28/2002
From: Earth
Status: offline
|
RE: Web Remote Access, Win2K Server! - 5/10/2003 18:19:54
Here is the message:
***Stop: 0x0000007F (0x00000008, 0x00000000, 0x00000000,0x00000000,)
unexpected_Kernel_Mode_TRAP
Thanks a lot.
| |
|
|
|
storm
Posts: 421
Status: offline
|
RE: Web Remote Access, Win2K Server! - 5/12/2003 8:12:15
Ok, now we have something to work with.
the first hex number " 0x0000007F" is called the stop bit, this is what threw the error, ie blue screen. The rest of the hex numbers in the ( ) are called the perameter bits.
And then we have the exception itself: " unexpected_Kernel_Mode_TRAP "
The way to troubleshoot this is to go to the KB pick the proper OS, and enter in the stop bit for the search criteria. I usually enter the whole thing to start and if I don' t get any hits then I enter the first two charachters and the last three such as " 0x07F" . Reason being is that the stop bit is usually refered to in this abbreviated form.
Now after you get some hits a little detective work is usually required and this is where the perameter bits come into play. You may find an article that says something like: ....if the third perameter bit is ...... then this is the problem or if the second perameter bit is then this is the problem......etc..
You also want to look for an article that not only matches your stop bit but also matches your exception. In this case it' s unexpected_Kernel_Mode_TRAP
with all that said i did find an article that makes both of these matches and it is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;137539
I think that about covers it. Good luck and let me know what happens.
_____________________________
storm..." Someone put forth the proposition that you can petition the lord with prayer, petition the lord with prayer, petition the lord with prayer...YOU CANNOT PETITION THE LORD WITH PRAYER"
| |
|
|
|
Light
Posts: 199
Joined: 3/28/2002
From: Earth
Status: offline
|
RE: Web Remote Access, Win2K Server! - 5/16/2003 16:19:36
hi there, we changed the mainboard and memory still the same problem perhaps I need to re-install the O/S!
| |
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|
Printable Version 
