Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have a box with Windows NT Server 4.0 ( Service pack 4) running with two network cards. I would like the box to act like a router, routing between to networks. The problem is that all the domains shows up in network neighborhood, but not all the computers show up under the domains or are up reachable. I have turned on routing on the server, but it still continues.
The IP addresses for each network is 165.156.1.58 255.255.192.0
165.156.96.2 255.255.192.0
I think my problem is with my subnet mask.Any help would be greatly helpful!
Thanks!

I am no IP expert but I belive your subnet mask is wrong. They need to be different. That is the purpose of a router to router between differnet "networks". These are on the same network.

Your subnet mask is just fine. But I think your IP sceme is a little off, the 192 mask enables 62 hosts per subnet and one of your subnetts starts at 58. I belive the second subnet should start at 64 or 65. Also, make sure the IP forwarding check box is selected in your adapter properties, if it's routing then I'm sure thats OK too. Also NT uses NetBios to transmit your browser info, and NetBios is not routable. So I would look into using WINS, DNS, LMHOSTS\HOSTS to resolve your computer names to IP addresses. An easy way to tell if this is the problem is if you can ping the IP but can't see the computer in net neighborhood. Also, I belive only NT computers or 95\98 machines with file and print sharing installed will be seen anyway. Good Luck!

If you want to continue to use that subnet mask, you get 2 subnets, here is what your network addresses should be:
Subnet 1 - 165.156.64.0
Range - 165.156.64.1 to 165.156.127.254Subnet 2 - 165.156.128.0
Range - 165.156.128.1 to 165.156.191.254

the last response is correct because by using 192 as the third octet you are defining the network portion of the id to be the bits masked out by 192 - ie he 128 bit and the 64 bit. you can't have (normally) 00 or 11 which leaves you with 10 and 01 as the possible network ids. when you then put the host id in it means that the third octet must be 128+1 up to 128+63or 64+1to 64+63. the 63 comes from the remaining 6 bits of the 3rd octet after masking the first 2 bits.
by having 165.156.1.58, 255.255.192.0 you are saying you have a host id of 314 ( 58+256) on network id 0 which isn't allowed.
in addition you might be better off using class c rather than class b.

![]() |
SQL Server 7 Table Transf...
|
NT permissions
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |