Slashdot Mirror
Workarounds for Vista's Networking Problems?
tridium asks: "I recently moved into a new place where the landlord left a Linksys WRT54G v2 router for us to use. The three laptops in the house running XP connected to it fine, but my desktop, running Vista RC1 build 5600, had to be hardwired. The Internet worked fine for a bit, but I noticed some websites weren't loading up (Google, Gmail, and several others), and IM clients weren't working. Vista's self-diagnosis said it couldn't communicate with the DNS server, so I researched and it seems the new TCP stack in Vista is wreaking havoc with my router. I upgraded the firmware from Linksys, tried manually setting IP settings, modified the registry to disable TCP window stacking, but nothing helped. Linksys support was also useless in fixing the problem. I'm at a loss and any help, short of downgrading to XP, would be greatly appreciated." Other people have experienced problems getting Vista to work with off-the-shelf routers. A thread from September identifies the new window scaling feature as a potential culprit, while another article says that Vista and SPI-enabled routers don't play well together. Whether the problem is related is unknown, but another thread offers some troubleshooting tips for anyone else who may be experiencing this problem. Has anyone figured out how to disable (or at least work around) some of the more troubling aspects of Vista's new TCP 'features'?
For me it stopped being funny after the 10,000th time. Imagine if every linux question were guaranteed to include multiple "Install the latest patch from Redmond" variants. Sure, it is funny once (especially the redmond one I just made up) but give it a rest once in a while. I'm extra unsympathetic to downmods since this used to be a guaranteed +5, Insightful. Stupid karma whores.
Anyway, even the most rabid linux fan has to admit that there are people who, for various reasons, use windows. Let them ask questions and get answers without snarky unhelpful "advice" from time to time ok?
Man, you really need that seminar!
This relates to a question I posed on Amiga.org:
t opic_id=35273&forum=22#forumpost417060
/dev/udp, etc.)
Amiga.org - Forum
http://www.amiga.org/modules/newbb/viewtopic.php?
"Is pluggable TCP/IP stacks feasible in mainstream operating systems?
On Amiga we have been graced with AmiTCP, Termite TCP, Miami, Genesis, and probably other TCP/IP stacks about which I do not know. IIRC, these mutated from an original stack produced by Commodore (AS225?) and all offer some compatibility to what appears to be ubiquitous among Amiga, the bsdsocket.library.
So I read about how Gibson Research decried the raw socket access introduced by the new Windows XP TCP/IP implentation (which has not caused the end of the world, best as I can tell,) and Windows Vista introduces another TCP/IP stack. All of these harken back to winsock.dll and winsock2.dll.
Then there's the TCP/IP stack within the Linux kernel, and found in most Unix implementations such as Solaris (/dev/tcp,
We run into so many issues with vendors' TCP/IP stacks (like Windows XP SP2's half-open connection limitation,) why do third party vendors not create third-party TCP/IP stacks? Or do they?
Regardless of the thought process behind the curiosity, could we speculate on the viability? Would it be a potential segregation of the mainstream OS world, or could one vendor's better implementation take over?
I see potential for the server market where many system builders, administrators, and maintainers would like to tweak system performance and security as much as possible. Would TCP/IP outside of the operating system allow for such an approach? And would it be too much of a potential black-eye for OS vendors to ever allow?"