|
Ugh. The risk in dial-up networking is that an attacker could tap the phone line and connect up a modem to monitor the signal and hence see the data on the line. You can mitigate this risk by using encrypted PPP - Windows Remote Access Service has this capability, both on the client and server side (Routing and Remote Access).
Encrypted PPP, and VPN, use some form of public-key cryptography to encrypt packets before they're sent. Only the intended recipient should have the key to decrypt the packets. In fact it turns out that full public-key cryptography is too slow for practical encryption, so instead the two keys are used to derive a shared key for use with a simpler encryption algorithm (such as RC4) which is quick enough to keep up with the stream of packets. The higher-level protocol changes this key periodically to reduce the risk that an attacker could work out the key.
The main thing that VPN offers is that you don't need a rack of modems at the server end - you just need a suitable internet connection. The client's packets can come across any intermediate connections and networks; this is less likely to be an issue for you, but it means that the client can be connected to a Digital Subscriber Line. We've recently deployed VPN for ten mobile users - some are still on dial-up, others are using broadband connections.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
Thank you very much for your detail explaination.
|
|
|
|
|
Hi, can any one give me detail instruction how to setup lamplink between two computer?
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Did you mean "Lap Link", using parallel port?
Arsalan Malik
|
|
|
|
|
Yes, do you have any idea or suggestion? I need it in step by step connection and configuration.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Hi, some people said that using windows 2000 is for the server is better than windows server 2003 because windows server 2003 have some error. But some people said that windows server 2003 is better than windows 2000 server (if we use in the server too) because windows server 2003 has some new feature that windows 2000 server doesn't have. Does any body have any comment about using windows 2000 server and windows server 2003 on the server? Which one is better? Are there any website that give the result between windows 2000 and windows server 2003 benchmark?
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Look here,
Lab Report: Windows Server 2003 Outperforms Predecessors
Published: April 24, 2003
http://www.microsoft.com/windowsserver2003/evaluation/performance/etest.mspx
Progload
|
|
|
|
|
All software has bugs. If you encounter one that's causing a problem, call MS technical support - if you don't have a support contract, they'll charge you for the initial call, but if it's a confirmed bug, you'll be refunded. If you do have a support contract with a given number of calls you can make, one will be deducted when you open the issue but again if the bug is confirmed and they issue a hotfix, it'll be credited.
Our experience with Windows Server 2003 is good - one 2.8GHz P4 with 768MB RAM runs Exchange Server 2003 Enterprise Edition for 15 users, SourceGear Vault for 5 users, is a department file-server (about 80GB in use) and is an Active Directory domain controller. CPU rarely goes above 20% - however, this system is mainly bandwidth-limited since we only have 256Kbps upstream bandwidth on our ADSL connection, which the VPN users often saturate. Downstream is either 512Kbps or 1Mbps, I can't remember which. Six users (including myself) in the same office use a 100Mbps switched LAN. I don't think we've had any blue screens on this box, and it's seriously cheap hardware - assembled by myself from some parts bought from an online retailer and some parts left over from a previous system that had fried its processor. I wouldn't advise this, but it does work.
If you plan to run a web server, I'd recommend Server 2003 since IIS 6.0 is a big improvement over its predecessor.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
For a web server the Web Edition of Server 2003 is great -- highly recommended. Stable as a rock, very configurable, and runs on low-end hardware.
Ours is a lowly PII 400MHz with 128MB RAM, and it performs very well.
my blog
|
|
|
|
|
Last I heard you could only get Web Edition if you're already a volume license customer or prepared to become one - it's only available through volume licensing programmes.
Is this still true?
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
As far as I know, yes, it is only available through certain licensing arrangements with Microsoft.
my blog
|
|
|
|
|
Hi, I know that IP address 192.168.x.x is assigned to private IP address for use in our LAN. But I wonder that when our windows 2000 start it try to obtain IP address from DHCP server (if we choose to "Obtain an IP Address Automatically" from TCP/IP property dialog box). If it find DHCP server then it will get an IP address from the server. If it could not find DHCP server then it will assign an IP address itself to 169.254.x.x. From here i have the question, does an IP address of 169.254.x.x is the private IP address like 192.168.x.x? If I choose IP address of 169.254.x.x and assign it (static IP address) to use in my LAN, is it possible to do that?
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Private Address ranges
IANA reserved 4 address ranges to be used in private networks, these addresses won't appear on the Internet avoiding IP address conflicts:
10.0.0.0 through 10.255.255.255
172.16.0.0 through 172.31.255.255
192.168.0.0 through 192.168.255.255
169.254.0.1 through 169.254.255.254 (Reserved for Automatic Private IP Addressing)
(Automatic, meaning Non-Static.)
The range 127.0.0.0 to 127.255.255.255 is reserved for IP loopback addresses, which is mainly used for testing purposes and to check if the TCP/IP stack has correctly loaded.
|
|
|
|
|
Thank you very much for your explaination.
|
|
|
|
|
Ok. Service running using local system account can be allowed to interact with desktop, right? But if service is set to use some other specified account will it be able to interact with desktop?
Also a little off - can I set an application to be running in other then current user account?
We are talking 2000, XP (and possibly NT).
|
|
|
|
|
You may want to take a look at an article posted here on CP,
Start Your Windows Programs From An NT Service
By Xiangyang Liu
Make your MFC, VB and other Windows programs behave like NT services.
http://www.codeproject.com/system/xyntservice.asp
and Another here from Microsoft,
http://www.microsoft.com/msj/0298/service.aspx
Hope that helps.
|
|
|
|
|
Only services running in the LocalSystem context and marked interact can create desktop windows.
Don't do it. Instead, write a remote administration API (you could use DCOM, RPC, sockets, named pipes, ...) and an administration GUI which talks to the service using that interface.
If you only want to show message boxes, you can pass the MB_SERVICE_NOTIFICATION flag to MessageBox, regardless of which account the service is running under.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
Hi, I have a problem while choosing a license when installing windows 2000. I still don't understand between Per seat vs. Per server license mode. Whether I have read Microsoft document but I still don't understand. Does anybody give me an idea about the difference between these two license mode? If you have an example than it would be greater.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Installing with per Server licensing makes sense for small networks; each client connecting to the server uses one license. Per Seat licensing grants the license to the client, so that the client can connect to any server in a large network.
In other terms, Per Server licensing attaches the license to the server. If you have 5 licenses, 5 clients can be connected to the server at a time, and it doesn't matter which clients they are. If you use Per Seat licensing, the license is granted to the client, allowing that client to connect to any server. This makes sense in a large network with many servers.
"My kid was Inmate of the Month at Adobe Mountain Juvenile Corrections Center" - Bumper Sticker in Bullhead City
|
|
|
|
|
Thank you very much for your explaination.
|
|
|
|
|
Does anybody have any experience or information in running the IIS on NT4 with the ability to serve ASP .NET files?
If so what setup is necessary?
post.mode = postmodes.signature;
SELECT everything FROM everywhere WHERE something = something_else;
> 1 Row Returned
> 42
|
|
|
|
|
If you want to run ASP.NET web application, you need to have IIS install property in your computer. In windows NT4, you also need IIS too. To install IIS you need to install windows NT option pack and install visual studio.net. I'm not sure that windows NT option pack could be download from an internet or not. But according to my experience, i installed windows NT option pack from the CDROM at my work place.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
hi
i decided lower my user rights to improve my computer security
but sometimes need "open new console and log in there as admin"
just i do not know how to do it under windows (xp)
so: how to? (expect console will be named desktop here)
thanks for reply
t!
|
|
|
|
|
Right click on the command prompt shortcut, and choose "Run As..."
my blog
|
|
|
|
|
Hi, i have a problem the computer at lab room in my school. I have 10 computer the workgroup, but each member could not ping using the computer name. But it could ping using IP address. If i ping 192.168.0.5 then it is reply. But if I ping "LIBRARY" machine it is notworking. Does any body know its solution.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
