Win2k routing issues

[Gary Davidson]

Hi guys, could reaslly do with some help here.

Here's my scenario:

Have a Win2k Pro machine off site which connects via internal ADSL
Modem card to office - No problem there.

Win2k maschine also has an ethernet card connected to a Dlink Wireless
to Ethernet bridge. Ethernet card uses DHCP for IP address from
wireless AP on subnet 10.194.45.x.

Win2k machine also connects via an Arcnet card to an NT4 client
machine using a static IP of 10.194.44.x.

Win2k and NT4 pc's communicate via arcnet on 10.194.44.x with no
problem.

By adding a static route on the NT machine it can see the ethernet IP
address of 10.194.45.x on the Win2k machine.

The problem with the client NT4 comes when trying to the see the
wireless AP on 10.194.45.xx or any other machine on subnet - It can't
see anything. It can route to the win2k on 10.194.44.x and then
looses where to send the packet next.

I need to be able to get to the NT4 machine from a wireless PC routing
through the win2k pc and I need the NT4 machine to be able to see PC's
on the 10.194.45.x wireless network.

It's messy, I know but how can I do this??

I have enabled IP forwarding in the registry.

Any help greatly appreciated.

Regards

Gary

 

[Doug Sherman [MVP]]

Try:

1. On the Win2k Pro machine, run ipconfig /all and make sure that routing
is enabled. If not, run regedit and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Change the value of IPEnableRouter from 0 to 1.

2. The static route on the NT machine should allow you to connect to
machines on the 10.194.45.x subnet by IP address - eg.
\\10.194.45.1\sharename. Your ability to connect by computer name depends
on the name resolution mechanisms available on your network. If these
machines have static IPs, you could use an lmhosts file. You may or may not
be able to 'see' the machines on the remote subnet depending on whether WINS
is configured, domain vs. workgroup, location of master browsers, etc.

3. For the machines on the 10.194.45.x subnet to access the NT machine,
they must use the 10.194.45.x NIC on the Win2k Pro as a default gateway, or
have a route to this NIC configured on different default gateway, or have a
static route configured to this NIC on the client machines. For this reason
using a dynamic IP on the 10.194.45.x NIC on the Win2k Pro machine is not
recommended.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[gdavid9]

Thanks for the reply Doug.

Routing is enabled.

The static route on the NT Machine is as follows.
10.194.45.0 mask 255.255.255.0 10.194.44.1
The 10.194.44.1 is the IP address of the Win2k on the acrnet. With
this added I can ping the IP of the Wireless on 10.194.45.xxx on the
win2k PC.

I have added the 10.194.45.xxx address as the gateway on the NT machine
but I still can't ping any other machines.

Using a static route on the PC's on 10.194.45.xx I can get to NT
machine. Just need to get from the NT to the 10.194.45.xx. Half way
there.

I agree about not using dynamic IP, if I can prove routing in both
directions then I maybe able to address this.

Thanks

Gary

 

[Doug Sherman [MVP]]

Don't know what to tell you at this point - routing appears to be properly
configured. Most likely either the AP or some downstream firewall is
blocking communication. For example, if the 10.194.45.x network has XP
machines or the machines are running third party firewalls, they may be
configured to block ICMP (ping) echoes. Or, they may be configured to allow
networking only on the local subnet.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP