Windows 2003 Network

Jonty · Post by **Jonty** » Sun Jun 12, 2005 3:53 am

Hi all

I've recently put in a new server at work, which runs Windows 2003 Server. All the client machines are running Windows XP Pro (around 20 clients).

When I first setup the network we were using ISDN through a router (Actel or something like that), all was fine and dandy. We have just transferred over to 2MB ADSL... and I've now got some problems.

I've setup another machine to take the ADSL connection (connects using a USB Modem) and that works fine, in the Windows 2003 Server I've got 2 network cards, the are named as follows:

Server Local Area Connection (194 range)
Local Area Connection (169 range)

The first runs the network, while I want the second for a connection to the ADSL connection machine. I've tried connecting the the second card directly into the network card of the ADSL machine, but no joy. I've tried connecting the ADSL machine directly into the hub but again no joy.

Can anyone give me any clues as to what IP range the second card should be on as well as the ADSL machine (if I put the second card within the same IP range it stops people accessing the server).

Wish I'd never bothered setting this up, considering I'm not an IT bod

Any help pr advice would be grately appreciated.

Thanks

Jon

Post by **YeOldeStonecat** » Sun Jun 12, 2005 9:04 am

I'm trying to picture your setup, not clear about it yet.

So you have 1 workstation that's running as a sort of....proxy server? USB DSL modem plugged into it, and trying Windows ICS to share the connection to the NIC?

Server is multi-homed, with a NIC uplinking to the above mentioned workstation? And another NIC going to the switch for the rest of your LAN? Therefore you are trying to also run ICS on your server, for the clients to run through?

My initial thoughts are to stop here, and redesign a bit. Running double ICS...I don't see that as being reliable over the long haul. What is the possiblity of getting an ethernet DSL modem instead of the USB DSL modem? This way you could use a router for your network, leave the server single homed, keeping things simple and reliable..and protected behind a NAT firewall.

Jonty · Post by **Jonty** » Sun Jun 12, 2005 12:18 pm

Thanks for the reply , here's a quick diagram of what I mean

I tried connecting the the USB modem directly into the 2003 Server, I could get a connection but couldn't share it. It mentioned needing two cards installed so that the firewall could be activated, although when setting it up it couldn't recognise the additional card (it was working fine with ISDN through a router).

Run some diagnostics test on the card and it was fine as well as pinging the server card. Think I've gone in above my head here

Post by **YeOldeStonecat** » Mon Jun 13, 2005 8:18 am

OK so your server can surf fine, what IP information are your clients getting?

Jonty · Post by **Jonty** » Mon Jun 13, 2005 8:23 am

The clients are running on the 192.168.16.x to 192.168.16.xxx range. The server uses DHCP, and everything on that side is fine. When I try and ping the 192.168.0.1 (ADSL Machine) and 192.168.0.2 (Card 1) from the client machines they just time out.

Just ran a tracert on the server to the ADSL machine (192.168.0.1) and it came up with the following:

USERNAME.mshome.net

Ok that's wrong as we are on a domain, went to change the domain name; however, it was already set to the original domain i.e. USERNAME.xyz.local

Just wish they would let me spend some more money and buy a bloody router

got to get it working with what I've got at the moment. I'm sure it's possible, but not sure how.

Post by **YeOldeStonecat** » Mon Jun 13, 2005 5:45 pm

Well, from experience I've not done a multi-homed setup like you have using the ICS built into Windows Server, when I've done multi-homed setups it's been on a Small Business Server that's using ISA (basically todays version of Proxy).

Sounds to me like you'd need to reconfigure your gateway on the LAN NIC of the server, and the gateway handed out to your clients. Your clients should be getting your servers LAN IP address as their DNS server. DNS will be important for local name resolution and active directory to function correctly.

Here's a quick readme on setting up ICS on 2K3.
http://support.microsoft.com/default.as ... -us;324286

Jonty · Post by **Jonty** » Tue Jun 14, 2005 10:05 am

Cheers for the help

Had a chat with them today and told them they needed an ADSL Router, had to explain why... "just said it would make my job a damn sight easier! Jesus I'm a Quantity Surveyor not an IT bod"

They got some petty cash out, sent someone to get one and hey presto it now works like a dream.

Thank you again for the help

Post by **YeOldeStonecat** » Tue Jun 14, 2005 10:15 am

Jonty wrote:
They got some petty cash out, sent someone to get one and hey presto it now works like a dream.

Good to hear they accepted the more rock solid solution!