> I'm firguring that a route has to be added but I'm not sure what route to
> use. It already automagically has a route like this...
>
> Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 209.0.37.97 192.168.200.106 1
>
> But note the interface. It seems to me that because the interface's
> primary address is assigned the rfc1918 address it can't see the gateway.
> Even WITH the aliased address of 209.0.37.98.
Well, honestly, when I dealt with this I had the default primary on the
interface and added the private address as the 'alias'. I think the problem
is that in this case the packets are sent out to the gateway, but have the
private address in the packet. (BTW I'm not a network geek, so excuse the
lack of correct terminology) However if you have a specific route set
up on the proper address it seems to work. EX:
First address (added through ctl panel-network) 209.0.37.98
With gateway set to 209.0.37.97
This gets the default route set up properly
Second address (added in regedit) 192.168.200.106
This approach has problems though, any local host lookup will have to
be through a host file on the windows machine, since the only DNS servers
the PC will find are probably on the internet interface. MS networking
may be a little more difficult, i.e. browse may not work however
mapping a network drive will be possible by manually entering the
resource.
There are no good options except the one you can't use - proxy
server.
--
Floyd Pierce |Manager I/T Marketing & Development
|Box USA
Phone 914-749-3289 |floydp@boxusa.com
Fax 817-315-1414 |floydp@imagin.net
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>