Forum Moderators: open
Thanks!
Is the stuff coming off the web actually running through the XP box? If so, then you might be able to change your connection set up to bypass that, and there would be no possibility of caching...though I don't know for sure if it will cache stuff or not.
(hope that helps).
I've used this setup before and I really don't like it. For <$100 (US) I'd put a cable/dsl router on the network if you have it. The setup you're using is forcing the XP box to do all the work, and slows down both your client and server. Otherwise, if you're on dialup, that's probably your best bet.
I've used this setup before and I really don't like it.
I would like to say that there are quite a few advantages of ICS too:
1. Client machines effectively have a direct connection to the Internet (although client machines can't accept incoming connections, so you can't host a webserver or something). You can use any application level protocol and connect to any port as with a direct connection.
2. Its faster than a proxy server setup.
3. You can set it up without the need of any additional software or hardware.
I would like to say that there are quite a few advantages of ICS too:
The only advantage I can see is when you're on a dialup connection. Fairly reasonable, inexpensive, and probably the only way to do it - unless of course you want to pay for multiple phone lines - If you have that much cash, you need to go high speed anyway.
If you have a LAN and a high speed connection, the only way to go is with the router. The last one I installed had NO setup. Just plugged it into the hub/switch and everyone on the LAN is flying.
P.S: we did discover software problems on certain servers (FTP) that we needed to access with the ICS setup. They went away when we used the Cable/DSL router setup.
bobriggs: Don't you have to buy additional static IPs from your ISP for the Cable/DSL router setup?
No. You get one IP address. All computers on the LAN are assigned an internal IP address, something like 168.192.100.1, 168.192.100.2, etc. The router takes care of all WAN requests. (they come from the one ISP static IP, then the router sends the request results to the local computer)
The FTP problem had something to do with the FTP server we were requesting info from not being able to handle passive transfers. The router looks like only one computer to that particular FTP server. I don't know why it fixed the problem but it did.
LinkSys makes a good router. That's the first one I used, and it had to be programmed.
Then I saw a cheaper one made this week by Siemens. 4 ports for the LAN, 1 port for the WAN (cable/dsl) and another for a shared printer port. (You plug your cable/dsl modem into the wan port and the PC's on RJ-45 into the hub portion). Nothing to it. I didn't have to program it like I did the LinkSys router. Immediately, all PC's on the network had internet connection. The shared printer port is great also. Just install the printer port software on each PC, then install your printer to use that 'shared port': piece of cake. Easy network printer.