Discussion Locked

multihomed server, NAT, Firewall, Win98

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a client with a Multihomed PDC, IP1= 192.168.1.1, 255.255.255.0, 192.168.1.20 Gateway. IP2=192.168.2.1, 255.255.255.0, No Gateway. IPX/SPX,Netbieu, TCP/IP, we need these protocols because of specialised software running from the SERVER. Everything has been working OK with our static routes, until we are trying to add a NAT/Firewall(DI-704),IP=192.168.1.20. DSL modem with static IP. Clients on 192.168.1.xxx work OK for Internet. Clients 192.168.2.xxx can ping Gateway but cannot ping Internet addresses. Browsing is none functional. Please help.

7 replies

by stillatit

Here is the relevant data from the DI-704 data sheet at http://www.dlink.com/products/broadband/di704/ :

The DI-704 allows up to 253 computers to simultaneously connect to the Internet through the same ISP account. The Di-704 employs a Dynamic Host Configuration Protocol (DHCP) that provides dynamic allocation of IP addresses for up to 253 clients on your network. Being very flexible, the DI-704 will connect to any Ethernet devices and multiple types of machines and operating systems.
--- end of quote ---

The bottom line is that it will do NAT for one class C range, not two. In any case, if you think about it, since the ..2.x addresses are coming through a router (the NT), NAT would route traffic back to the router, with no way to further address it to the originating computer.

You might think about buying a second static IP address on the DSL and putting a second DI-704 on the 192.168.2.0 segment. That is probably the cheapest solution, and certainly the easiest.

Good luck.

by rudolph(uk)

Select the DHCP Relay tab in the TCP/IP Properties dialog in the Server and specify the IP address of the remote DHCP server, in your case 192.168.1.20. I should work... hopefully.

by mckaytech

It sounds like you need to enable IP Forwarding on your multi-homed server and also set a gateway address on the second NIC (192.168.2.1).

As it now stands, a workstation on the .2 subnet would have no idea how to get to DI-704 on the .1 subnet.
paul

This discussion is closed to new replies.