ICS-Problem

[Guest]

Just set up W2K-Server and tried to start the Internet connection sharing.
Shared Connection is ISDN and the Network is Fast Ethernet.
I did everything, the HELP says but it just don't work.
The Server's IP is fixed 192.168.0.1 and the Area for the others is 0.2 - 0.10.
The only other machine at the moment is a W2K Pro. The Network connection works fine.
The Systems Report tells me that the DNS can't find the 192.168.0.1 which should be the server (running DNS) itself.
Maybe here's the problem.
The IE-Options on the Workstation (Proxies) is all marked off. But it also doesn't work with some marked on 🙁
I tried to find a solution now for 3 Days and I just gave up.
Please help me!

 

[Guest]

Based from what you have said, it sounds like you are running a DHCP server as well as the DNS server. First off, ICS shouldnt even be used with these services. The actual reason its not working is probably because you gave it (server)the .1 IP address. ICS should not even be used in conjunction with static IPs to begin with. That and the fact that your client is probably trying to get the same IP might give you additional problems. ICS is just meant for windows peer-to-peer networks, not server-client environments. I'd suggest you don't even bother with it. Install Routing and Remote services on your server instead. NAT works very well for windows 2000, and you could aslo try to setup your server as an actual router, but NAT is easier to configure. Not only that, but with NAT you'd be able to use your DHCP scope properly. Assigning a DHCP scope when you are using ICS doesnt make much sense, and as you've seen, probably won't even work.
Bottom line, disable ICS and configure NAT on your server.

 

[breed33]

I have to disagree with most of these statements. The ICS can work with W2K servers and static IP addresses. Under the covers ICS is using DHCP to assign IP addresses and DNS to route messages.

I have two W2K servers set up at home. One is my internet gateway over DSL. I have two NICs in the server and all machines connect to it via DHCP to cruise the net.

ICS is a NAT application. It is a software bridge that connects one network to another. The ICS will work fine for a server client relationship. At home my client (server) logs into my firewall server which is also a Domain Controller (with AD setup). The ICS stuff is hidden well beneath the normal client server options. In fact the clients have no understanding of ICS and they don't need to. They just need to make a connection (DHCP is easier to configure) and they can access the internet.

When I get home from work I will run ipconfig to get all of the settings for setting up static IP addresses on your network.

You don't use any proxy stuff in IE either. It shouldn't cause this much heartache.

What did we do before we had computers?

 

[Guest]

"You should not use this feature in an existing network with other Windows 2000 Server domain controllers, DNS servers, gateways, DHCP servers, or systems configured for static IP addresses. If you are running Windows 2000 Server, and one or more of these components exist, you must use network address translation to achieve the same result.

These words are from the mouth of Microsoft. Sure, ICS is using a form of DHCP to assign IPs and such. Those features are built-in the ICS program and independant of an actual DHCP and DNS server...one reason why he probably shouldnt be using his server as an ICS host when it already has DNS and DHCP installed on it. Besides that, the DHCP allocator that is included with ICS is incredibly limited and really allows for no manual configuration.

Sure ICS is a form of NAT, but thats not what I am referring to. I'm saying he should configure NAT on his server from the Routing and Remote Access service. This is totally different from ICS, as I'm sure you know. NAT will let him assign a scope to his network, which he has already tried doing, ICS will not. There are of course many other things that NAT will allow him to do, that ICS will not.
The bottom line is this...He is using W2K Server, so why not use some of its more sophisticated features? NAT is MUCH better than ICS and he has access to it, so he should be using it. He should be using it anyways if he's running DNS and DHCP on that machine.