Re: Connection to ASDL modem fails on R2
- From: Joel Finkel <JoelFinkel@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 8 Jan 2008 13:21:00 -0800
The same bug in two different NIC drivers? Perhaps. I use an old 4-port NIC
form Alacritech and a new one from Linksys. Both exhibit the same behavior.
"Volodymyr Shcherbyna" wrote:
Most likely, a bug of NIC driver..
--
Volodymyr
NG tips:
http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx
"Joel Finkel" <JoelFinkel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2BBC148E-32A6-44E5-85F6-D08311D8FB43@xxxxxxxxxxxxxxxx
I now believe this to be an issue with R2. I booted my old OS (Windows
Server 2003 Standard wiht SP2) and my connection has been stable for
several
hours.
This proves that the issue is with neither the ISP nor the hardware.
There
appears to be either a bug in R2 or a fundamental incompatability with R2
and
my NICs.
"Joel Finkel" wrote:
Upon rebooting, there is no outgoing traffic UNTIL I toggle the IP
address.
Simply setting it to some bogus IP address and then back to what it
should be
is insufficient for grtting traffic to flow.
Wireshark reveals incoming traffic, but my machine simply stops
responding
to them.
"Joel Finkel" wrote:
Nothing has fixed the problem, including uninstalling and re-installing
the
Kerio Firewall. I am lucky if the conneciton lasts for more than 5
minutes.
Any suggestions, short of doing a fresh install of Windows Server 2003
R2?
Thanks in advance.
Joel Finkel
"Joel Finkel" wrote:
The ISP has confirmed that there are no problems on their end.
I followed the directions given here:
http://support.microsoft.com/kb/317518/, and issued the following
command:
netsh int ip reset resetlog.txt
I rebooted, re-entered all the requried informaiton for TCP/IP on the
NIC,
and rebooted. The symptoms did not disappear.
I followed the directions given here:
http://support.microsoft.com/default.aspx/kb/325356, and issued the
following
command:
netsh winsock reset
I then rebooted. I will post the results. I expect the NIC to hang,
but
maybe this will solve the issue.
-Joel Finkel
"Volodymyr Shcherbyna" wrote:
Weird behaviour ... Can you un-install Kerio FW and make the tests?
Also you
may contact your ISP, whether it might be a hardware issue with
their modem.
--
Volodymyr
NG tips:
http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx
"Joel Finkel" <JoelFinkel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:712BB10F-0501-4C0D-8095-4844E7DD64EE@xxxxxxxxxxxxxxxx
Okay, I start unfiltered logging and packets stream by. Then,
it all
stops.
It only begins again when I :
1) goto Network Connections | Connection Properties | General |
Internet
Protocol | Properties
2) Change the IP address and Close all the way Status page
(Network
Connections | Connection Properties | General)
Packets start flowing again within a second.
They start flowing even if I enter a bogus IP address although,
of course,
I
do not have connectivity until I set it to one the two the IP
addresses
assigned to me.
Interestingly, if I have been using IP A and it fails, I can
enter a bogus
IP address, close out, and re-enter to enter IP A again. The
connection
resumes when I close out again.
In other words, I do not have to toggle between by two IP
addresses, A &
B.
All I have to do is CHANGE the IP address to something else, even
a bogus
one, and packets start to flow again.
Perhaps this is enough information that someone has a suggestions
for me
as
to how I can fix this.
Thanks.
"Joel Finkel" wrote:
Thanks, but I have absolutely no idea how to use this tool
(wireshark)
effectively. I'm an application software developer, not a
networking
guru,
so all of that stuff is Greek to me.
/Joel Finkel
"Volodymyr Shcherbyna" wrote:
Use wireshark or simular to investigate the problem and have
more
details to
provide here.
--
Volodymyr
NG tips:
http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx
"Joel Finkel" <Joel Finkel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:C2858309-9900-4B5E-BC77-FD6192E8BEB1@xxxxxxxxxxxxxxxx
Folks,
Forgive me if this is not the proper newsgroup, but I cannot
find one
more
appropriate.
I have a machine running Windows 2003 R2. It has a NIC
connected to
an
ADLS
modem, which I use for internet connectivity. My ISP has
provided me
with
two IP addresses, lets call then A and B.
I use the Connection Properties window to set the NIC's IP
address to
A,
and
set the other values (Default Gateway, DNS servers, etc).
It will
work
for
30-90 minutes and then fail.
I then set the IP address to B and it will work again for
30-90
minutes.
If
I toggle it back to A, it will work again for a while. In
other
words, I
have to keep toggling the NIC's IP address assignment.
I have tried a second NIC, with the same results. I have
connected
directly
to the modem and through a switch: same results. I am using
a Kerio
Firewall, I have the same symptoms when it is turned off.
Everything worked beautifully under Windows 2003. It began
to fail
when I
did a fresh install of R2.
Any assistance is greatly appreciated. Thanks in advance,
Joel Finkel
- References:
- Re: Connection to ASDL modem fails on R2
- From: Joel Finkel
- Re: Connection to ASDL modem fails on R2
- From: Volodymyr Shcherbyna
- Re: Connection to ASDL modem fails on R2
- From: Joel Finkel
- Re: Connection to ASDL modem fails on R2
- From: Joel Finkel
- Re: Connection to ASDL modem fails on R2
- From: Joel Finkel
- Re: Connection to ASDL modem fails on R2
- From: Joel Finkel
- Re: Connection to ASDL modem fails on R2
- From: Volodymyr Shcherbyna
- Re: Connection to ASDL modem fails on R2
- Prev by Date: Re: C program wit memory and address
- Next by Date: Re:How to configure PPPOE network adapter settings in XP,VISTA in .Net
- Previous by thread: Re: Connection to ASDL modem fails on R2
- Next by thread: Re: Winsocket send fails
- Index(es):
Relevant Pages
|
Loading