DHCP in Windows XP
-
Here's the layout. I have a notebook and a PC. I want to easily connect each other directly with an Ethernet cord and use their machine names. At the moment, I'm restricted to using IP addresses set by myself (which can be a headache!) Is there a way to make my PC act as a DHCP server? The solution by Microsoft involves editing the registry file but I want to try other paths before going to that extreme. My thanks in advance.
-
Here's the layout. I have a notebook and a PC. I want to easily connect each other directly with an Ethernet cord and use their machine names. At the moment, I'm restricted to using IP addresses set by myself (which can be a headache!) Is there a way to make my PC act as a DHCP server? The solution by Microsoft involves editing the registry file but I want to try other paths before going to that extreme. My thanks in advance.
I don't know if there are solutions that avoid using additional software, but in the past I have successfully used this tiny software: Static DHCP Server http://ruttkamp.gmxhome.de/dhcpsrv/dhcpsrv.htm[^].
Luca The Price of Freedom is Eternal Vigilance.
-
I don't know if there are solutions that avoid using additional software, but in the past I have successfully used this tiny software: Static DHCP Server http://ruttkamp.gmxhome.de/dhcpsrv/dhcpsrv.htm[^].
Luca The Price of Freedom is Eternal Vigilance.
I don't mind having to use additional software, I just don't want to touch the registry.
-
Here's the layout. I have a notebook and a PC. I want to easily connect each other directly with an Ethernet cord and use their machine names. At the moment, I'm restricted to using IP addresses set by myself (which can be a headache!) Is there a way to make my PC act as a DHCP server? The solution by Microsoft involves editing the registry file but I want to try other paths before going to that extreme. My thanks in advance.
If I recall correctly... If there is no DHCP server detected, the machine will be assigned a unique address, within a special MS address range. Haven't used it "in anger", but I do recall having an address when I was off the network (not just the regular address sticking around either). [EDIT] Found the link http://support.microsoft.com/kb/220874[^] [/EDIT] Brad
-
Here's the layout. I have a notebook and a PC. I want to easily connect each other directly with an Ethernet cord and use their machine names. At the moment, I'm restricted to using IP addresses set by myself (which can be a headache!) Is there a way to make my PC act as a DHCP server? The solution by Microsoft involves editing the registry file but I want to try other paths before going to that extreme. My thanks in advance.
Try Enabling NetBIOS over TCP/IP. It allows the computer to broadcast its computer name over the network, so it can be resolved. By default, NetBIOS is only enabled for dynamically assigned addresses, but not allowed for static IPs. Go to your network properties, TCP/IP properties, and in the WINS tab in advanced settings, you will find three radio buttons.
Luis Alonso Ramos Intelectix Chihuahua, Mexico
Not much here: My CP Blog!
-
Here's the layout. I have a notebook and a PC. I want to easily connect each other directly with an Ethernet cord and use their machine names. At the moment, I'm restricted to using IP addresses set by myself (which can be a headache!) Is there a way to make my PC act as a DHCP server? The solution by Microsoft involves editing the registry file but I want to try other paths before going to that extreme. My thanks in advance.
You can tuyrn on IP autoconfiguration whic is easier. Each stack will assign itself an address from a certain range which aere unikely to clash. Google for autoconfigured IP addreses, it'll tell you where to put the reg values.
Truth is the subjection of reality to an individuals perception
-
Try Enabling NetBIOS over TCP/IP. It allows the computer to broadcast its computer name over the network, so it can be resolved. By default, NetBIOS is only enabled for dynamically assigned addresses, but not allowed for static IPs. Go to your network properties, TCP/IP properties, and in the WINS tab in advanced settings, you will find three radio buttons.
Luis Alonso Ramos Intelectix Chihuahua, Mexico
Not much here: My CP Blog!
-
I don't mind having to use additional software, I just don't want to touch the registry.
WiseHacker wrote:
I don't mind having to use additional software, I just don't want to touch the registry
You would rather install third party SW than turn on a micrtisift feature called autoIP address configuration? I wouldnt. And dont be scared of the registry, it is nothing really.
Truth is the subjection of reality to an individuals perception
-
Here's the layout. I have a notebook and a PC. I want to easily connect each other directly with an Ethernet cord and use their machine names. At the moment, I'm restricted to using IP addresses set by myself (which can be a headache!) Is there a way to make my PC act as a DHCP server? The solution by Microsoft involves editing the registry file but I want to try other paths before going to that extreme. My thanks in advance.
Maintaining separate IP addresses for 2 machines is hardly a headache! XP can provide its own headaches if left to work things out on its own. Don't forget to enable file sharing (and share something) or you won't be able to do much. If you are connecting the machines directly with a cable, use a crossover cable and assign the machines addresses like 192.168.0.100 and 192.168.0.101. If you are connecting both machines to a router use a regular cable and set the gateway address to that of the router and make sure you assign the machines addresses in the same range. (e.g. LinkSys is usually 192.168.1.###, D-Link is usually 192.168.0.###) Garry
-
WiseHacker wrote:
I don't mind having to use additional software, I just don't want to touch the registry
You would rather install third party SW than turn on a micrtisift feature called autoIP address configuration? I wouldnt. And dont be scared of the registry, it is nothing really.
Truth is the subjection of reality to an individuals perception
I messed up my machine one tampering with it and had to reformat. That's how dangerous it is.
-
Maintaining separate IP addresses for 2 machines is hardly a headache! XP can provide its own headaches if left to work things out on its own. Don't forget to enable file sharing (and share something) or you won't be able to do much. If you are connecting the machines directly with a cable, use a crossover cable and assign the machines addresses like 192.168.0.100 and 192.168.0.101. If you are connecting both machines to a router use a regular cable and set the gateway address to that of the router and make sure you assign the machines addresses in the same range. (e.g. LinkSys is usually 192.168.1.###, D-Link is usually 192.168.0.###) Garry
You are missing the point, I want to avoid using IPs. What's the point in naming a machine if you can't use the name? After all they didn't invent hostnames just for kicks. At the moment, I've gone wireless thanks to an AirPort and it has made life so much easier thanks to it's built in DHCP.
ggallen wrote:
If you are connecting the machines directly with a cable, use a crossover cable and assign the machines addresses like 192.168.0.100 and 192.168.0.101.
What's a cross over cable, anyway? I've never touched the underside of networks. At the moment, I'm using a Ethernet cable (that blue thing).
-
If I recall correctly... If there is no DHCP server detected, the machine will be assigned a unique address, within a special MS address range. Haven't used it "in anger", but I do recall having an address when I was off the network (not just the regular address sticking around either). [EDIT] Found the link http://support.microsoft.com/kb/220874[^] [/EDIT] Brad
Brad Bruce wrote:
Found the link http://support.microsoft.com/kb/220874
I found that too. Is it really safe to turn that function on? I use my PC as backup storage for my PhD work.
-
You are missing the point, I want to avoid using IPs. What's the point in naming a machine if you can't use the name? After all they didn't invent hostnames just for kicks. At the moment, I've gone wireless thanks to an AirPort and it has made life so much easier thanks to it's built in DHCP.
ggallen wrote:
If you are connecting the machines directly with a cable, use a crossover cable and assign the machines addresses like 192.168.0.100 and 192.168.0.101.
What's a cross over cable, anyway? I've never touched the underside of networks. At the moment, I'm using a Ethernet cable (that blue thing).
The fact that you set a fixed IP address doesn't mean that you can't then just forget about it and access the machine by name. It DOES, however, make troubleshooting easier. If you know the addresses of the network components then you can attempt to access them directly. e.g If you ping an address and it fails then either the device doesn't exist or you have a TCP/IP problem. If you ping 'Sam' and it fails it may just mean that your DHCP server is unavailable. The Airport will solve your problem just fine... setting one of your machines to be the DHCP server would have resulted in complaints from the other one every time the 'server' wasn't booted first. A crossover cable is one of those 'blue things' with a couple of the wires reversed and is only necessary if you are connecting 2 machines directly. The reasons for this you probably don't want to know! Like most things about computers, if it's working then who cares how it is setup but if it's NOT working then knowing something about the situation may save you money. Garry
-
The fact that you set a fixed IP address doesn't mean that you can't then just forget about it and access the machine by name. It DOES, however, make troubleshooting easier. If you know the addresses of the network components then you can attempt to access them directly. e.g If you ping an address and it fails then either the device doesn't exist or you have a TCP/IP problem. If you ping 'Sam' and it fails it may just mean that your DHCP server is unavailable. The Airport will solve your problem just fine... setting one of your machines to be the DHCP server would have resulted in complaints from the other one every time the 'server' wasn't booted first. A crossover cable is one of those 'blue things' with a couple of the wires reversed and is only necessary if you are connecting 2 machines directly. The reasons for this you probably don't want to know! Like most things about computers, if it's working then who cares how it is setup but if it's NOT working then knowing something about the situation may save you money. Garry
ggallen wrote:
The fact that you set a fixed IP address doesn't mean that you can't then just forget about it and access the machine by name.
It's still harder to type an IP in than the name.
ggallen wrote:
The Airport will solve your problem just fine
Yes, but it only runs ar 56 MBit/s while I have Gigabit LANs in both my Notebook and desktop machines. I sometimes have gigabytes files to tranfer as I use virtual machines, hence the need for the cable.
ggallen wrote:
setting one of your machines to be the DHCP server would have resulted in complaints from the other one every time the 'server' wasn't booted first
Not a problem with me as I always turn the desktop machine on first.
-
I messed up my machine one tampering with it and had to reformat. That's how dangerous it is.