Can 2K Server share it's DSL connection with the LAN?

[YokyDoky]

I have a 2K Server which I would like to use as my DSL router. So it has 2 NICs, RASPPPoE installed, it makes the DSL connection real nice but when I try to share the "dial-up" connection (created by RASPPPoE) with the LAN nic it says the NIC is not present. Well, the NIC IS present and there WAS a complete network until the IP leases expired on the clients. Now they have no IP address since ICS serves as DHCP and isn't recognizing the NIC. What am I doing wrong, or am I supposed to be using RAS and NAT for this? Y. Doky - "Manager" of Systems

"Works well under constant supervision or when trapped like a rat in a pipe."

 

[shawnpd40]

Ok, it is possible I am a bit confused here but we just took a W2K server out of an ICS scenario so I know it works...one of the NICs (let's call it NIC A) should be connected to your DSL modem. NIC A should have a TCP/IP address assigned to it that is on the same network as the LAN side of your DSL (something like 192.168.1.X). Your second NIC (NIC B) should have the Obtain an IP address automatically option selected. Once this step is complete go back to NIC A and select the sharing option. You should get a dialog box that states something like this action will cause the (NIC B)to get address 192.168.0.1. blah blah blah. If you are using DHCP to assign client addresses then you need to set up your scope so the clients will are assigned addresses in the same network (192.168.0.0).

Hope this helps...and hope I didn't assume to much!

 

[LiNetTech]

Yes its very possible And to be honest with you man you will have some serious security options if you do go with the Windows 2000 box as A router , you must install routing and ras to have the use of the 2 nics (a) and (b) with in Nat you will beable to have a Private and public interface local connection 1 and 2 , with out Nat (NETWORK ADDRESS TRANSLATION ) IT WILL NOT WORK AS A ROUTER ! as well as do not forget about the services you will need to configure with in DHCP like to say ! #003 router and #005 name servers wich would be your dns servers from your isp
then get yourself a small hub or enough of a hub to set up as many pcs you need to hook up ! sticking with the basic 192.168.1.1 to 192.168.100 for your dchp scope it will run fine ! There is a heck of alot more to configure with this as an idea but man its worth the effort !
I hope i didn't go to far with this ................... Have Fun !

 

[LiNetTech]

One More thing the first nic could be DHCP from Isp ! But you must have the Second Nic have a static Ip so you have to create a Static route lets say 24.186.1.1 would be your ip from Isp as well as nic #2's default gateway ! then your dhcp address internal 192.168.1.101 you should have that static as well so it will be the internal pcs Gateway then you could have all the others DHCP or even make them static entries i would go STATIC ........
server Nic one DCHP
Nic two 192.168.1.101 Ip FROM STATIC SCOPE
255.255.255.0
24.186.1.1 Gateway isp ip
First pc 192.168.1.102
255.255.255.0
192.168.1.101 gateway first nic ip

 

[BOKA]

Good advices above. Just one small addition - if your ISP gives you private IP like 192.168.1.x , you MUST BE ABSOLUTELY SURE that you assign to your second NIC an IP from different network, meaning the 3-rd octet MUST be different (192.168.2.x or 192.168.10.x for example).

Good luck.

 

[LiNetTech]

Hey Boka you got that right ! Lol Thanks for informing people about that! Thanks ........ it was a late night for me ! Bascialy your windows 2000 server will do everything any run of the mill router as per say Linksys SMZ .......... its a good thing to know how to configure a router as per software with windows 2000 Linux Or what ever. but a Linksys router is a simple way to Get what you need done ! But on the other hand as you learn you could put up a win2k router after your linksys Router and set up a Dmz like to say put up a Ftp server or you Mail server then Anything past that would be for your internal network ! Have fun !

 

[YokyDoky]

Well, fellas...

I think you two are all over this thing, but your instructions aren't very clear to the average mullet like myself. Here's how RASPPPoE is configured on a multihomed Windows machine: (since Bell's PPPoE sucks)

Network Interface A: "Dial-Up Connection" (even though
it is DSL) created by RASPPPoE and Shared with Network
Interface C.

Network Interface B: NIC connected to DSL modem -
RASPPPoE enabled, TCP/IP configured to DHCP everything.

Network Interface C: NIC connected to internal LAN
with static 192.168.0.1 address.

This much I know is correct because it worked this way for over two years. So I THINK one of the above responses answers my question: this arrangement absolutely requires RAS/NAT, right? What I'm getting when I enable sharing using only ICS is a Microsoft Error saying the local LAN NIC can't be found, even though it says it is functioning normally and pings in and out succeed.

Meanwhile, I have the system functioning on a Linksys router, though there is a serious performance issue I have yet to diagnose. For example, when a client starts up, the logon time is dramatically longer than before. Same with connecting remotely using Terminal Services, or even FTPing in. Slooooo

http://wwwww.

Y. Doky - "Manager" of Systems

"Works well under constant supervision or when trapped like a rat in a pipe."

 

[LiNetTech]

Do you have a Dmz set up for the FTP Server ?