Windows Forum

Ask something
Discussion Locked

multiple networks

0 helpful
12 replies

by terry.funk

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I work on a large network. We are changing from Netware to W2K. We also run TCP/IP across our different networks. I can ping any host on any network. So I don't think routing is the problem.

My problem is this: I can set up a Win Nt or W2K server on one net and all the workstations can see the server, let say this is network 192.168.1.0.

I can set up another Windows server on another network, let say this is network 192.168.2.0. All the workstations can see this server also.

However,I can't see server A from network B and I can't see server B from network A.

How do I get all the workstations from each of the two networks to see the servers on the other network?

I can ping via TCP/IP and via IPX. But with Windows 2000 or NT no way.

Thanks

12 replies

by bbrown

From your description, workstations on the same network with the server can ping it, the workstations can ping the workstations on the other network, but the workstations can not ping the server on the other network.
The conclusion is the netmask on the servers must not be set correctly or the servers do not have a default gateway set.
From your network description, the netmask should be 255.255.255.0 if divided into 192.168.x networks. The default gateway of the servers have to be an addresson the same network. Set it to the same as a workstation that works.

Bobby

by drdon

I assume your gateway is correct on the properties for TCP/Ip on the Win2000/NT server. In a mixed environemnt (netware/NT) frame type issues come into play. If you are using 802.3 (I know) for the Netware side, and "autosense" frame type on the NT/2000 side if 802.2 appears (HP printers) than NT/2000 defaults to 802.2 and you will not see the other side.

Next, check the Client configuration. If Client32 is used, enable the Domain to login to. (Are the NT/2000 servers in a single Domain?).

Check the event viewer on the NT/2000 server and be sure the services for the protocols started OK. Also look for a master browser error.

Do you have a router involved in your design? Check it out from the servers and workstations tobe sure it is ping-able.

Can you ping the hard set IP address for the servers from other workstations?

Hope checking the configuration helps.

by mckaytech

If what connects the two networks is a router, it has to be set up to forward NetBios packets so browsing can occur across the subnets. If you're coming from a Netware environment, it is likely that this capability was never enabled on the routers.

The end result would be exactly what you are seeing - you're able to ping everywhere but unable to browse across a subnet boundary.

regards!

paul

by dao251

It is unclear what you mentioned as "can't see". What happens when you type \\ in the Start-Run box on the server B?

I believe your issue could be name resolution.
By default your workstations/servers are not WINS-enabled and use broadcasts for name resolution. routers do not pass broadcasts -- that's why you "cannot see" another subnet (cannot query them by name, not by IP). You have to install WINS server in one of the subnets and "WINS-enable" your workstations (please refer to Getting Started coming with your NT).

If you mentioned something more sophisticated than name resolution please be more specific.

by dao251

It is unclear what you mentioned as "can't see". What happens when you type \\ in the Start-Run box on the server B?

I believe your issue could be name resolution.
By default your workstations/servers are not WINS-enabled and use broadcasts for name resolution. routers do not pass broadcasts -- that's why you "cannot see" another subnet (cannot query them by name, not by IP). You have to install WINS server in one of the subnets and "WINS-enable" your workstations (please refer to Getting Started coming with your NT).

If you mentioned something more sophisticated than name resolution please be more specific.

This discussion is closed to new replies.