WEll I have a DLink card here which I will get around to=20
putting in as it appears that no one is gonna fix=20
anything.
-----Original Message-----
Ya... those are the same ones that I got but from a=20
different location on their web site. Says 8.0 but=20
really they are 7.0.36.0

Thanks anyway.

I still have the RealTek installed anyway. That's=20
working. Disappointing though that it doesn't work the=20
way it's supposed to. Oh well maybe eventually Intel=20
will fixed this.


-----Original Message-----
http://support.intel.com/support/net...dapter/pro100/
p
r
o100ve/index.htm

That is the page intel support took me to. It doesn=20
not=20
appear to be for our card which I mentioned to him and=20
he=20
said that it is a library of drivers and contains the=20
drivers for our card. I-----Original Message-----
Can you let me know where you got the "latest"=20
drivers? =20
Are they for the Pro/1000 CT?

Thanks


-----Original Message-----
I had noticed the same thing when I called intel and=20
they=20
pointed me to the "latest" drivers. I emailed intel=20
about the situation but they have never responded. I=20
called their support line but the people on there are=20
like robots reading scripts and assume you are=20
stupid. =20
It is so pathetic its not even funny. I am thinking=20
its=20
time to just give up and install a new network card=20
and=20
forget about it. I made Microsof refund the 35=20
dollar=20
tech support fee they charged me as they couldn;t fix=20
the=20
problem either. You can't imagine the fire hoops=20
they=20
had me jumping through.
-----Original Message-----
That is... drivers for the Intel Desktop Board=20
D875PBZ=20
which has the Intel Pro/1000 CT NIC.


-----Original Message-----
Hey Richard

I just finally noticed something... on Intel's web=20
site... the LAN drivers (latest version) for=20
download=20
indicate that they are version number 8.0.62019

However... after downloading and installing...=20
that's=20
not=20
the version number... the version number is 7.0.36.0

I wonder if this discrepancy is on purpose or if it=20
is=20
really a mistake.


-----Original Message-----
Thanks James
-----Original Message-----
I posted this in an older thread.

I just disabled my onboard Intel NIC and=20
installed=20
a=20
RealTek. I now have audio/video. Intel better=20
fix=20
this! I was unable to roll back the drivers=20
since=20
the=20
original drivers that came with the board didn't=20
work=20
in=20
the first place and updating them to the ones=20
they=20
were=20
on the net didn't fix the problem either. So=20
rolling=20
back the drivers was not an option for me.

But it's working now with this NIC. I'll be=20
watching=20
Intel's web site to see if they update their=20
drivers=20
anytime soon. I better not hold my breath.

My motherboard: D875PBZ (onboard lan Intel=20
Pro/1000=20
CT)


-----Original Message-----
If you can tell me the versions of the driver in=20
question, as well as the
model of the card, I can have one of ours=20
testers=20
try=20
to=20
reproduce this. If
it is causing an issue, we can work with Intel=20
to=20
fix=20
it.

--=20
John Holmes
Developer, MSN Messenger

This posting is provided "AS IS" with no=20
warranties,=20
and=20
confers no rights.
Please do not send e-mail directly to this=20
alias.=20
This=20
alias is for
newsgroup purposes only.


"richard" wrote in message
bl...
And I like the "bad" reference. The fact is=20
that=20
they
are not "bad" they are BAD as in when you roll=20
back=20
the
driver the program them works. That is the=20
definition=20
of
BAD.
-----Original Message-----
Hi Richard,

The Intel NIC issue that you and others=20
discovered=20
in
another thread is not the only cause of
this problem. Realistically, the only way to=20
get=20
that
fixed is to complain to Intel --=20
unless these "bad" drivers are on=20
WindowsUpdate...
________________________________________ ____
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources -=20
http://messenger.jonathankay.com

"richard" wrote in message
bl...
Jonathan,
Alot of people have with Intel nic cards have=20
fixed=20
this
problem by rolling back the driver. There is a=20
problem
with intel nic cards and messenger that really=20
needs=20
to
be addressed.
-----Original Message-----
Greetings,

I don't believe the problem is on your side,=20
most=20
likely
since your contact isn't receiving
you, something on their side is blocking it. =20
Tell=20
them
to do the following:
Make sure that the Internet Connection=20
Firewall=20
hasn't
turned on, click Start, then
click the Control Panel. If you're in category=20
view
click Network and Internet connections
then click Network Connections. Right click=20
your
network/internet connection, then click
Properties. Click the Advanced Tab, and verify=20
that=20
the
Internet Connection Firewall is
unchecked.
If you're using a router (UPnP enabled),=20
remove=20
the
current port forwardings -- to do so,
click Start, All Programs, Accessories,=20
Communications,
Network Connections. Right-click the
"Internet Gateway" (should be under the=20
Internet=20
Gateway
heading) and choose Properties.
Choose the Settings button, click each 'msmsgs'
or 'msnmsgr' entry and then choose 'Delete'
to each one. Then close Messenger (right-click=20
the
Messenger icon, choose Exit), then restart
Messenger and try a voice/video conversation=20
again.

Finally, both of you should run through the=20
Audio/Video
Tuning Wizard (click the Tools menu
in the main Messenger window, then Audio=20
Tuning=20
Wizard).
_______________________________________ _____
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources -=20
http://messenger.jonathankay.com




"cumi" wrote in message
news:08f901c331a7$9e867fe0$a601280a@phx. gbl...
Hello,
i have a dell dimension 8300 with the newest=20
chipset
857,
i get the incoming picture and Video, but i=20
can=20
not=20
send
a
picture or video. I have no firewall or=20
router.=20
can
somebody tell me please why it dosen=B4t work.

Thanks for help


.



.



.

.

.

.

.

.

.

.

.