I have had an NT4 Server upgrade dumped in my lap and I will be the first
to admit I don't have much NT networking experience. The problem I am
having is that ip forwarding does not seem to be working and I can find no
way to get win95 and 98 clients on the two subnets to browse each other.
My set up is as follows
16 port hub interface 1 interface 2
16 port hub
192.168.0.X---192.168.0.2 Win NT4 Server 192.168.1.2---192.168.1.X
|
|
192.168.0.1--------> dial up to ISP
Win XP client with dial up internet service
Note netmask is 255.255.255.0 and ip forwarding is enabled on the NT server
Each hub has a number of Win95 or Win98 clients hanging off. I have set
up DHCP on the NT Server and I am getting ip addresses assigned to the
clients no worries. The clients can all ping the interface on their subnet
but can not ping anything on the other subnet.
The Win95 and 98 clients can all browse shared drives on the server and
can browse any shared drives and printers on their subnets but can not
browse the other subnet but they can see the names of clients on the other
subnet. They just can't browse any shared resources.
The Win XP box has it's internet connection shared and all clients on the
192.168.0.X subnet can use the shared internet connection except the Server.
It can ping the XP box and if I ping a site out on the web it is resolving
an IP address but it can't ping it.
What I need to happen is for all clients to be able to browse each other and
I need any client to be able to use the shared internet connection.
I am suspecting that I have a routing issue but I have very little
experience with NT. As this site is located out in the middle of nowhere
it has been dumped in my lap to get it working.
I would appreciate any help I could get.
Regards
Richard
--
____________________________________________________
Richard Luckhurst
Manager / Engineer
Sound Advice
P.O. Box 104
Narrabri NSW 2390 Australia
Ph / Fax +61 2 6792 6060
>I have had an NT4 Server upgrade dumped in my lap and I will be the first
>to admit I don't have much NT networking experience. The problem I am
>having is that ip forwarding does not seem to be working and I can find no
>way to get win95 and 98 clients on the two subnets to browse each other.
>My set up is as follows
>
>16 port hub interface 1 interface 2
>16 port hub
>
>192.168.0.X---192.168.0.2 Win NT4 Server 192.168.1.2---192.168.1.X
> |
> |
>192.168.0.1--------> dial up to ISP
>
>Win XP client with dial up internet service
>
>Note netmask is 255.255.255.0 and ip forwarding is enabled on the NT server
>
>Each hub has a number of Win95 or Win98 clients hanging off. I have set
>up DHCP on the NT Server and I am getting ip addresses assigned to the
>clients no worries. The clients can all ping the interface on their subnet
>but can not ping anything on the other subnet.
Have you enabled IP forwarding in the TCP/IP properties of the server?
>The Win95 and 98 clients can all browse shared drives on the server and
>can browse any shared drives and printers on their subnets but can not
>browse the other subnet but they can see the names of clients on the other
>subnet. They just can't browse any shared resources.
Pinging and browsing are a different matter. Browsing will require
Netbios name resolution, normally provided by WINS. Properly
configured, this should allow your browsing. look up WINS in the help
on the server.
>The Win XP box has it's internet connection shared and all clients on the
>192.168.0.X subnet can use the shared internet connection except the Server.
>It can ping the XP box and if I ping a site out on the web it is resolving
>an IP address but it can't ping it.
More problematic. You need to set all the 192.168.0.x clients with a
default gateway of the XP system so they can use the internet. They
also all need a static route entered to reach the other subnet, such
that they use the NT server NIC as their gateway address for the
192.168.1.x subnet. On the 192.168.1.x subnet you'll need the NT
server's NIC as the default gateway, and on the server you'll need the
XP system's IP as the default gateway.
Go to a command prompt and type ROUTE /? for information on setting
static routes, or use the help functions.
Jeff