Browsing Two Networks

I've got a NT4 server with 2 nics and 2 Win98SE stations. I've connected one Win98 station to each nic on the NT4 server via crossover cable. Both Win98 stations are logging in to the domain "ROUTETEST" hosted by the NT Server.
The first nic has an ip address of 10.0.0.1 with a subnet mask of 255.255.255.0. The second has an address of 10.0.1.1 with a subnet mask of 255.255.255.0. So they're essentially two separate networks belonging to one domain. A WINS server is set up at 10.0.0.1.
The first Win98 station has an address of 10.0.0.2 with a subnet mask of 255.255.255.0 and a default gateway of 10.0.0.1. It is connected to the first nic on the NT server (via crossover).
The second Win98 station has an address of 10.0.1.2 with a subnet mask of 255.255.255.0 and a default gateway of 10.0.1.1. It is connected to the second nic on the NT server.
Both Win98 clients can log in to the domain and the NT server can see both clients in the Network Neighbourhood. However, each Win98 client can only see itself and the server when browsing the network. I'd like them to be able to see both Win98 clients.
I can map shared drives from one Win98 station to the other. But I can't browse. Why not!?

1. RE: Browsing Two Networks
lbyard May-04-01 12:11 PM
In response to message 0

Beats me. If you want to treat everything like it is on the same network, why don't you put everything on the same network/IP subnet? Have you enabled routing on the server? Larry

2. RE: Browsing Two Networks
ismits May-04-01 02:43 PM
In response to message 1

Since they're two separate adapters, I assume I can't have both nics on the same network. The first 98 client won't know that it has to go through the nt server to get to the other client.
I have already enabled routing: from one client I can map shared drives of the other client.
Why do it this way? It's a test. I'm to find a solution to this problem. And it's interesting, no?

3. RE: Browsing Two Networks
lbyard May-04-01 03:30 PM
In response to message 2

Believe there is a difference in "same networks" and same IP subnets. I don't see why you can't have 192.168.01 assigned to one of the server NICs and 192.168.0.2 assigned to the other one, for example. Interesting... that's debatable, but a NIC is cheaper than a hub. Larry