General discussion

Locked

Static Routes assigned by DHCP

By IronEagle ·
This may be a relatively simple question.

I have a Win2k server running DHCP for 2 subnets and another subnet that has static IP range assigned.

I have a WinXP client in one of the DHCP subnets which is connected directly to the server, and another client (WinXP) connected via a hub on the other subnet.

Without a static route the clients cannot see each other. Both can see the relevant NIC on the server. Of course this is expected though.

The problem is this: The subnet mask I have chosen for my own reasons is 255.255.255.224. DHCP on Win2k can assign static routes (option 033), but uses the 255.255.255.255 subnet mask which doesn't work. Does anyone know how to change the subnet mask to a custom mask?

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Static Routes assigned by DHCP

by IronEagle In reply to Static Routes assigned by ...

NOTES:
If I manually add a static route by using Route add. Everything works fine.

My network consists of three subnets.
192.168.x.0 mask 255.255.255.224
192.168.x.32 mask 255.255.255.224
192.168.x.64 mask 255.255.255.224

I have tried setting up RRAS, but I can't get this to work either, it does not appear to pass the routes to the clients as I would expect.

Collapse -

Static Routes assigned by DHCP

by Haissam In reply to Static Routes assigned by ...

as far as I know Option 33 implements stateful network routes i.e. the subnet should be implicit in the network.

You can try adding the routes using a once off log on script to all the clients.

Collapse -

Static Routes assigned by DHCP

by IronEagle In reply to Static Routes assigned by ...

Poster rated this answer

Collapse -

Static Routes assigned by DHCP

by d.walker5 In reply to Static Routes assigned by ...

A client had a similiar problem using a XP computer to obtain its' configuration from an NT v4 DHCP server. He was receiveing a valid IP address along with invalid options, or no options, and the subnet mask is set to 255.255.255.255.

To fix theproblem I reconfigured the static route (033) option on the DHCP server. You can also remove the option and static configure those nodes needing a static address. See Server Help "static route (033)." The static route (033) option is normally configured in pairs of address, however, the user interface in Windows NT 4.0 DHCP Server Manager allows you to type an odd number of IP addresses for the routes (it must be an even number.) If you do type an add number, the XP computer cannot properly interpret the DHCP packet information.

The subnet info you provided may be casuing a problem? The subnet mask of 255.255.255.224 provides for six subnets with thirty nodes each, totally 180 nodes. My a problem is understanding 192.168.0.0/27?

With a subnet mask of 255.255.255.224 the first three subnet IP address ranages are:

Subnet Valid Node Address

001 (32)-- 192.168.x.33/27 thru 192.168.x.62/27
192.168.x.63/27 Broadcast

010 (64)-- 192.168.x.65/27 thru 192.168.0.95/27
192.168.x.94/27 Broadcast

110 (96)-- 192.168.x.97/27thru 192.168.x.127/27
192.168.x.126/27 Broadcast

Try changing your DHCP Scope(s) to reflect the above.

Hope this helps.

Collapse -

Static Routes assigned by DHCP

by IronEagle In reply to Static Routes assigned by ...

This answer didn't exactly help me as I had found a work around prior to seeing the answer. I do have one question though, why do you add the /27 on the end of the IP Range. I'm new at this and always interested to learn, so if you can explain this, either here or by e-mail would be greatly appreciate it.

Thanks

Collapse -

Static Routes assigned by DHCP

by IronEagle In reply to Static Routes assigned by ...

This question was closed by the author

Back to Windows Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums