From: <ch...@to...> - 2004-05-17 11:47:10
|
The campus using 192.168.0.x could be a problem you may have to start thi= s at home and change the tap back to 10.1.2.5 after windows tries to set it to 192.168.0.1 . This may only be possible on XP in my experience win2k insists on using the 192.168.0.1 address and network for ICS but I have heard that XP lets you change it (unconfirmed). There was some talk a while back about using a proxy on win2k to get around this. chris > On Sun, May 16, 2004 at 02:56:10PM +0100, Zaki wrote: >> Thanks for the reply guys. >> >> Usually, I'll move around constantly between campus >> and my house. Campus is 192.168.0.x and House is >> 10.1.1.x, so what ip address(n subnet) should i use >> for the NAT? I'll have vnc working tomorrow with >> XDMCP. Should I set static IPs in NAT and have TAP a >> static Ip and then i vnc into it everytime? >> > > I understand your netmask at home is 255.255.255.0 > If so, here's a simple recipe: > > On the Windows side of TAP, set > IP 10.1.2.5 > Netmask 255.255.255.0 > > On the colinux side, make sure DHCP is disabled, set > IP 10.1.2.11 > Netmask 255.255.255.0 > Gateway 10.1.2.5 > > Use 10.1.2.11 to access coLinux from Windows host. > > Enable ICS on the adapter you use to connect to home/campus network, > select > TAP as the home networking connection. > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=3D2562&alloc_id=3D6184&op=3Dclick > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |