WinXP ICS over ADSL problem

[Inbar Shani]

Hello!

My configuration:
'Server Machine' - A compaq workstation, WinXP, two NIC: external
INTEL Ethernet adapter and an internal INTEL Ethernet adapter (if
needed, i'll post the drivers). The external card is connected to an
ALKATEL ADSL modem. The internal network card is connected to a CAJUN
device, used to connect a LAN.
'Client Machine' - Same compaq workstation, WinXP (basic installation,
didn't mess with any network configurations), one NIC for the LAN.

ADSL and ICS configuration:
Default. No DHCP, No DNS, No Bridge.
The IP of the intenral network card is the one assigned by the ICS
option of WinXP.

My situation and problem:
ADSL configured on the Server Machine works great.
Once I configure the ICS (Internet Connection Sharing), the Client
Machines recognize the Internt Gateway (the server). Once I've tried
surfing from one of the Client Machines, it works fine for a minute or
two, and then I start getting "The page can not be displayed". At the
Server Machine I realized the ADSL connection is only sending, with
almost no recieving. Once this happens, all Internet surfing will fail
(except directlly to my ISP) with the only solution disconnecting and
reconnecting (which does'nt help, as the trouble returns when the
CLient Machine start surfing again).

The more curious thing:
I have EXACTLY same Server Machine configuration at another building
(not connected to the first LAN) and it works fine. Natrually I've
tried replacing the servers and their ADSL modems (which are the same,
too), but to no avail. Can't change all Client Machines, but did
shutdown all those on the trobuled LAN except one, and that one still
affects the same trouble.

My question:
Can you HELP ME????
(or at the least, where can I get some help)

TIA,
Inbar

 

[CheshireCat]

We used to have the same problem with ics until we dropped it in favour of a
hardware firewall. I don't know what the difference is between ics and
firewall/router traffic but there was something wrong somewhere.

 

[Inbar Shani]

For anyone who's intrested - it turned out the problem is the
(internal) network switch, which was badly configured. So the XP ICS
is not to be blamed.