On Mon, Jul 15, 2002 at 08:57:20PM -0400, Wesley Allen wrote:

Shortly after I started using a wireless lan, I began having problems with connecting to my local ip addresses; I'm not sure what's causing it. Internet works FINE, and yet, a couple of minutes after I boot my machine I can't connect to anything in the 192.168 range! It doesn't matter the protocol, smb, http, etc. no connections at all. What's stranger is that my win4lin install, which uses vnet, has no problems at all. What in the world is going on here? Any thoughts?

If this were a Sun box, I'd blame gated, which is the arch nemesis of all that is good and decent. ;) On a related note, the first thing I would look at is the routing table (netstat -nr), and make sure you have a route for that network. I would then check on the network interface and make sure it's passing packets (do a tcpdump or your favorite packet sniffer). -- Randomly Generated Tagline: "If you want a completely predictable and static environment, learn VMS." - Ed Taylor