Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can a standard XP Pro be used as a router? 1
- Thread starter miggyal
- Start date
Please clarify what you intend to do.
I believe you mean a "server". If so, it is possible. You can install you're multi-user programs on it and give other users access.
You can also use a hub and create a peer-to-peer network so you can share data, disk space, and printers. You don't need a router for that.
hope this helps.
Aloha,
cg
I believe you mean a "server". If so, it is possible. You can install you're multi-user programs on it and give other users access.
You can also use a hub and create a peer-to-peer network so you can share data, disk space, and printers. You don't need a router for that.
hope this helps.
Aloha,
cg
- Thread starter
- #3
I was trying to set up a standalone XP machine with 2 network cards in it, so I could give them different IP addresses for fault finding etc...
As I am on a network and are trying to do stuff with remote management, but could do with making the network think that I am trying to access it from outside the network, if you know what I mean?
As I am on a network and are trying to do stuff with remote management, but could do with making the network think that I am trying to access it from outside the network, if you know what I mean?
Standalone/On a Network?
Okay, I'm going to lay out what I think you're trying to do as I'm not positive with this.
You're running an XP system, that isn't joined to a domain or tree of any kind. However, you do have a current network connection attached to this system.
What you're trying to do, is to set this system up with an IP address that is external to the firewall so that you can test accessing the system from an external network (IE. Home, another office, etc...).
If this is the case there are several ways to test this out, but you'll want to move this disucssion to a networking forum, as all of them will involve setting up different network zones, router configuration, and some firewall tweaking.
The easiest way to do this is to take yourself off the network and use a DUN connection to the internet and test it from a truly external IP.
As for the two IP's, one for each NIC, it can be done. You can leave them dynamic to attempt to obtain their own address or you can static them. However, giving one an IP external to your current networking zone and an IP current to your internal network will not allow you to adequately test anything. Your system would act as a go between for itself and any programs that you wished to test.
Okay, I'm going to lay out what I think you're trying to do as I'm not positive with this.
You're running an XP system, that isn't joined to a domain or tree of any kind. However, you do have a current network connection attached to this system.
What you're trying to do, is to set this system up with an IP address that is external to the firewall so that you can test accessing the system from an external network (IE. Home, another office, etc...).
If this is the case there are several ways to test this out, but you'll want to move this disucssion to a networking forum, as all of them will involve setting up different network zones, router configuration, and some firewall tweaking.
The easiest way to do this is to take yourself off the network and use a DUN connection to the internet and test it from a truly external IP.
As for the two IP's, one for each NIC, it can be done. You can leave them dynamic to attempt to obtain their own address or you can static them. However, giving one an IP external to your current networking zone and an IP current to your internal network will not allow you to adequately test anything. Your system would act as a go between for itself and any programs that you wished to test.
I believe the Server products are the only ones that do routing, not Windows 2000 or XP.
If you are trying to set up a dedicated router and have a spare hooptie machine around, give coyote linux a shot.
You download the program to a Windows machine, then all you need to do is put you your settings in and tell it what brand/model nic's you have. Say go, and it creates a boot floppy. Put that in your machine and set your BIOS to boot to floppy. The program loads and if you put the correct LAN/WAN/NIC info in, you have a router.
If you are trying to set up a dedicated router and have a spare hooptie machine around, give coyote linux a shot.
You download the program to a Windows machine, then all you need to do is put you your settings in and tell it what brand/model nic's you have. Say go, and it creates a boot floppy. Put that in your machine and set your BIOS to boot to floppy. The program loads and if you put the correct LAN/WAN/NIC info in, you have a router.
Yep. Hooptie is some sort of old machine.
This is the system requirements from Coyote's web site.
486DX/25 or better processor
12Mb RAM
1.44Mb floppy drive
Network interface card for LAN
Network interface card or serial dialup modem for Internet connection
VGA display adapter
That is a hooptie in my book!
You don't have to have a hard drive in the machine.
Jamie
This is the system requirements from Coyote's web site.
486DX/25 or better processor
12Mb RAM
1.44Mb floppy drive
Network interface card for LAN
Network interface card or serial dialup modem for Internet connection
VGA display adapter
That is a hooptie in my book!
You don't have to have a hard drive in the machine.
Jamie
-
1
- #11
- Thread starter
- #13
- Status
Similar threads
- Locked
- Question
