|
Home > Archive > 70-210 > September 2002 > Spid's Tue (9/17) Win2K Pro. QoD
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Spid's Tue (9/17) Win2K Pro. QoD
|
|
|
| Here's an easy one...
I've got 8 Windows 2000 Professional systems. They are all networked together in a peer-to-peer workgroup environment via a single Hub and they are all on the same network.
I just got my own fancy dancy cable modem, and install a second NIC in one of the Windows 2000 systems. I hook up the cable modem to that system. I'm having a blast surfin' the 'Net and sending emails at super fast broadband speeds, but the other systems are sad because they currently are unable to join in on the fun. 
The other systems would like to be able to access the Internet and send emails too.
What should I do to get all the systems hooked up to the Internet, making them happy again, with the least amount of administrative effort? (Choose all that apply) 
A. Configure TCP/IP on all of the systems to obtain an IP address automatically.
B. Configure TCP/IP on each system to use a static IP address.
C. Disable on-demand dialing on the computer system that has 2 NIC's
D. Enable ICS on the NIC that is connect to the cable modem.
See you tommorrow for the answer! | |
| denis_baribeau 2002-09-17, 7:56 am |
| That would be
B,D | |
|
|
| enforcer 2002-09-17, 9:03 am |
| in a very loud voice with plenty of DB i will got for B and D | |
| Deja-vue 2002-09-17, 9:18 am |
| Tricky...
My Answer is A-C Reason:
If the Internet connection to be shared is a Dial-up connection, "on demand dialing" must be checked to give one ore more users on the network access to the Internet.
In Spid's case, it is a Cabe-modem, which is a "always-on" connection.
Therefore, "on demand dialing" should be unchecked.
sorry, i had to do some editing.... | |
|
| Hmmmm.... ICS has it's own DHCP allocator, you would still opt to set the addresses as static on the clients?
If you do that, what IP address range would you use based on the IP address the network interface that ICS is enabled on receives? And what would be your default gateway?
Just throwing this out to spark some conversation | |
| enforcer 2002-09-17, 9:28 am |
| and i now change my answer, because i did not read the question properly
AD  | |
| Deja-vue 2002-09-17, 9:43 am |
| Yes, M$ says:
"You should not use this feature on a computer running DNS server or DHCP server or a Windows domain controller. When you enable ICS, the network adapter connected to the home or small office network is given a new static IP address configuration. Existing TCP/IP connections on the CS computer are lost and need to be re-established. "
The default Gateway for the clients should be the IP Address of the ICS enabled Interface of the multi-homed Machine. | |
| Teck Shark 2002-09-17, 9:43 am |
| Good point Spid. The IP address of the ICS host would be your default gateway. I would have said A & D because the question said to perform this with the least amount of administrative overhead, and configuring manual IP's takes more work than necessary.
Actually the best way to do this would be to buy a cable/dsl router, and hook your cable modem to the router. Then hook the router right into the hub. Then all you have to do is enable DHCP on the router & configure each PC to obtain an IP automatically. Simple, easy to do, and then you don't have to mess with ICS.  | |
| Deja-vue 2002-09-17, 9:48 am |
| I should really start reading the Questions slowly and then post.
Think before you post.... how true.
Anyways.... ICS sucks!
NAT rules! | |
| Teck Shark 2002-09-17, 9:50 am |
| quote:
Originally posted by Deja-vue
Yes, M$ says:
"You should not use this feature on a computer running DNS server or DHCP server or a Windows domain controller. When you enable ICS, the network adapter connected to the home or small office network is given a new static IP address configuration. Existing TCP/IP connections on the CS computer are lost and need to be re-established. "
The default Gateway for the clients should be the IP Address of the ICS enabled Interface of the multi-homed Machine.
Good point Deja, although this only applies to a Server environment where you have a domain controller(s) & an existing Windows DNS or DHCP server. But we're dealing with a peer-to-peer workgroup environment in this case, where there is no Windows DHCP server issuing IP's, so that doesn't apply.
Oooops! Sorry, I see you already corrected yourself Deja... | |
|
| quote:
Originally posted by Deja-vue
Anyways.... ICS sucks!
NAT rules!
Can't argue with that! | |
| NetChild1985 2002-09-17, 10:30 am |
| Guys, I'm going with "A" and "D" on this question! | |
| Deja-vue 2002-09-17, 11:07 am |
| How come no-one answers C?
On demand dialing must be unchecked, because a Cable-modem is used instead of a dial-up.
Spid, you really got us on this one, because in the real world, no-one is using ICS anymore.
| |
| Teck Shark 2002-09-17, 12:54 pm |
| quote:
Originally posted by Deja-vue
How come no-one answers C?
On demand dialing must be unchecked, because a Cable-modem is used instead of a dial-up.
Spid, you really got us on this one, because in the real world, no-one is using ICS anymore.
Deja,
On-Demand Dialing isn't even an option for a DSL/cable modem based connection.
http://www.practicallynetworked.com/sharing/ics/images_ics/ICS2KLAN4.gif | |
| denis_baribeau 2002-09-17, 1:42 pm |
| I use ICS at my place I find it easy to setup ,it auto set 192.168.0.1 has gateway and than it want to create the stupid diskette to walk to the other clients ,myself find it easier just to set static ip .0.2,.3,.4,.5 ,mask ,default gateway,reboot and all is working .possibly that is what that diskette is suppose to do but I end up with the same result.
Has for least administration is concerned than A,D probably is if you make the diskette.
| |
| Teck Shark 2002-09-17, 2:35 pm |
| quote:
Originally posted by denis_baribeau
I use ICS at my place I find it easy to setup ,it auto set 192.168.0.1 has gateway and than it want to create the stupid diskette to walk to the other clients ,myself find it easier just to set static ip .0.2,.3,.4,.5 ,mask ,default gateway,reboot and all is working .possibly that is what that diskette is suppose to do but I end up with the same result.
Has for least administration is concerned than A,D probably is if you make the diskette.
Denis,
Windows 2000 ICS does not generate
a "Client Configuration Disk". That's only used when a Windows 95/98/ME PC is configured as the Host. | |
| denis_baribeau 2002-09-17, 3:09 pm |
| Haaaaa ! well that's for what ,That's how it is running here. and more likely that
A,D are the right step since this forum/thread is base on win2000. LOL
Thanks Teck Shark .
PS: My setup does suck big time,but does the job for everyone.I know the draw back. | |
| rafman 2002-09-17, 4:07 pm |
| Deffinitely A & D would be correct. I know this as I recently setup thi config.
~RafMan | |
| Deja-vue 2002-09-17, 5:03 pm |
| *******I suck******* | |
| chunder 2002-09-17, 8:28 pm |
| ah drat.. i knew it all along but too late to the punch.. i lose.
but yeah, i'd like to enter an answer for A and D. | |
| namrak 2002-09-17, 10:43 pm |
| Had to check back again to see how the question was going down. Turns out I would have been right (A) and (D), but differences in perspectives were brought up which made me question myself. They always say, go with your first hunch! | |
| enforcer 2002-09-18, 3:01 am |
| quote:
Originally posted by namrak
Had to check back again to see how the question was going down. Turns out I would have been right (A) and (D), but differences in perspectives were brought up which made me question myself. They always say, go with your first hunch!
that's what they said to esmerelda | |
| robertmillar 2002-09-18, 4:20 am |
| A & D | |
|
| quote:
Originally posted by Spid
Here's an easy one...
I've got 8 Windows 2000 Professional systems. They are all networked together in a peer-to-peer workgroup environment via a single Hub and they are all on the same network.
I just got my own fancy dancy cable modem, and install a second NIC in one of the Windows 2000 systems. I hook up the cable modem to that system. I'm having a blast surfin' the 'Net and sending emails at super fast broadband speeds, but the other systems are sad because they currently are unable to join in on the fun.
The other systems would like to be able to access the Internet and send emails too.
What should I do to get all the systems hooked up to the Internet, making them happy again, with the least amount of administrative effort? (Choose all that apply)
A. Configure TCP/IP on all of the systems to obtain an IP address automatically.
B. Configure TCP/IP on each system to use a static IP address.
C. Disable on-demand dialing on the computer system that has 2 NIC's
D. Enable ICS on the NIC that is connect to the cable modem.
See you tommorrow for the answer!
And the answer is.... A,D
Tech Shark hit it right on the head....
quote:
Originally posted by Tech Shark
....the question said to perform this with the least amount of administrative overhead, and configuring manual IP's takes more work than necessary.
ICS has it's own DHCP allocator that distributes IP addresses to clients in the scope 192.168.0.0/24 subnetwork. The interface (NIC in this case) that is connected to the cable modem will be the one that you enable ICS on and it will assign itself the IP address of 192.168.0.1/24 (which will be the default gateway on the client pc's). Clients should be configured to obtain their IP addresses automatically.
Could you use static addresses? Absolutely. But it would take more "administrative effort". Also, in using a cable modem or DSL modem, On-Demand dialing is not shown as an option. Thanks Tech Shark for the screen-shot.
This question got some good debate going, I enjoyed reading it. Nice job eveyone! |
|
|
|
|