Hello everyone, I've been looking everywhere for the multi client and gameguard bypass of shaiya phillipines and still no luck. I have tried using some 3rd party programs like ollydbg and etch editing the game.exe but I failed. During work, I have realized that there is an alternative that can be done via virtualization technology but requires a decent pc desktop specification. Here's how I did it.
You need:
Choose Virtualization software
VMware
VirtualBox
HyperV
etch..
ISO of desired Operating System
Windows XP
Windows 7
etch..
I personally use VMware and Windows XP ISO, so im gonna show you how to do it.
Download and install VMWare.
Open the VMware Player
Create a New Virtual Machine
Install OS later
Choose Microsoft Windows / Windows XP Professional
If you're gonna use this just for Shaiya, alot 20 HDD space and store as a single file.
Click Custumize Hardware
Minumim Memory should be 1024 or 1GB
CD/DVD ROM, Use ISO image file and locate it
Network Adapter should be NAT
Play the Virtual Machine and wait for the installation to finish.
Install the Shaiya Philippines game client
Install VMware tools.
Reboot and start playing!
Screenshot of working Dual Client via VMWare
Should there be any questions, Post a comment and I will be happy to help.
Mark Achel Gagalac
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Sunday, January 16, 2011
Friday, January 14, 2011
How to Optimize Windows 7 Desktop
Here's my personal tips and tweaks to get the best performance of your Windows 7 desktop.
1) Editing the performance options
- Right Click on My Computer then choose Properties.
- Click on Advanced system settings.
- In the Advanced tab under Performance, Click on Settings and choose the "Adjust for best performance".
- Click Apply and hit OK.
2) Tweaking the boot configuration and the system services and startup via msconfig
- Open the RUN command, and type in msconfig
- Click on the Boot tab, edit the Timeout seconds to 3 and click on Advanced options.
- Put the max processor available in the Number of processors options and alot full memory in the Maximum memory option and hit OK.
- Click on the Services tab and check the Hide all Microsoft services.
- You can uncheck everything or just choose the application services you need and click on Apply.
- Click on the Startup tab and click on Disable all. Click on Apply and hit OK.
- Reboot!
After reboot, You will notice that your system is a lot faster than it was before or even small difference but result is actually different. :)
Mark Achel Gagalac
1) Editing the performance options
- Right Click on My Computer then choose Properties.
- Click on Advanced system settings.
- In the Advanced tab under Performance, Click on Settings and choose the "Adjust for best performance".
- Click Apply and hit OK.
2) Tweaking the boot configuration and the system services and startup via msconfig
- Open the RUN command, and type in msconfig
- Click on the Boot tab, edit the Timeout seconds to 3 and click on Advanced options.
- Put the max processor available in the Number of processors options and alot full memory in the Maximum memory option and hit OK.
- Click on the Services tab and check the Hide all Microsoft services.
- You can uncheck everything or just choose the application services you need and click on Apply.
- Click on the Startup tab and click on Disable all. Click on Apply and hit OK.
- Reboot!
After reboot, You will notice that your system is a lot faster than it was before or even small difference but result is actually different. :)
Mark Achel Gagalac
Thursday, January 13, 2011
Top Tips for Importing & Exporting your VM with Hyper-V
As you accumulate virtual machines, then sooner or later you are probably going to run into a situation in which you want to move one or more virtual machines to a new host server. Microsoft makes this possible through the Hyper-V Manager’s Import and Export functions.
If you look at Figure A, you can see that when you select a virtual machine, Hyper-V displays an Export link in the lower right corner of the console. There is also an Import Virtual Machine link at near the top of the Actions pane.
Figure A
The Import and Export functions are accessible through the Hyper-V Manager.
On the surface, it appears that you can simply select a virtual machine, export it, take the exported image to another server that’s running Hyper-V, and import it. On some levels this really is the way that the import and export processes work. There are some gotchas that you need to be aware of though, and the only way that you can avoid those gotchas is to understand what’s really going on when you export and import a virtual machine.
Virtual Machine Identification
The first thing that you need to understand about the import and the export process is that Hyper-V has two different ways of identifying virtual machines. The most obvious way of identifying a virtual machine is by the name that you have assigned to it. For example, if you look back at Figure A, the Actions pane will show you that I have selected a virtual machine named Posey-IM. Virtual machines retain their name throughout the import and export process. Although it is certainly advisable to avoid having multiple virtual machines with the same name, it is not an absolute requirement.
The reason why virtual machine names do not absolutely have to be unique is because there is a second factor that identifies a virtual machine. This second identification factor is the virtual machine’s Globally Unique Identifier, or GUID, which is automatically assigned to a virtual machine by Windows, and does have to be unique.
The Virtual Machine Export Process
The virtual machine export process itself is actually really simple to perform. Simply select a virtual machine from the Hyper-V Manager, and then click the Export link. After doing so, Windows will display the Export Virtual Machine dialog box that is shown in Figure B. All you have to do now is to enter the path that you want to export the virtual machine to, and then click the Export button.
Figure B
The process of exporting a virtual machine is really simple.
So what’s so tricky about the export process? Well, not a lot really, but there are still some things that you need to know about it. For starters, Windows will place the virtual machine within a sub folder that bears the virtual machine’s name within the path that you have specified. For example, I decided to export a virtual machine named R2. Not wanting to lose the files among other clutter, I created a folder named C:\R2 and specified that as the export path. What I ended up with was the exported files residing in a folder named C:\R2\R2\.
One of the big questions that I had about the export process before I began was whether or not it left the original virtual machine instance intact, and in its original location. I’m happy to report that the files making up the virtual machine are untouched during the export process. This does however, mean that you will have to manually remove those files once you have moved the virtual server to its new location.
The other thing that you need to know is that depending on the size of the virtual machine, the export process can take a really long time to complete. Unfortunately, I can’t tell you exactly how long, because the amount of time depends on the size of the .VHD files that are being used, and on your machine’s hardware capabilities.
As you can see, exporting a virtual machine is really simple. Now let's take a look at the anatomy of the exported information, and how the import process works.
The Anatomy of a Virtual Machine
When you export a virtual machine, one of the things that Hyper-V asks you for is the export path. Whatever path you enter, Hyper-V will create a folder in that path that bears the name of the virtual machine that you are exporting. For instance, when I exported my virtual machine, I used C:\R2 as the path, and Hyper-V created a new folder named R2. Now my virtual machine resides in a folder named C:\R2\R2, as shown in Figure C.
Figure C
Hyper-V creates a folder in the destination path that bears the name of the virtual server that you are exporting.
If you look at the figure, you will notice that within the folder that Hyper-V creates are three sub folders. There is also an XML file named Config.xml.
The Snapshots Folder
The Snapshots folder is used as a repository for snapshots of the virtual machine. This folder contains three elements. First, there is a subfolder that bears the virtual machine’s GUID. If no snapshots exist, the folder will still be present, but it will be empty. If snapshots do exist, then this folder will contain the diffing data for the virtual hard disks.
The snapshots folder may also contain a subfolder for each snapshot. This folder bears the name of the individual snapshot ID. In addition, there will be an export file (a .EXP file) for each individual snapshot.
The Virtual Hard Disks Folder
As the name implies, the Virtual Hard Disks folder stores the .VHD files (virtual hard drive files) used by the virtual machine. You can see an example of this in Figure D.
Figure D
The Virtual Hard Disks folder contains the .VHD files for the virtual server.
The Virtual Machines Folder
At a minimum, the Virtual Machines folder will contain a file named after the virtual machine’s GUID, but with an .EXP extension. This file is the virtual machine export file. It retains the virtual machine’s settings during the export process.
If the virtual machine was in a saved state during the export process, then the Virtual Machines folder will contain a sub folder, which will store two saved state files. If the machine was not in a saved state at the time of the export, then the sub folder may exist, but it will be empty.
Importing a Virtual Machine
The import and export process is used primarily as a means for moving virtual machines from one host server to another. Therefore, the first step in the import process is to copy the export folder and all of its sub folders to the desired host server. After doing so, open the Hyper-V Manager and click the Import Virtual Machine link. You should now be prompted to enter the virtual machine’s path.
Although this seems simple enough, there are two very important There are two important things that you need to know about the import process. First, it is up to you to copy the virtual machine files to the location from which you want to use them. When you import the virtual machine, it’s physical location on the host server becomes permanent, and moving the virtual machine is no longer an option. It is therefore important to place the virtual machine files on the desired volume before you import it.
The other thing that you need to know is that when you import the virtual machine, the .EXP file and the CONFIG.XML files will be deleted. These files are replaced with a new CONFIG.XML file. What this means to you is that because the .EXP file is gone, the virtual machine cannot be imported again (unless you export it again). If you want to use the virtual machine as a template or as an image that you can quickly restore, then it is important to work only from a copy of your exported files so that the original remains untouched.
Conclusion
The process of importing and exporting virtual machines isn’t all that difficult, but by following these tips, hopefully you'll save yourself from a few of the most common pitfalls related to duplicate virtual machines or the imported machine’s location.
Source: http://www.petri.co.il/importing-and-exporting-your-virtual-machines.htm
If you look at Figure A, you can see that when you select a virtual machine, Hyper-V displays an Export link in the lower right corner of the console. There is also an Import Virtual Machine link at near the top of the Actions pane.
Figure A
The Import and Export functions are accessible through the Hyper-V Manager.
On the surface, it appears that you can simply select a virtual machine, export it, take the exported image to another server that’s running Hyper-V, and import it. On some levels this really is the way that the import and export processes work. There are some gotchas that you need to be aware of though, and the only way that you can avoid those gotchas is to understand what’s really going on when you export and import a virtual machine.
Virtual Machine Identification
The first thing that you need to understand about the import and the export process is that Hyper-V has two different ways of identifying virtual machines. The most obvious way of identifying a virtual machine is by the name that you have assigned to it. For example, if you look back at Figure A, the Actions pane will show you that I have selected a virtual machine named Posey-IM. Virtual machines retain their name throughout the import and export process. Although it is certainly advisable to avoid having multiple virtual machines with the same name, it is not an absolute requirement.
The reason why virtual machine names do not absolutely have to be unique is because there is a second factor that identifies a virtual machine. This second identification factor is the virtual machine’s Globally Unique Identifier, or GUID, which is automatically assigned to a virtual machine by Windows, and does have to be unique.
The Virtual Machine Export Process
The virtual machine export process itself is actually really simple to perform. Simply select a virtual machine from the Hyper-V Manager, and then click the Export link. After doing so, Windows will display the Export Virtual Machine dialog box that is shown in Figure B. All you have to do now is to enter the path that you want to export the virtual machine to, and then click the Export button.
Figure B
The process of exporting a virtual machine is really simple.
So what’s so tricky about the export process? Well, not a lot really, but there are still some things that you need to know about it. For starters, Windows will place the virtual machine within a sub folder that bears the virtual machine’s name within the path that you have specified. For example, I decided to export a virtual machine named R2. Not wanting to lose the files among other clutter, I created a folder named C:\R2 and specified that as the export path. What I ended up with was the exported files residing in a folder named C:\R2\R2\.
One of the big questions that I had about the export process before I began was whether or not it left the original virtual machine instance intact, and in its original location. I’m happy to report that the files making up the virtual machine are untouched during the export process. This does however, mean that you will have to manually remove those files once you have moved the virtual server to its new location.
The other thing that you need to know is that depending on the size of the virtual machine, the export process can take a really long time to complete. Unfortunately, I can’t tell you exactly how long, because the amount of time depends on the size of the .VHD files that are being used, and on your machine’s hardware capabilities.
As you can see, exporting a virtual machine is really simple. Now let's take a look at the anatomy of the exported information, and how the import process works.
The Anatomy of a Virtual Machine
When you export a virtual machine, one of the things that Hyper-V asks you for is the export path. Whatever path you enter, Hyper-V will create a folder in that path that bears the name of the virtual machine that you are exporting. For instance, when I exported my virtual machine, I used C:\R2 as the path, and Hyper-V created a new folder named R2. Now my virtual machine resides in a folder named C:\R2\R2, as shown in Figure C.
Figure C
Hyper-V creates a folder in the destination path that bears the name of the virtual server that you are exporting.
If you look at the figure, you will notice that within the folder that Hyper-V creates are three sub folders. There is also an XML file named Config.xml.
The Snapshots Folder
The Snapshots folder is used as a repository for snapshots of the virtual machine. This folder contains three elements. First, there is a subfolder that bears the virtual machine’s GUID. If no snapshots exist, the folder will still be present, but it will be empty. If snapshots do exist, then this folder will contain the diffing data for the virtual hard disks.
The snapshots folder may also contain a subfolder for each snapshot. This folder bears the name of the individual snapshot ID. In addition, there will be an export file (a .EXP file) for each individual snapshot.
The Virtual Hard Disks Folder
As the name implies, the Virtual Hard Disks folder stores the .VHD files (virtual hard drive files) used by the virtual machine. You can see an example of this in Figure D.
Figure D
The Virtual Hard Disks folder contains the .VHD files for the virtual server.
The Virtual Machines Folder
At a minimum, the Virtual Machines folder will contain a file named after the virtual machine’s GUID, but with an .EXP extension. This file is the virtual machine export file. It retains the virtual machine’s settings during the export process.
If the virtual machine was in a saved state during the export process, then the Virtual Machines folder will contain a sub folder, which will store two saved state files. If the machine was not in a saved state at the time of the export, then the sub folder may exist, but it will be empty.
Importing a Virtual Machine
The import and export process is used primarily as a means for moving virtual machines from one host server to another. Therefore, the first step in the import process is to copy the export folder and all of its sub folders to the desired host server. After doing so, open the Hyper-V Manager and click the Import Virtual Machine link. You should now be prompted to enter the virtual machine’s path.
Although this seems simple enough, there are two very important There are two important things that you need to know about the import process. First, it is up to you to copy the virtual machine files to the location from which you want to use them. When you import the virtual machine, it’s physical location on the host server becomes permanent, and moving the virtual machine is no longer an option. It is therefore important to place the virtual machine files on the desired volume before you import it.
The other thing that you need to know is that when you import the virtual machine, the .EXP file and the CONFIG.XML files will be deleted. These files are replaced with a new CONFIG.XML file. What this means to you is that because the .EXP file is gone, the virtual machine cannot be imported again (unless you export it again). If you want to use the virtual machine as a template or as an image that you can quickly restore, then it is important to work only from a copy of your exported files so that the original remains untouched.
Conclusion
The process of importing and exporting virtual machines isn’t all that difficult, but by following these tips, hopefully you'll save yourself from a few of the most common pitfalls related to duplicate virtual machines or the imported machine’s location.
Source: http://www.petri.co.il/importing-and-exporting-your-virtual-machines.htm
Saturday, January 1, 2011
Increase bandwidth by tweaking QoS in Windows XP Pro
The following tweak applies only to Windows XP Professional edition.
The default system behavior is that all 100% bandwidth is available, however, if there is a running application that indicates to the OS it needs to send high priority/real time data, then as long as it has the socket open, Windows XP will restrict “best effort” traffic to 80% of the bandwidth so that high priority traffic can be accommodated. Basically, applications can make this request to the operating system for QoS support using the QoS application programming interfaces (APIs) in Windows and this only applies if a specific app is requesting QoS.
If you'd like to change how much bandwidth is reserved for QoS (the default is 20% of the total bandwidth), do the following:
1. Make sure you're logged in as "Administrator" (not just any account with admin privileges).
2. Navigate to START>Run and type: gpedit.msc
3. Navigate to Local Computer Policy > Administrative Templates > Network > QOS Packet Scheduler
4. In the right window, double-click the limit reservable bandwidth setting
5. On the setting tab, check the enabled setting.
6. Where it says "Bandwidth limit %", change it to read 0 (or whatever percentage you want to reserve for high priority QoS data)
7. Click OK, close gpedit.msc
Under START > My Computer > My Network Connections > View Network Connections, right-click on your connection and under Properties (where it lists your protocols), make sure QOS Packet Scheduler is enabled.
The tweak desribed below helps boost priority for DNS & hostname resolution in general. What this means is, it helps web pages load faster, and has negligible effect on downloads (not counting the couple of ms gain with the host resolution at connect-time).
Applying this tweak assumes some proficiency in editing the Windows Registry using Regedit (Start > Run > type: regedit). As always, backup your Registry before making any changes so you can revert to the previous state if you don't like the results.
The default system behavior is that all 100% bandwidth is available, however, if there is a running application that indicates to the OS it needs to send high priority/real time data, then as long as it has the socket open, Windows XP will restrict “best effort” traffic to 80% of the bandwidth so that high priority traffic can be accommodated. Basically, applications can make this request to the operating system for QoS support using the QoS application programming interfaces (APIs) in Windows and this only applies if a specific app is requesting QoS.
If you'd like to change how much bandwidth is reserved for QoS (the default is 20% of the total bandwidth), do the following:
1. Make sure you're logged in as "Administrator" (not just any account with admin privileges).
2. Navigate to START>Run and type: gpedit.msc
3. Navigate to Local Computer Policy > Administrative Templates > Network > QOS Packet Scheduler
4. In the right window, double-click the limit reservable bandwidth setting
5. On the setting tab, check the enabled setting.
6. Where it says "Bandwidth limit %", change it to read 0 (or whatever percentage you want to reserve for high priority QoS data)
7. Click OK, close gpedit.msc
Under START > My Computer > My Network Connections > View Network Connections, right-click on your connection and under Properties (where it lists your protocols), make sure QOS Packet Scheduler is enabled.
The tweak desribed below helps boost priority for DNS & hostname resolution in general. What this means is, it helps web pages load faster, and has negligible effect on downloads (not counting the couple of ms gain with the host resolution at connect-time).
Applying this tweak assumes some proficiency in editing the Windows Registry using Regedit (Start > Run > type: regedit). As always, backup your Registry before making any changes so you can revert to the previous state if you don't like the results.
Sunday, December 12, 2010
Remote Server Administration Tools for Windows 7
Remote Server Administration Tools for Windows® 7 enables IT administrators to manage roles and features that are installed on computers that are running Windows Server® 2008 R2, Windows Server® 2008, or Windows Server® 2003, from a remote computer that is running Windows 7.
Here's the link:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en
Enjoy!
Here's the link:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en
Enjoy!
Friday, December 10, 2010
Linux Integration Services v2.1 for Windows Server 2008 Hyper-V R2
I tried to google a tool and a way to make a linux or redhat based system run on Hyper-V and finally I found a good one.
A set of drivers that enable synthetic device support in supported Linux virtual machines under Hyper-V.
Here's the Link:
http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=eee39325-898b-4522-9b4c-f4b5b9b64551
A set of drivers that enable synthetic device support in supported Linux virtual machines under Hyper-V.
Here's the Link:
http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=eee39325-898b-4522-9b4c-f4b5b9b64551
Sunday, August 22, 2010
PRTG Network Monitor
I was looking for a good network monitoring tool this past few weeks. I tried MRTG, Cacti, Bandwidthd and etch. Cacti seems to be one of the best graphing tool I've used and Nagios for alerts and etch.. But if you guys wants it easy way, You can use PRTG Network Monitor. It's very easy to setup and use but runs only in Windows Operating Systems. I suggest you give it a try.. heres the link:
http://www.paessler.com/prtg/
http://www.paessler.com/prtg/
Monday, August 16, 2010
112 Windows run commands
| Accessibility Controls Add Hardware Wizard Add/Remove Programs Administrative Tools Automatic Updates Bluetooth Transfer Wizard Calculator Certificate Manager Character Map Check Disk Utility Clipboard Viewer Command Prompt Component Services Computer Management Date/Time Properties DDE Share Device Manager Direct X Control Panel (If Installed)* Direct X Troubleshooter Disk Cleanup Utility Disk Defragment Disk Management Disk Partition Manager Display Properties Display Properties Display Properties (w/Appearance Tab Preselected) Dr. Watson System Troubleshooting Utility Driver Verifier Utility Event Viewer File Signature Verification Tool Findfast Folders Properties Fonts Fonts Folder Free Cell Card Game Game Controllers Group Policy Editor (XP Prof) Hearts Card Game Iexpress Wizard Indexing Service Internet Properties IP Configuration (Display Connection Configuration) IP Configuration (Display DNS Cache Contents) IP Configuration (Delete DNS Cache Contents) IP Configuration (Release All Connections) IP Configuration (Renew All Connections) IP Configuration (Refreshes DHCP & Re-Registers DNS) IP Configuration (Display DHCP Class ID) IP Configuration (Modifies DHCP Class ID) Java Control Panel (If Installed) Java Control Panel (If Installed) Keyboard Properties Local Security Settings Local Users and Groups Logs You Out Of Windows Microsoft Chat Minesweeper Game Mouse Properties Mouse Properties Network Connections Network Connections Network Setup Wizard Notepad Nview Desktop Manager (If Installed) Object Packager ODBC Data Source Administrator On Screen Keyboard Opens AC3 Filter (If Installed) Password Properties Performance Monitor Phone and Modem Options Power Configuration Printers and Faxes Printers Folder Private Character Editor Quicktime (If Installed) Regional Settings Registry Editor Registry Editor Remote Desktop Removable Storage Removable Storage Operator Requests Resultant Set of Policy (XP Prof) Scanners and Cameras Scheduled Tasks Security Center Services Shared Folders Shuts Down Windows Sounds and Audio Spider Solitare Card Game SQL Client Configuration System Configuration Editor System Configuration Utility System File Checker Utility (Scan Immediately) System File Checker Utility (Scan Once At Next Boot) System File Checker Utility (Scan On Every Boot) System File Checker Utility (Return to Default Setting) System File Checker Utility (Purge File Cache) System File Checker Utility (Set Cache Size to size x) System Properties Task Manager Telnet Client User Account Management Utility Manager Windows Firewall Windows Magnifier Windows Management Infrastructure Windows System Security Tool Windows Update Launches Windows XP Tour Wizard Wordpad | access.cpl hdwwiz.cpl appwiz.cpl control admintools wuaucpl.cpl fsquirt calc certmgr.msc charmap chkdsk clipbrd cmd dcomcnfg compmgmt.msc timedate.cpl ddeshare devmgmt.msc directx.cpl dxdiag cleanmgr dfrg.msc diskmgmt.msc diskpart control desktop desk.cpl control color drwtsn32 verifier eventvwr.msc sigverif findfast.cpl control folders control fonts fonts freecell joy.cpl gpedit.msc mshearts iexpress ciadv.msc inetcpl.cpl ipconfig /all ipconfig /displaydns ipconfig /flushdns ipconfig /release ipconfig /renew ipconfig /registerdns ipconfig /showclassid ipconfig /setclassid jpicpl32.cpl javaws control keyboard secpol.msc lusrmgr.msc logoff winchat winmine control mouse main.cpl control netconnections ncpa.cpl netsetup.cpl notepad nvtuicpl.cpl packager odbccp32.cpl osk ac3filter.cpl password.cpl perfmon telephon.cpl powercfg.cpl control printers printers eudcedit QuickTime.cpl intl.cpl regedit regedit32 mstsc ntmsmgr.msc ntmsoprq.msc rsop.msc sticpl.cpl control schedtasks wscui.cpl services.msc fsmgmt.msc shutdown mmsys.cpl spider cliconfg sysedit msconfig sfc /scannow sfc /scanonce sfc /scanboot sfc /revert sfc /purgecache sfc /cachesize=x sysdm.cpl taskmgr telnet nusrmgr.cpl utilman firewall.cpl magnify wmimgmt.msc syskey wupdmgr tourstart write |
Rearm Windows from Evaluation Period
If your 30 days trial is about to expire, I found a good way to rearm it. I have learned this quirk and I just wanted to share. Here's how to do that:
1) Run your CMD as Administrator.
2) Type slmgr.vbs –rearm
3) Restart your system and smile. :P
If the above command didn't work, specially if you're using Windows 7, try:
slmgr.vbs /rearm
Have Fun! :)
1) Run your CMD as Administrator.
2) Type slmgr.vbs –rearm
3) Restart your system and smile. :P
If the above command didn't work, specially if you're using Windows 7, try:
slmgr.vbs /rearm
Have Fun! :)
Dynamic Versus Static IP Addresses
Here we describe dynamic and static IP addresses, and discuss the advantages and disadvantages associated with each type.
A.1 Dynamic IP (DHCP) Address
Each time a DHCP client boots, it sends out a DHCP discover message. All DHCP servers answer (in practice only one is set to do this at Fermilab; in the future possibly a second will be added for redundancy) with an offer message that includes an address which is available to the client.
The client machine typically repeats the discover message several times to make sure it hears from all the servers, then eventually chooses the "best" server, where what is "best" is up to the client. It may mean that the addresses the DHCP server has available offer the longest lease time. Or the client might prefer a server that provides WINS servers over one that doesn't (the WINS servers keep track of all the clients' and servers' latest dynamic IP addresses).
The currently active DHCP server is configured by hand to handle and reserve IP addresses and the IP configuration information that goes with them. Addresses are made available in an order that permits a client to have the best chance of getting back the same address it was using most recently. To this end, the DHCP server offers its least recently used address to a new client.
Once the client chooses a DHCP server, it "officially" requests the IP address and configuration information. In addition to this, it receives a lease time for the address. This lease time is not absolute. As long as it is running, the client machine requests renewal of the lease. This is invisible to the user, although there is a mechanism for the user to release the address early ( ipconfig/release from the command prompt).
Client machines in the NT domain typically access multiple file servers, print servers, and so on. The clients as well as the servers may change their IP addresses. Via the WINS servers, this is transparent to the user.
Advantages
1. All the IP configuration information gets automatically configured for your client machine by the DHCP server.
2. If you move your client machine to a different subnet, the client will send out its discover message at boot time and work as usual. However, when you first boot up there you will not be able to get back the IP address you had at your previous location regardless of how little time has passed.
Disadvantage
Your machine name does not change when you get a new IP address. The DNS (Domain Name System) name is associated with your IP address and therefore does change. This only presents a problem if other clients try to access your machine by its DNS name. One example is ftp . If a Windows machine is set up as an ftp server, then its ftp server name (which uses the DNS name) changes every time the IP address does. If you need to use your Windows machine as an ftp server (or as a Web server), request a static IP address rather than a dynamic one.
A.2 Static IP Address
Advantages
1. The two names (Windows name and DNS name) are the same as each other, and neither ever changes. Other clients may therefore reliably access your machine by its DNS name (e.g., using ftp ).
2. With a static address your machine is more easily accessible by non-Windows internet services. This is not a significant advantage as people seldom telnet to their Windows PC.
Disadvantages
1. You can't move your machine to a different subnet and expect it to work. You need to reconfigure it.
2. If machines come and go, or are up only some of the time, static assignments are less resource-efficient (where the resource in question is the IP address itself).
SOURCE: http://www.fnal.gov/docs/pc/nt_at_fermilab/html/current/ntguide.b.html
A.1 Dynamic IP (DHCP) Address
Each time a DHCP client boots, it sends out a DHCP discover message. All DHCP servers answer (in practice only one is set to do this at Fermilab; in the future possibly a second will be added for redundancy) with an offer message that includes an address which is available to the client.
The client machine typically repeats the discover message several times to make sure it hears from all the servers, then eventually chooses the "best" server, where what is "best" is up to the client. It may mean that the addresses the DHCP server has available offer the longest lease time. Or the client might prefer a server that provides WINS servers over one that doesn't (the WINS servers keep track of all the clients' and servers' latest dynamic IP addresses).
The currently active DHCP server is configured by hand to handle and reserve IP addresses and the IP configuration information that goes with them. Addresses are made available in an order that permits a client to have the best chance of getting back the same address it was using most recently. To this end, the DHCP server offers its least recently used address to a new client.
Once the client chooses a DHCP server, it "officially" requests the IP address and configuration information. In addition to this, it receives a lease time for the address. This lease time is not absolute. As long as it is running, the client machine requests renewal of the lease. This is invisible to the user, although there is a mechanism for the user to release the address early ( ipconfig/release from the command prompt).
Client machines in the NT domain typically access multiple file servers, print servers, and so on. The clients as well as the servers may change their IP addresses. Via the WINS servers, this is transparent to the user.
Advantages
1. All the IP configuration information gets automatically configured for your client machine by the DHCP server.
2. If you move your client machine to a different subnet, the client will send out its discover message at boot time and work as usual. However, when you first boot up there you will not be able to get back the IP address you had at your previous location regardless of how little time has passed.
Disadvantage
Your machine name does not change when you get a new IP address. The DNS (Domain Name System) name is associated with your IP address and therefore does change. This only presents a problem if other clients try to access your machine by its DNS name. One example is ftp . If a Windows machine is set up as an ftp server, then its ftp server name (which uses the DNS name) changes every time the IP address does. If you need to use your Windows machine as an ftp server (or as a Web server), request a static IP address rather than a dynamic one.
A.2 Static IP Address
Advantages
1. The two names (Windows name and DNS name) are the same as each other, and neither ever changes. Other clients may therefore reliably access your machine by its DNS name (e.g., using ftp ).
2. With a static address your machine is more easily accessible by non-Windows internet services. This is not a significant advantage as people seldom telnet to their Windows PC.
Disadvantages
1. You can't move your machine to a different subnet and expect it to work. You need to reconfigure it.
2. If machines come and go, or are up only some of the time, static assignments are less resource-efficient (where the resource in question is the IP address itself).
SOURCE: http://www.fnal.gov/docs/pc/nt_at_fermilab/html/current/ntguide.b.html
Subscribe to:
Posts (Atom)