17 replies
by jboss
by jkey
I tried this but it didn't help.
Thank you.
by jkey
by jkey
by naamor
Have you confirmed that the NIC is functioning properly, or that is is not disabled in the BIOS?
If this is set properly, try re-installing the NIC drivers.
You could try putting another NIC in and seeing that works.
Did anything change between when it was working and when it stopped? Did you by chance install a firewall (Zonealarm, Blackice etc) if so is it configured properly?
by jkey
by rcom
Where is the 169.254.x.x IP address shown. Is it in the TCP/IP properties? If it's in the properties then you're modem nay not be using DHCP. If your sure it's using DHCP get rid of the IP address and subnet mask. Plus double check DNS settings. There will be 2 IP addresses for the DNS server. Check to make sure those are correct.
Can you ping internal 127.0.0.1. or any other IPs. to run the ping command select run then just type in ping 127.0.0.1 then hit enter. If it shows a connection then at least there is commnication going on. But if it shows connection timed out then there's a internal problem.
McAfee firewall will stop the connection if not setup correctly it used to work so we can assume that if that's the reason somethinghas changed. To test stop the CPDCLNT service and see if you can get online. There's been times when for whatever reason firewall will dump the settings. So you need to run firewall and open the settings for the network adapter and select allow DHCP. Disable Netbios over TCP/IP. Also make sure that Internet Explorer or whatever browser you use has access to the internet in the allowed programs in Firewall. If the firewall settings in XP are enabled that may also be stopping the connection. You can run the uninstaller in control panel add remove programs for Mcafee Firewall and select repair. The same can be done for Internet Explorer if that's your browser of choice.
Also make sure you have the latest dat file boot to safe mode andscan for viruses. Run msconfig.exe and check in the startup section to make sure nothing suspicious isn't being loaded.
Write down your settings then unload all TCP/IP networking properties from the connection. Then re-install. This will reinstall a fresh winsock.
by jkey
by vanquisher
Hey JKEY,
This may help you out...
START > RUN > Type in "cmd" > ENTER
Type in, at the command prompt, "ipconfig /all"
/all
Displays the full TCP/IP configuration for all adapters. Without this parameter, ipconfig displays only the IP address, subnet mask, and default gateway values for each adapter. Adapters can represent physical interfaces, such as installed network adapters, or logical interfaces, such as dial-up connections.
Now that you have this info...
Type in "ipconfig /release" > ENTER
/release [Adapter]
Sends a DHCPRELEASE message to the DHCP server to release the current DHCP configuration and discard the IP address configuration for either all adapters (if an adapter is not specified) or for a specific adapter if the Adapter parameter is included. This parameter disables TCP/IP for adapters configured to obtain an IP address automatically. To specify an adapter name, type the adapter name that appears when you use ipconfig without parameters.
Type in "ipconfig /renew" > ENTER
/renew [Adapter]
Renews DHCP configuration for all adapters (if an adapter is not specified) or for a specific adapter if the Adapter parameter is included. This parameter is available only on computers with adapters that are configured to obtain an IP address automatically. To specify an adapter name, type the adapter name that appears when you use ipconfig without parameters.
Now check to see if you can connect...
by jkey
I tried to do this originally but it didn't help. I believe that the problem is caused by McAfee. I believe it's firewall blocked all of my extenal ports. I tried to unblock them manually without success.
Thanks.
by vanquisher
by jkey
by jkey
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending