|
I have a loptop which use at home and at work. At my home, i have an internet connection via LAN which has it own IP, subnet mask, gateway, DNS, computer name and workgroup. At my office also has it own IP, subnet mask, gateway, DNS, computer name and workgroup too. But it is differences (IP, DNS, GATEWAY, WORKGROUP). When I come to my office i have to change all of these thing to match at my office. When I take it to home, i have to change to match to the system at my home. But now I'm tired in just 2 days. Does anybody know a good method to switch between the system at home and at work very fast without doing manual? I think it could be don't using the script, but I don't know how to do it. Can any people give me some idea or comment?
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Look into netsh . You could also look at using DHCP at work or home. A fair number of DSL/cable routers have DHCP server software built-in.
I don't think there's an easy way to set the workgroup name, but it's not really important - you can still see all workgroups in Entire Network, and you can access network shares by name. It's just a little trickier to browse. What you can't do is have one machine on two different domains - that isn't permitted.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
How about using the script file or using hardware profile? I never don't that before but I think we might be able to use it. Using the script to change the computer IP, GATEWAY, DNS, Workgroup... between home and office. Or using hardware profile to remember the setting of the network card (IP address, DNS, Gateway...). I will try to use it in my lab machine at home.
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Hi, my computer have a problem, i try to install windows 2000 on it. The installation is finish and start to logon windows for the first time. I think the windows logon screen nearly appear, the computer unexpected restart by itself. I try to do it many time but it still restart when the logon screen nearly appear. I decide to install windows xp instead of windows 2000 and the same problem occure. I don't know what is the main problem. Does anybody have any idea about that?
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Hi, I use ADSL router to share the internet in my house. Because difference people use at difference time and difficult to control the power it the router. I have an idea to set auto power shutdown function in my router. What I want to do is set a schedule to turn off the power of my router at 12:00AM everyday. Are there any software or hardward device that could control the time to turn off the device? I need it
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
|
Thank you very much for your information.
|
|
|
|
|
Hi, I just create the an author console in MMC and select Computer Management as the node that I add to my console. I could view the user name... I wonder, if the other computer perform this procedure too, how could I secure my system and data?
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Hi, I have a problem when I connect my computer to the workgroup in my house. I use workgroup system and use static IP address. I already check the workgroup in every computer and it appear the same. Then I check an IP address and it have the same network ID. So it should work fine, but when I turn on two computer running togehter at the same time (one is windows 2k pro and the other one is win2k server) the first computer (win2k server) could see the second computer (win2k pro). But the second one (win2k pro) could not see the first computer (win2k server) on the network. But if I use ping command to ping from the second computer to the first computer, then it is reply. I don't know why it have this problem. Could any one give me an advice or suggestion?
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
I've set my email account in MS Outlook 2003 to IMAP. When I mark my emails to delete they do not get deleted. It seems there is tips here. Thanks for your help.
Mazy
"One who dives deep gets the pearls,the burning desire for realization brings the goal nearer." - Babuji
|
|
|
|
|
I searched for 'imap delete' in Outlook Help, and discovered that you have to click Edit > Purge Deleted Messages.
So obvious, isn't it?
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
Thanks.
Mazy
"One who dives deep gets the pearls,the burning desire for realization brings the goal nearer." - Babuji
|
|
|
|
|
Yeah, I used to see this kind of similar function in Netscap 4.7. If I use IMAP in my e-mail account in Netscape and want to delete the file I have to select the message and click on the delete button. And it display the cross sign near the message. If I want to permanently delete it, I have to go to the File menu and click on command "Compact Folder...". Then it will delete the message permanently from the server and its display on your computer.
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Anyone know if there is a log file somewhere for Add/Remove Programs. I have a pc where someone removed some programs and now it isn't working well. He doesn't remember what he removed.
*no it wasn't me*
thanx
If there's one thing I've learned, it's that life is one crushing defeat after another until you just wish Flanders was dead. - Homer Simpson
|
|
|
|
|
If the programs used Windows Installer, you'll see events in the Application event log (Control Panel > Administrative Tools > Event Viewer).
If not, you might find some logs in the user's Temp directory. This isn't standard, though.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
How can I disable the focus switching when the mouse is moved across the windows in a multiple window desktop view? In other words, require that the mouse be clicked before focus is switched... as is done in win2k and all the older window versions?
Nulli Secundus
|
|
|
|
|
|
Thanks for the input.
Nulli Secundus
|
|
|
|
|
Hi, I use workgroup in my house and use ADSL router to the share the internet in my house. My question are:
1. Can I use Microsoft ISA in workgroup system?
2. Can I use Microsoft ISA to control the internet usage? If I use ADSL router to share the internet.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Microsoft ISA Server, Part I – introduction, installation, configuration, Web caching and Internet access
http://www.windowsecurity.com/articles/Microsoft_ISA_Server_Part_I__introduction_installation_configuration_Web_caching_and_Internet_access.html
|
|
|
|
|
Hi!
Recently I've been asked if my program can be run on a cluster consisting of 2 Win2K machines and I couldn't give an answer, because I don't know nothing about windows clusters Is anybody here to share some light on the subject of server clustering?
The application in question is a client-server app using .NET remoting for communication. The server part consists of SingleCall CAO's and a class instance published explicitely (using RemotingServices.Marshal() ). The server also operates on a locally installed SQLServer, if this makes any difference.
Can this work out-of-the-box on a cluster? Do I have to modify the program/architecture?
I'd be really grateful for any information on this subject.
Best regards,
mav
|
|
|
|
|
Try to read the below definition:
clusterA group of two or more nodes within a system supporting clustering.<br />
<br />
Overview<br />
When a client on a network tries to access shared resources or applications on a cluster, the cluster appears to the client as a single node or server instead of the group of nodes or servers it really is.<br />
<br />
In the Cluster service of Microsoft Windows 2000 and Windows .NET Server Enterprise Server and Datacenter Server, each node in a cluster is a completely independent computer system that must be running Windows 2000 Enterprise Server. Typically, such nodes are connected by a shared storage bus such as an external Small Computer System Interface (SCSI) disk subsystem or RAID array.<br />
<br />
clustering<br />
Any technology that enables two or more servers to appear to clients as a single system.<br />
<br />
Overview<br />
A cluster consists of a group of computers functioning together as a unit, running a common set of applications, and presenting a single image to client systems. Clustering can be implemented in various ways, but its basic goals are to provide businesses with high availability, high reliability, and high scalability solutions for mission critical business operations.<br />
<br />
Clustering solutions generally come in two basic types:<br />
<br />
<br />
Stateful clustering: The goal of this type of clustering is to provide high availability and high reliability for fast, uninterrupted service in high- demand environments that can tolerate minimal downtime (stateful clustering is not designed to scale applications out to handle more users-this is the purpose of stateless clustering discussed next). Stateful clustering works by connecting independent computer systems into a single entity called a cluster, with each system within the cluster being called a node. Generally some multiple of two is used as the number of nodes within a cluster, for example, 2, 4, 8, 16, or 32 nodes. The different nodes within a cluster are usually connected using a shared disk subsystem which typically consists of a hard disk system or RAID-5 array connected to each node using a fast Small Computer System Interface (SCSI) bus or fiber channel connection. The result is a cluster of computer systems that acts and functions as if it were a single system. In stateful clustering, the nodes within a cluster generally share the workload, and when one node fails its workload fails over (transfers to) another node in the cluster with no interruption of services from the user's perspective. When the failed node comes back online, the workload fails back to this node and normal operation of the cluster resumes. Failover in stateful clustering systems can be implemented in different ways, and this is discussed below. An example of a platform supporting stateful clustering is the Cluster service of Microsoft Windows 2000 Enterprise Server and Datacenter Server. Another name for stateful clustering is shared storage or shared something clustering.<br />
<br />
<br />
Stateless clustering: The goal of this type of clustering is to provide high availability and high reliability by enabling administrators to scale out applications to meet increased demand as the number of users and traffic generated increase. Stateless clustering uses a group of nodes (servers) that are not connected in any way apart from the underlying network connectivity. No failover occurs between nodes when a node in the cluster fails. Instead, some form of load balancing is used to share the workload between the different nodes, and if one node fails the other nodes pick up the extra workload with no interruption of services. Stateless clustering is supported by three Microsoft products: Network Load Balancing (NLB), Component Load Balancing (CLB), and Application Center 2000. Another name for stateless clustering is shared- nothing clustering, and SQL Server 2000 supports a form of shared-nothing clustering known as Federated Server Groups.<br />
<br />
Stateful clustering solutions themselves generally fall into three different categories, depending on if and how failover occurs between different nodes:<br />
<br />
<br />
Active/active clustering: This type of clustering makes the most efficient use of system resources because there are no redundant nodes: all nodes run active processes. If one node of a cluster fails, other nodes take on the failed cluster's workload. The latency for failover in this scenario is typically 15 to 150 seconds, depending on the hardware/software configuration. Active/active clustering is supported by the Cluster service of Microsoft Windows 2000 Enterprise Server and Datacenter Server, and by the Cluster service of Windows .NET Server (discussed later in this article).<br />
<br />
<br />
Active/standby clustering: Nodes are paired within a cluster, with one node designated to take over should another node fail. If an active node fails, a standby node assumes its workload. Latency for failover is also 15 to 150 seconds. Active/standby clustering is a more expensive solution than active/active because the standby node is essentially doing nothing unless the active node fails.<br />
<br />
<br />
Fault-tolerant clustering: Nodes are paired within a cluster, and all nodes perform all tasks simultaneously. This is an expensive solution from a hardware point of view, but latency for failover is reduced to a second or less.<br />
<br />
Marketplace<br />
Many different clustering solutions are in the marketplace, but this article focuses on four different clustering technologies delivered by Microsoft platforms and products, namely:<br />
<br />
Windows clustering, previously known as Microsoft Cluster Services (MCSC)<br />
<br />
Network Load Balancing (NLB)<br />
<br />
Application Center 2000<br />
<br />
Component Load Balancing (CLB)<br />
<br />
You can find additional information in separate articles on each of these four solutions.<br />
<br />
Windows clustering is a feature of Microsoft Windows 2000 Advanced Server and Datacenter Server and of Windows .NET Server. Windows clustering is probably Microsoft's best-known clustering platform and was originally developed for Microsoft Windows NT Server Enterprise Edition where it was code-named Wolfpack during its development. Windows clustering is a stateful clustering solution that enables system architects to create clusters from groups of independent computer systems and to run and manage cluster-aware applications. Using Windows clustering, you can build two-way clusters (that is, clusters with only two nodes) on Windows 2000 and Windows .NET Server Enterprise Server edition or four- way clusters on Windows 2000 and Windows .NET Server Datacenter Server edition (Windows NT Server Enterprise Edition supported only two-way clustering). In Windows clustering a cluster connects nodes together using a shared file system and clusters can utilize active/active clustering for maximum reliability and availability. Windows clustering makes an excellent choice for clustering database and messaging applications for enterprises.<br />
<br />
Network Load Balancing (NLB) is a stateless clustering solution included with Windows 2000 and Windows .NET Server Enterprise Server and Datacenter Server editions, and it was formerly called Windows Load Balancing Services (WLBS) on the Windows NT Server 4 platform. NLB provides load balancing of Internet Protocol (IP) traffic to up to 32 independent network nodes (servers) and is typically used to build farms of Web servers or Exchange 2000 Outlook Web Access (OWA) servers for large enterprises. When one node in an NLB cluster goes down, the load is simply redistributed to the remaining nodes.<br />
<br />
Application Center 2000 is a part of Microsoft Corporation's .NET Server family, and is a stateless clustering platform designed to provide a single point of management for farms of Web servers. Appcenter is typically used in conjunction with NLB and CLB to provide high availibity, high reliability clustering that can scale out to large numbers of users. Appcenter manages a collection of servers in a Web farm as a single entity and can be used to create new clusters, join servers to existing cluster, remove nodes from clusters, deploy applications and application components to different nodes within a cluster, move components between nodes of a cluster, monitor the performance of a cluster, and manage load balancing of network connections to cluster nodes and COM+ components within a cluster-aware application.<br />
<br />
Component Load Balancing (CLB) is supported by all versions of Windows 2000 Server and is used to provide load balancing of COM+ objects across distributed applications deployed on up to 16 nodes (servers). CLB is a stateless clustering solution that requires no special hardware but needs Microsoft Application Center 2000 in order to operate.
Before you write any application relate to the network prcess, you have understand some basic concept of network and the environment that you will deploy your application. Understand network environment for the application that you will install make your distribution computer easy to use your application with less of error opportunity. Ex: type of application that you will distribute, system/application protocol that you will use, default port that to transfer packet... These are the concept of network that developer need to understand before they develop their application.
I got this definition from "Microsoft Encyclopedia of Networking, 2nd Edition" Author: Tulloch, Mitch and Tulloch, Ingrid. Publish by Microsoft Press, ISBN: 0-7356-1378-8.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Thanks a lot for this overview!
I'll have to digest it for a while
Regards,
mav
|
|
|
|
|
Please inform what log files will be useful to analyse performance issues for sharepoint portal.
|
|
|
|
|
Can anyone direct me to a cmd flag reference?
For instance why is the /c flag used and why is the /k flag used below:
<br />
Sub Copy()<br />
Set objShell = CreateObject("Wscript.Shell") <br />
WScript.Echo("Copying files...")<br />
'WScript.Echo("cmd /c Copy " & strFolderToStartFrom & strFileToCopy & " \tmp\" & strZip) <br />
objShell.Run("cmd /c Copy " & strFolderToStartFrom & strFileToCopy & " \tmp\" & strZip)<br />
'WScript.Echo("cmd /k unzip -l \tmp" & strZip), 1, False<br />
objShell.Run("cmd /k unzip -l \tmp" & strZip), 1, False<br />
Set objShell = Nothing <br />
End Sub<br />
<br />
Thanks for any help anyone can give me with this!
|
|
|
|
|