cRunchy

Group: Members
Posts: 16
Joined: Mar. 2006 |
 |
Posted: April 07 2006,15:41 |
 |
Quote (doobit @ April 06 2006,18:01) | I've not had any problem with wget through a router, and a firewall, over wireless or hardwired. I'm just using the default settings. |
This makes me wonder whether the problem might be due to network cards or drivers?
As I said I can use FTP but not HTTP most probably because FTP is slower or less prone to errors... (General web browsing works fine.)
For reference or comparison my setup is:
System = XP on 1.7GHz 512MB Level = SP1 (I wonder if SP2 has less or more problems?) QEMU network settings = Default Network Card = Generic PCI - AcerLan ALN-325 Drivers = RTL8139 (XP's own driver version.) LAN = NetGear Router --> Broadband
The other thought is whether using QEMU that is part of the "embedded" setup, "QEMU" as a separate install or "QEMU Manager" makes any difference. I prefer QEMU Manager but there may be slight differences that might help some people with the network problem?
cRunchy
|