I pulled the infor below out of the EVOX install tutorial, above in this forum. When I used it I didn't pay much attention to the FTP section. After going back and reading it today, it seems incorrect. Or possibly the way it is used in EVOX is incorrect.
Usually when dealing with an IP address, static means "unchanging" and assigned by an administrator. So I would think that if you set the Static value to Yes, then you would need to manually set the IP address, and subnet mask, as with any other network device.
When Static is set to NO, I would assume that means that the device is looking for a DHCP server to lease and IP address from. Which is correct.
Which means if you are using a home Router/Switch combo that is acting as a DHCP server "handing out IP addresses" you would want to set static to NO.
Where as if you are using a HUB, or a crossover cable, you would want to set this to YES, and configure it manaually, since there will be no DHCP server available.
So it this a typo? Or is the way "static" is used in the evox.ini wrong?
[font=verdana, arial, helvetica] When I open my evox.ini file, under the [Network] heading this is what I see:
[Network]
SetupNetwork = Yes
StaticIP = NO
Ip = 192.168.0.50
Subnetmask = 255.255.255.0
Defaultgateway = 192.168.100.1
DNS1 = 0.0.0.0
DNS2 = 0.0.0.0
The settings that you need to make sure are configured properly are the following:
You definitely want to set "SetupNetwork = Yes", this tells Evox to configure your Xbox for networking.
Next you will need to configure "StaticIP = Yes" if you are using a router to connect your Xbox to your PC, or "StaticIP = No" if you are using a crossover cable, or hub to connect your Xbox to your PC.
Finally, if you set StaticIP = No, then you will need to specify the ip address assigned to your Xbox. You should be able to figure this out based on your computer?s network configuration. For more information on Xbox networking, please see my tutorial on how to setup an Xbox network. In my case, I use a Linksys router to connect my Xbox and my computer. Therefore, I have "StaticIP = Yes". Your case may be different. [/font]
Usually when dealing with an IP address, static means "unchanging" and assigned by an administrator. So I would think that if you set the Static value to Yes, then you would need to manually set the IP address, and subnet mask, as with any other network device.
When Static is set to NO, I would assume that means that the device is looking for a DHCP server to lease and IP address from. Which is correct.
Which means if you are using a home Router/Switch combo that is acting as a DHCP server "handing out IP addresses" you would want to set static to NO.
Where as if you are using a HUB, or a crossover cable, you would want to set this to YES, and configure it manaually, since there will be no DHCP server available.
So it this a typo? Or is the way "static" is used in the evox.ini wrong?
[font=verdana, arial, helvetica] When I open my evox.ini file, under the [Network] heading this is what I see:
[Network]
SetupNetwork = Yes
StaticIP = NO
Ip = 192.168.0.50
Subnetmask = 255.255.255.0
Defaultgateway = 192.168.100.1
DNS1 = 0.0.0.0
DNS2 = 0.0.0.0
The settings that you need to make sure are configured properly are the following:
You definitely want to set "SetupNetwork = Yes", this tells Evox to configure your Xbox for networking.
Next you will need to configure "StaticIP = Yes" if you are using a router to connect your Xbox to your PC, or "StaticIP = No" if you are using a crossover cable, or hub to connect your Xbox to your PC.
Finally, if you set StaticIP = No, then you will need to specify the ip address assigned to your Xbox. You should be able to figure this out based on your computer?s network configuration. For more information on Xbox networking, please see my tutorial on how to setup an Xbox network. In my case, I use a Linksys router to connect my Xbox and my computer. Therefore, I have "StaticIP = Yes". Your case may be different. [/font]