After some discussion, it seems Windows clients determine a netmask based on the class of the IP address. 10.x.x.x is a 255.0.0.0 netmask 192.168.x.x is a 255.255.255.0 netmask (I think) Perhaps the solution is as simple as choosing an IP range that Windows will assign the proper netmask to the route. FYC Allan - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
