But the whole local network mask is 255.255.0.0 wich means that its is possible to have local boxes configured with an IP in the form /16. What about routing tables on the client side, that is on 192.168.110.254 box ? Maybe there is a route to the only W2K box (192.168.158.15) ? I am a bit surprised by output of traceroute on the HP-UX box. Maybe you could try to modify HP-UX's routing table in the same way ? For example metric of 10 for the default route, 1 for the exceptions. Since we are speaking of metrics, take a look at the W2K's routing table and notice that default route has a metric of 10, and that the routes to the exception networks (192.168.100.0/24, 192.168.135/24 and 192.168.222.0/24) have a metric of 1. So wich metric did you used for this route ? The "G" in UG means the route has been entered with a metric, that it is a Gateway. I think it is not possible, but if it would, you host would be no more reachable. I guess it would be a very, very bad idea. Once this has been said, and though I am not a network guru, here are some suggestions : Sorry I try to explain the best I can, but I've a lack of english vocabulary.ĭ'abord arrete de jeter la pierre sur ton Anglais : le mien est au moins aussi mauvais, mais j'arrive a me debrouiller -)
255 255 255 255 NETWOK WINDOWS
Sorry but when someone says, "it's not possible" may he/she explain why it can work from windows and not from UNIX.įorget to mention no firewall involve in this configuration.Īgain, for me I can't see why adding route 192.168.110.0 with mask 255.255.255.0 cannot work ( I may be stupid :) ! ). If yes, It should be possible to add the new route.Īs I'm french I'm not sure of what you mean by "fall in subnet". Will the lan 192.168.0 still able to connect to server.
255 255 255 255 NETWOK PC
To Duncan and Steven that's what I was thinking, most of the desktop PC are inġ92.168.0.0 lan, they can connect the HP because lan mask is 255.255.0.0. To Asif : customer network team says the router is ok, the remote customer connect to other 192.168.158.* server : they say the router routes are properly configured. Then they had a remote site/users connecting these servers(), so they ask me to add the new route. The default gw is an AD( win2003) I don't know why. This is a customer config, as far as I know lan hosts are 192.168.0 mask 255.255.0.0 HPE Blog, Austria, Germany & Switzerlandįirst of all sorry default gw is not 192.168.0.254 but really 192.168.0.199 as you can see on netstat.ġ92.168.100.0 route should help a remote user to connect the server via 192.168.0.254.
0 kommentar(er)
