Windows 2000 Advanced Server and Internet Sharing Connection.

[epsison]

I am new with Windows 2000 Advanced Server. I have the following network setup:

1 Server running Windows 2000 Advanced Server
5 Workstations running Windows 2000 Professional.

I was successful in installing the Windows 2000 Advanced server software and connecting the workstations to the server. However, when I tried the Internet Connection sharing I wasn't successful. More so, I have problems with my network connections.

IP Address of Server : 10.10.10.2 (I think this is the default installed by the W2K wizard. It is possible to change this?)

When ICS is enabled the IP Address is changed to another IP address. I tried assigning static IP addresses to the clients. Unfortunately this didn't work.

Please help.

Thanks

 

[GlenJohnson]

Does the server access the internet? You can use fixed ip's on your pro machines and use the ip of the server for the gateway. If this isn't the problem, let us know what is. Thanks Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Since we cannot know all that there is to be known about anything,
we ought to know a little about everything."
Blaise Pascal

 

[drunkmestupid]

Hello,

This isn't my thread, but I'm going to join in... okay? LOL

I too have a single server (Win2k Server... not Advanced) with several Win2K Pro workstations.

Upon original install of the server and "Configure you server" wizard, everything worked just fine, including Internet connection sharing.

Right now I only have access to a dial up account in which I enabled Internet Connection Sharing through it's properties page. When the server was dialed in to this account, the workstations accessed it just fine. No manual IP addressing or Gateway at all... completely automatic through DHCP (and DNS?).

Now, however, the workstations cannot access the internet at all.

WHAT HAS CHANGED: Due to a drive malfunction, I had to put a newly formatted (NTFS... as was before) Windows 2000 Server installation in. I set everything up as it was before... "typical" install and "configure your server" wizard again. The domain was set up the same.

I can access the server drives from the workstations, just not the internet.

Anyone?


TIA!

 

[epsison]

Thanks for your reply Mr. Glenn Johnson. I think I have the same problem as drunkmestupid. I have a dial-up internet connection in the server. I only have a small network and I feel ICS is the most cost-effective solution for the company.

I tried what you suggested last December. I assigned static IPS to the 5 clients (192.168.0.x, etc.). What gateway will I assign to the clients? I used 192.168.0.1 since this was assigned by ICS to the server.

I also tried the Wingate solution on the server. It worked but the clients could not access their respective files in the server. (All the clients are members of the domain that I defined) More so, I encountered memory dumping problems. Although I was able to restore the last best configuration.

Do I have to re-install everything again?

Thanks in advance for your help again.

 

[GlenJohnson]

No manual IP addressing or Gateway at all... completely automatic through DHCP (and DNS?).
You have to have a gateway to get to the net. If server is accessing the net, then the server's ip address is your gateway.
More so, I encountered memory dumping problems. Although I was able to restore the last best configuration.
Look in your event viewer for problems. Also, make sure you have your server set for small memory dump, and not to automatically re-boot. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Since we cannot know all that there is to be known about anything,
we ought to know a little about everything."
Blaise Pascal

 

[Paganatron]

I have had loads of problems with ICS before. Put the tick in the box, reboot and your clients should pick up an ip address from the server. This worked for a couple of weeks before just stopping. As far as I know the server should automatically reconfigure itself to a 192.... ip range. There is a better option.
As you are running a server product, you can use RRAS. You can configure a demand dial interface. Right-click general and install Network Address Translation (NAT), assign your ethernet interface to NAT as a private interface and your dial demand interface as public. I found this to be a much more robust solution, as well as you can use any ip range and use DNS on your server which wont clash with the ICS DNS.
If you are using an adsl modem, you may have problems as this isnt seen as a hardware modem and cannot be used with RRAS. (I found this to be aparent with the Alcatel and Fujitsu modems)

Hope this helps!! )

 

[drunkmestupid]

when i made that statement, i was merely pointing out that i did not manually set it up. of course there has to be a gateway, but it was previously all done automatically.

i guess i will look more into rras... it's just frustrating when something that should be (and at one point was) simple and easy just quits with no apparent solution...

 

[epsison]

Thanks Paganatron. I also tried that before and it didn't work. I followed the step-by-step instructions given in the website. I'm not sure if I missed something. Hence, I decided to try the Wingate solution. However, I think this caused the memory dumping problem. Hence, I performed an emergency restoration and was able to restore to the last good configuration.

What I could not remove is the wingate icon in the Control Panel even though I have uninstalled the Wingate software.

I don't know if I have to reinstall the Windows 2000 Advanced Server. Any advice????