SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : How high will Microsoft fly? -- Ignore unavailable to you. Want to Upgrade?


To: dybdahl who wrote (62264)10/28/2001 5:07:35 PM
From: rudedog  Read Replies (2) | Respond to of 74651
 
Lars - I am using an XP box with 2 NICs, one connected to a DSL line which passes a DHCP address, and the other to my home network, and the instant messaging works fine. The box I am currently typing on has 192.168.1.105 as its address after NAT, while the real DSL address is a 64.xxx.xxx.xxx address. The instant messaging works just fine through that. I assume that the XP box does some special translations to make that work since it obviously does not present the internally generated NAT address outward. I have also used a Linksys router and had to use the "DMZ" setting to get the messaging to work. I have not tried this with anyone not running XP except my brother, who is running Win2K on a cable modem with a fixed IP address. There are probably lots of "gotchas" in the new scheme but it is at least as easy as most VPN connections. BTW, VPN works just fine through the same rig, in fact works just fine with NAT on both sides.

I have only sympathy for the problems IT shops have in maintaining order in the face of hardware, software, network and user configuration changes. Not a job I would want.