(e-mail address removed) hath wroth:
I've emailed the author of NetSwitch to see if that does RWIN / MTU /
etc.
I'm not sure that it does. My laptop is sitting in my palatial
office. I'll check later this afternoon.
Jeff - GREAT idea about the simple reg files. That should do the trick,
easy, quick, and effective.
Yep. That's what I did before I bought Netswitcher. The problem with
that method is that some changes really do require a reboot. Changing
the numbers can cause "unexpected results" such as locking up the
entire IP stack after a few connects and disconnects. That was not
very common but intollerable for what I was doing (firmware updates
and router configs). There were also many more changes that I wanted
to make when switching locations. The one that drove me nuts was that
I had to use fixed IP addresses at some sites (for security reasons)
and dynamic (DHCP) addresses at others. Windoze has no native way to
switch between these without reconfiguring the interface IP settings.
Another was the SMTP server so I could send outgoing email from
inside. That would change with each location (this was before POP3
before SMTP and authenticated SMTP became popular). The REG files
will work fine for simple RWIN changes, but other stuff requires an
application.
I cross-posted thread to 5 (not 8) groups, because I was unsure which
group was most appropriate. Searches returned the most results for
RWIN in the 5 I selected. For future reference, which single group
would you suggest posting questions like this to?
The problem is that your question is Windoze specific and has very
little to do with wireless. The RWIN problem appears more in wired
connections than wireless. It's often difficult to determine the
areas covered by each newsgroup by name. It's also not a major
disaster if you elect to crosspost. I just think it's better if you
limit yourself to one or perhaps 2 newsgroups. When I formerly run a
news server (never again!), I would automatically drop locally
originated crosspostings with more than 3 groups.
People often trim headers in their replys. If we did that, would you
check all 5 newsgroups to see if there were any newsgroup specific
replies?
Some discussion on the topic:
http://www.cs.tut.fi/~jkorpela/usenet/xpost.html
In order:
comp.protocols.tcp-ip This is specific to the protocol itself and
not really involved with the Microsoft implimentation of TCP/IP.
alt.internet.wireless This is primarly for home wireless networking
and not really involved in anything MS specific.
microsoft.public.windowsxp.help_and_support This looks like a
beginners group for MS users and covers a huge range of topics.
microsoft.public.windows.networking.wireless This might be a good
choice as it involves both TCP/IP and wireless from MS.
microsoft.public.windowsxp.perform_maintain This seems to have
little on wireless performance but seems to emphasize server and
client performance.
My guess is that the lesser evil would be:
microsoft.public.windows.networking.wireless
I didn't think that
cross-posting would cause any problems, and am frankly still unaware of
what the problem with cross-posting is. Isn't most newsgroup software
smart enough to mark messages read in multiple threads?
The problem with massive crossposting is that it generates huge
threads as readers from each newgroup add their opinions to the
discussion. Most often, the thread moves off topic and degenerates
into multiple non-relevent discussions. I predict that this one will
diverge into a discussion on proper usenet etiquette. If you're
looking for quantity rather than quality, massive cross posting is the
way to do that. However, that's not the "real" problem (from my
warped perspective). I don't like the idea of people posting in
newsgroups that they don't read. Read first, search with Google
Groups, and then if you don't find anything, post.
