2
1
I have come across an odd problem today. When trying to add a route to the Routing Tables (in Windows 7 Professional x64), I am using the command
Route add –p 192.168.20.0 mask 255.255.255.0 192.0.0.241
However, this gives me a Route: bad argument 192.0.0.241
, which would suggest to me that there is some kind of issue with that IP (which is our firewall). However, I then ran
Route add 192.168.20.0 mask 255.255.255.0 192.0.0.241
and it works fine and I can access that network. Does anyone have any ideas why the permanent routing did not work? I have used it on about seven or eight machines in the past without any issues (on XP and W7 machines).
Thanks
Interesting to hear that. All our PC's are on 192.0.0.x, however when this goes through the router, it supposedly then converts it to our external IP (64.something). The 192.168.20.x is our phone system that for some reason was put on a separate network to our PCs (mainly because the phone engineer didnt want to have to mess with extra config at the time - our managed services guys hate it!) – bmgh1985 – 2014-01-20T10:26:57.653
In fact, doing a WhoIs on that IP gives no such info. It actually says that: Addresses starting with "192.0.0." are reserved for a variety of different protocols by the IETF, the organization that develops Internet protocols. The common factor is that these addresses are not used by a single organization but by any network where the specific protocol is implemented. http://whois.arin.net/rest/net/NET-192-0-0-0-1
– bmgh1985 – 2014-01-20T10:31:56.053Take a look at either of these two Web pages: http://www.whatismyip.com/ip-address-lookup/ (here you will have to type in 192.0.0.241) and http://whatismyipaddress.com/ip/192.0.0.241
– MariusMatutiae – 2014-01-20T10:37:54.773Also, the Whois page you reference states: Addresses from this range should not be used as an alternative to the private IPv4 address ranges assigned by the IETF in the Best Current Practice. Apparently, your LAN is running against an explicit recommendation of the IANA, if all your PCs are on 192.0.0.0/24. – MariusMatutiae – 2014-01-20T10:40:12.567
Oh I dont doubt its a stupid IP range to use as a private address (I didnt set it up :P), but the point I am making is it is our internal network IP range and this has worked in the past (and even works now if done as a non-permanent connection) – bmgh1985 – 2014-01-20T10:43:46.673
Still all of this adds nothing to the fact that you cannot use a gateway with an IP outside the range of your subnet. You will have to find a gatway in the 192.168.20.0/24 subnet. – MariusMatutiae – 2014-01-20T10:44:03.460
.241 has a rout built into it to allow for connections to .20.0. Would be so much easier if the supposed "experts" who set these up for us years ago knew what they were doing (hopefully will be ripping these out in a year or so :P) – bmgh1985 – 2014-01-20T10:46:10.310