Need Multimedia Audio Controller for W7 installation

On Fri, 17 Aug 2018 12:31:28 -0400, Paul
wrote:

wrote:
On Fri, 17 Aug 2018 11:28:20 +0100, "J. P. Gilliver (John)"
wrote:

In message ,
writes:
On Fri, 17 Aug 2018 00:46:10 -0500, Char Jackson
wrote:

On Thu, 16 Aug 2018 15:52:01 -0400, wrote:

[]
On 15/08/2018 22:41, wrote:
[]
This emachine T3104 ran fine then - had both internet and
audio once I
installed the drivers, However it was horrendously slow, so
I decided
to try XP on it. Now I have reached the point where I can't connect
to the web. All else seems fine. I have tried and tried to
install/reinstall the connection, but I can't find the place
[]
I pinged the above 192.168.1.200 from my W10 PC and it found it.
I pinged this W10PC IPV4 Address 192.168.1.155 (taken from ping on
that machine) from the emachine WXP and it did not.

Mean anything?
Could just be that ICMP is disabled on the W10 firewall.

192.168.1.1 worked - 4 packets sent and received.
8.8.8.8 worked - 4 packets sent and received.
216.58.203.133 (gmail.com) - worked - 4 packets sent and received.
both machines. One is WXP, one is W10.

Now what?
Thanks
J
That's weird! Sounds like you have a connection. (Did you ping gmail.com
using its name, or did you specify its numerical IP address?) Maybe
something about the browser setup.

If you put http://216.58.203.133/ into the browser, do you get anything?


I get:

There is a problem with this website's security certificate

It recommended not going to it.
but I did anyway.
It went into a network diagnostic wherein it checked connectivity
wherein it said:

windows cannot conect to the internet using HTTP, HTTPS, or FTP.
Probably caused by firewall settings. Check firewall settings to the
HTTP port (80), HTTPS port (443) and FTP port (21).

I dunno how to do that. I will try.,

I do see errors in the Network Diagnostic under connectivity:
HTTP Successfully connected to www.microsoft.com
HTTPS Error 12157 an error occurred in the secure channel support
FTP(Active) Error 12029 connecting to ftp.microsoft.com A
connection with the server could not be established.
Could not make an HTTPS connection
Could not make an FTP connection
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!

Ohboy!
J


Are you running that diagnostic from WinXP ?

Yes - the problem emachine xp pc.

What were you expecting exactly ?

dunno.


*******

Of course HTTP worked successfully. There's no crypto
involved with that test case.

HTTPS has many variables, including certificates
and crypto choices for the connection. WinXP certificate
store might not be the same as other OSes. It's
easy to fail this test.

And ftp.microsoft.com is still running ???
The last time I tested that, it was borked.
Whether PASV or not.

In summary, your test shows you can reach the
Internet. The other test cases are inconclusive.
Maybe ten years ago, I would be more concerned
about the results. Today, that result is "normal"
for some values of "broken or borked" Internet.
You expect stuff like that to happen in 2018.

*******

If the only node you can't ping is the other
computer, then you have a NAT router in the
picture you're not telling us about.

Verify the wiring used on the two computers
and the router. And make sure there aren't
more networking boxes you aren't telling us
about.

I have a single Verizon router cat5-wired to two computers and to
wireless AIO and laser printers, I have a remote laptop that at least
used to print on either printer. Wud have been wireless of course.
Have not printed from it in years. The printers are also direct-wired
USB to the xp10 pc and they work nicely.


I can just smell a complicated networking
setup in that room... Start tracing the wires.

Paul

I will double check wiring tho. Maybe there is something amiss there
fho.
But remember now. Earlier I said I did have W7 installed on the
emachine and internet worked fine - just too too too slow. When I
changed the emachine to xp, I did not change any wires. That's when
the problem started. Really I didn't.
Thanks
J

On Fri, 17 Aug 2018 16:39:19 -0400, wrote:

On Fri, 17 Aug 2018 12:31:28 -0400, Paul
wrote:

wrote:
On Fri, 17 Aug 2018 11:28:20 +0100, "J. P. Gilliver (John)"
wrote:

In message ,
writes:
On Fri, 17 Aug 2018 00:46:10 -0500, Char Jackson
wrote:

On Thu, 16 Aug 2018 15:52:01 -0400, wrote:

[]
On 15/08/2018 22:41, wrote:
[]
This emachine T3104 ran fine then - had both internet and
audio once I
installed the drivers, However it was horrendously slow, so
I decided
to try XP on it. Now I have reached the point where I can't connect
to the web. All else seems fine. I have tried and tried to
install/reinstall the connection, but I can't find the place
[]
I pinged the above 192.168.1.200 from my W10 PC and it found it.
I pinged this W10PC IPV4 Address 192.168.1.155 (taken from ping on
that machine) from the emachine WXP and it did not.

Mean anything?
Could just be that ICMP is disabled on the W10 firewall.

192.168.1.1 worked - 4 packets sent and received.
8.8.8.8 worked - 4 packets sent and received.
216.58.203.133 (gmail.com) - worked - 4 packets sent and received.
both machines. One is WXP, one is W10.

Now what?
Thanks
J
That's weird! Sounds like you have a connection. (Did you ping gmail.com
using its name, or did you specify its numerical IP address?) Maybe
something about the browser setup.

If you put http://216.58.203.133/ into the browser, do you get anything?


I get:

There is a problem with this website's security certificate

It recommended not going to it.
but I did anyway.
It went into a network diagnostic wherein it checked connectivity
wherein it said:

windows cannot conect to the internet using HTTP, HTTPS, or FTP.
Probably caused by firewall settings. Check firewall settings to the
HTTP port (80), HTTPS port (443) and FTP port (21).

I dunno how to do that. I will try.,

I do see errors in the Network Diagnostic under connectivity:
HTTP Successfully connected to www.microsoft.com
HTTPS Error 12157 an error occurred in the secure channel support
FTP(Active) Error 12029 connecting to ftp.microsoft.com A
connection with the server could not be established.
Could not make an HTTPS connection
Could not make an FTP connection
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!

Ohboy!
J


Are you running that diagnostic from WinXP ?

Yes - the problem emachine xp pc.

What were you expecting exactly ?

dunno.


*******

Of course HTTP worked successfully. There's no crypto
involved with that test case.

HTTPS has many variables, including certificates
and crypto choices for the connection. WinXP certificate
store might not be the same as other OSes. It's
easy to fail this test.

And ftp.microsoft.com is still running ???
The last time I tested that, it was borked.
Whether PASV or not.

In summary, your test shows you can reach the
Internet. The other test cases are inconclusive.
Maybe ten years ago, I would be more concerned
about the results. Today, that result is "normal"
for some values of "broken or borked" Internet.
You expect stuff like that to happen in 2018.

*******

If the only node you can't ping is the other
computer, then you have a NAT router in the
picture you're not telling us about.

Verify the wiring used on the two computers
and the router. And make sure there aren't
more networking boxes you aren't telling us
about.

I have a single Verizon router cat5-wired to two computers and to
wireless AIO and laser printers, I have a remote laptop that at least
used to print on either printer. Wud have been wireless of course.
Have not printed from it in years. The printers are also direct-wired
USB to the xp10 pc and they work nicely.


I can just smell a complicated networking
setup in that room... Start tracing the wires.

Paul

I will double check wiring tho. Maybe there is something amiss there
fho.
But remember now. Earlier I said I did have W7 installed on the
emachine and internet worked fine - just too too too slow. When I
changed the emachine to xp, I did not change any wires. That's when
the problem started. Really I didn't.

Your tests have already confirmed that your network wiring is fine.
Don't spend too much time looking at that.


--

Char Jackson