Discussion Locked

using nat

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I do want to use nat. I have a win2000 setup up as a workgroup and networked to a win98.I thought I set up nat correctly, but it seems not to be working. I do want the win98 to be able to dial out on the win2000 and have internet access.How should I set up the win98 to see the win2000 and to have it dialup? Is there any way to check to see if I have nat setup correctly.I have a internal modem hooked up to the win2000. My isp is a free based internet access(bluelight).Any suggestions would be helpful.If I could correspond w/someone through their e-mail it would be a great help...I'm stumpped and I do need to have this implemented asap. Thank's in advance.......... But I do want to use nat for this.

8 replies

by ebob

Doesn't ICS (MS' Internet Connection Sharing) do this? I thought so.

The basic steps being to setup ICS on your "gateway" (your Win2K box in this case). Then setup your Win98 box as an ICS client. You may have to cut a setup diskette on your Win2K to get the client onto Win98. I did a quick search at MS (not MSN) and came up with these links (you may need to remove the spaces...):

http://support.microsoft.com/
support/kb/articles/q234/8/15.asp
http://www.microsoft.com/ ISN/Columnists/P57150.asp

by msfiroudis

Thank,s ebob,
Still using nat..
That was a very helpful article. But I still have a bit of a problem. When I enter static route what ip adress I'm I putting in there.
My isp's?.. I have a modem hooked up and do not there ip address, I imagine it's different every time.Also to get the win98 to get the internet through the win2000. How would I set up the win98 machine..
Thank's again

by ben

I have NAT working fine with Win2K, Win98 and MacOS clients all connecting. If you are talking Win2K Pro then you may have a problem (does Win2K ICS support 98 clients?), but if you have a Win2K server I suggest you check:

DHCP: Recommend you use it, with the address pool of 192.168.0.100-200 with the server op IP address 192.168.0.1 Configure the default gateway for each machine to be the server (192.168.0.1) and the subnet mask of everything to be 255.255.255.0 (if you don't do this some packets will remain in the local net and you get some wierd half-cock access!)

NAT: To be honest, its far simpler to use the wizard to set up the service. Just stop the service from the "Routing and Remote Access" console (thereby clearing the configuration), then choose "Configure Routing and Remote Access" and say you want to allow the workgroup to access the internet with NAT, choose the interface (modem) make it dial on demand and set the credentials... bob's yer uncle!

Clients: Obviously all need to be configured to use DHCP, with the server address configured to be 192.168.0.1 again.

If you are doing this entirely through Win2K pro, then it may be possible to manually set all the client IP addresses as defined above and still get it to work. Does NAT provide a cut down DHCP itself in Win2K Pro? Let me know.

It worked for me!! Feel free to E-Mail me (ben@2020casting.com) if you're still stuck, and I'll try to help.

Ben.

by ben

I have NAT working fine with Win2K, Win98 and MacOS clients all connecting. If you are talking Win2K Pro then you may have a problem (does Win2K ICS support 98 clients?), but if you have a Win2K server I suggest you check:

DHCP: Recommend you use it, with the address pool of 192.168.0.100-200 with the server op IP address 192.168.0.1 Configure the default gateway for each machine to be the server (192.168.0.1) and the subnet mask of everything to be 255.255.255.0 (if you don't do this some packets will remain in the local net and you get some wierd half-cock access!)

NAT: To be honest, its far simpler to use the wizard to set up the service. Just stop the service from the "Routing and Remote Access" console (thereby clearing the configuration), then choose "Configure Routing and Remote Access" and say you want to allow the workgroup to access the internet with NAT, choose the interface (modem) make it dial on demand and set the credentials... bob's yer uncle!

Clients: Obviously all need to be configured to use DHCP, with the server address configured to be 192.168.0.1 again.

If you are doing this entirely through Win2K pro, then it may be possible to manually set all the client IP addresses as defined above and still get it to work. Does NAT provide a cut down DHCP itself in Win2K Pro? Let me know.

It worked for me!! Feel free to E-Mail me (ben@2020casting.com) if you're still stuck, and I'll try to help.

Ben.

This discussion is closed to new replies.