You could put your own entries in the systems Hosts files. So that for example "PC1" would resolve to 192.168.1.100. One "set" of entries common to all machines should do the trick...
Find that file at... C:\WINDOWS\system32\drivers\etc in XP. Add entries such as. 192.168.1.100 PC1 192.168.1.101 PC2 Note! Only put entries in a PC's file, for the "Other" PC's on the network, not itself. Windows (and many other OS's) will always look up the Hosts file entry, before doing an DNS queries. So, anything in there takes presidence. This is also one way to hijack a PC, though not very common now, as it's too well known, and easy to fix. But... If you have all the PC addresses assigned by DHCP from the router (the normal way these days) they could change outside of your control, when they power up next time. Solutions. Firstly, do not use "automaticly detect settings" in the Internet setting dialog. It is posible for that protocol to "get out" and your PC connection then gets diverted via "someone else". It's rare, but it can happen. Set each PC to use your router as their DNS servers, this may be done by DHCP too. The router itself will then pass the request for sites unknown to it, to your ISP, and keep a local copy of the most frequent ones you use, well some routers do that, your PC's do not need to know anything about your ISP, only the router needs that info. If the router supports it (most do) use "LAN address reservation" so that it will always keep one particular address reserved for a particular MAC address, regardless of if it is is connected or not. You can usualy set up many such entries. Fixed addresses at each PC. That may be OK for machines that dont physicaly move outside your network, but any laptops would then need some fiddling to allow to connect to a "Hotspot" or other LAN. Check that any instances of the XP firewall, has the appropriate exceptions enabled for your application, and to allow incomming connections from other "Trusted" PC's on your own LAN. As you are behind a router, you could probably disable the XP firewall. But, if one other PC "picks up something malicious" when surfing the web, that could then get to the other unprotected PC's if their firewall's are down, if it wanted to. You may also find that the router (again, many offer this.. "Wireless Isolation" Netgear call it for example) will activly prevent a wireless machine, from "seeing" any other wireless connected devices! Good if you run a hotspot, but an absolute pain if you just want a home LAN. If you have file sharing working OK between the WiFi PC's, at least that should not be the problem. Lastly, when you have all the WiFi gadgets working with each other, learn how to, and use WPA/PSK encryption for the WiFi. XP makes it very easy to get multiple machines all connected to the same router/accress point, so long as you have a USB stick to move the settings arround with. But, please use a "Good" passphrase for the WPA key (non-dictionary words and numbers) or there is a remote chance it could be discovered with a "dictionary attack"... NOTE! This is not the same as someone useing one of the WEP crackers, WEP (NOT WPA) has a well known vulnerability. WPA with a good key phrase, is regarded as all but unbustable. Take a look at www.grc.com, they have a lot of good information as to how "The Net" and TCP/IP works. Hope something helps.. Dave B. > -----Original Message----- > From: Joseph A Benson [mailto:[EMAIL PROTECTED] > Sent: 10 July 2008 14:10 > To: twsocket@elists.org > Subject: [twsocket] HttpCli / LAN / Router / Proxy / ?Help! > > Hello > > I am looking for some assistance regarding the use of HttpCli > over a wireless LAN. > > I started using ICS recently from C++ Builder (5 > Professional) as a more reliable alternative to the > Netmasters components - in particular I used HttpCli > successfully on a single computer connected to the internet. > > Last week I setup a home wireless network using a linksys > access point to share my broadband connection - everything > works OK and I have internet access and file sharing for all > computers. I have since discovered that my program built > using HttpCli does not work anymore, if run on any of the > wirelessly connected computers, but works fine on my main PC > (PC1) which is wired directly to the router. > > Home Network Setup : > > Linksys Router/Access Point/broadband connection - 192.168.1.1 > PC1 - wired connection to router - 192.168.1.100 > PC2 - wireless connection to router - 192.168.1.101 > PC3 ... .102 etc > > All the PCs run Windows XP SP2 with full updates, and the > networking equipment is all from Linksys (router is a WAG200G). > > When run on any PC > PC1 Httpprot.pas throws an exception > when attempting to do a Get() - it returns a 400 with error > message "cannot resolve IP address". I have run the "httptst" > sample program supplied with ICS and I get the same error. > > To fix the problem I have tried changing various properties > of the HttpCli, e.g. setting the routers address as > proxy,username/password, but without any luck. I looked for > some differences between the computers setups - all Ifound > was that the wired computer PC1 had "no proxy" in its > browserconnection settings, while PC2 has "automatically > detect proxy settings". I have *not* tried changing any > settings on the router itself, as to be frank, I am not very > knowledgeable of it, and it seems to be working OK, apart from this. > > I have been checking the archives and while there are some > similar queries, none quite seems to have the answer I need - e.g. > > http://lists.elists.org/pipermail/twsocket/2001-December/012228.html > http://lists.elists.org/pipermail/twsocket/2004-January/024221.html > http://lists.elists.org/pipermail/twsocket/2006-March/033175.html > > I am going to have a look at the ICS user-created sample > code, some of which looks promising - i.e. iphelp, socketspy, > proxyinfo and traceroute > - but any immediate answers would be greatly appreciated. > > regards > > Joseph Benson > > > This mail has been scanned by Palmer Cook Computer Services Limited. www.palmercook.co.uk -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
