Unsolved
This post is more than 5 years old
77 Posts
0
1868
July 31st, 2005 18:00
Dimension 4700 Connectivity Issues ...
I'm having some connectivity issues when my D4700
first boots up and I'm using the onboard Intel NIC.
Are there any good PCI NICs that will be detected
and known to function on the Dimension 4700?
(my Broadcom NetXtreme is'nt detected)
Thanks.
--
blackjack
first boots up and I'm using the onboard Intel NIC.
Are there any good PCI NICs that will be detected
and known to function on the Dimension 4700?
(my Broadcom NetXtreme is'nt detected)
Thanks.
--
blackjack
No Events found!
fireberd
11 Legend
•
33.4K Posts
•
112.8K Points
0
July 31st, 2005 19:00
One issue is the PC startup before the broadband modem is ready.
If you power off the broadband modem and the PC and then power them back up at the same time, with newer and faster PC's, the PC will startup and the NIC card ready and attempting to handshake with the broadband modem before It's fully sync'd up and before it tells the PC the modem is "ready" and you will get some type of error notice that you can't connect to the "network" or that the modem is not ready, etc.
If that is the case, either leave the modem on all the time or power the modem up first and make sure it's fully sync'd before booting the PC.
I've come across this several times with customers and new PC's.
.blackjack
77 Posts
0
July 31st, 2005 22:00
function, XP Pro SP1a still does not detect the BC NIC.
It's detected quite well however, on my
D4600.
#####
The main problem I'm having is that I lose connectivity after
rebooting the computer when using the onboard Intel Pro/100 NIC.
It only happens on the first connection attempt. A TCP_SYN packet
is sent to the correct IP address (eliminating a DNS issue) but
the connection still times out.
If I close the browser and re-open it to the same URL, then the
connection is established! (same thing on a another clean install of XP)
Also, there is no problem with ICMP after a reboot. Issuing an echo-request
is always succesfull on the first attempt from the command line.
It seems to be TCP/IP related and that's why it would help me to have a
third party NIC that would work, which would help me to troubleshoot the
problem.
I haven't tried XP Pro SP2 yet. I wonder if that would solve the issue,
I don't see why it would ...
--
blackjack