• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Quick question: Why is XP doing this??

M

MikeMike

Lifer
i have wireless and wired, they both are currently connected, but XP has decided to "lose" my wired connection and not even show my ONBOARD network interface, just my wireless, and yes it is enabled in Bios...

any hints/ideas on how to get my wired to work since i am getting high pings?
 
use the command ipconfig and ipconfig/all

do you have an IP address on the wired?

If not then something is up. Do you have a link light on your wired?

XP is actually pretty good about preferring a wired connection to a wireless.

Has it always worked?
 
Originally posted by: spidey07
use the command ipconfig and ipconfig/all

do you have an IP address on the wired?no

If not then something is up. Do you have a link light on your wired?yes

XP is actually pretty good about preferring a wired connection to a wireless.

Has it always worked? from what i know yes, but maybe it shuts off when wireless catches a signal?
Click to expand...

nothing changes when i disable wireless either.

 
if you disable the wireless can you still communicate?

If so then post a "route print" and "ipconfig/all" from a command prompt. If you are using internal addressing like 192.168. and 10. and 172.16-31. then no need to hide your IP.
 
Originally posted by: spidey07
if you disable the wireless can you still communicate?

If so then post a "route print" and "ipconfig/all" from a command prompt. If you are using internal addressing like 192.168. and 10. and 172.16-31. then no need to hide your IP.
Click to expand...

no, when i disabled it my aim went byebye and wouldnt reconnect, and i dont believe i could post, gimme a second to retry.
 
well then something is up on the wired side and XP is doing what it is supposed to do.

you can verify with "ipconfig" from a command prompt to see if you are getting an IP address.

If you aren't then we need to look at why you can't talk, meaning...are you getting a link light on the card? (disclaimer - just having a link light doesn't mean all is well, it's just a start) What is on the other end of your wired connection? your own network gear or somebody elses? Do you get a link light on the other side?
 
Originally posted by: spidey07
well then something is up on the wired side and XP is doing what it is supposed to do.

you can verify with "ipconfig" from a command prompt to see if you are getting an IP address.

If you aren't then we need to look at why you can't talk, meaning...are you getting a link light on the card? (disclaimer - just having a link light doesn't mean all is well, it's just a start) What is on the other end of your wired connection? your own network gear or somebody elses? Do you get a link light on the other side?
Click to expand...

WRTG54 on the router, i think the issue is on the Comp, unless theres only one light color, its yellow on the mobo.

arg, when it says "patch" cable.. is that an Xover cable, or is it regular, i forget.
 
that would be a regular cable attached to one of the LAN ports on your router.

Crossover is only used when two end node (NICs) or two network gear (switches) need to be connected.
 
Originally posted by: spidey07
that would be a regular cable attached to one of the LAN ports on your router.
Click to expand...

i flipped up cables and nothing new other than a diff light on the router lit up. lol

ipconfig/all still shows the same
 
well you still haven't posted what your IPconfig is. If it is 169.x.x.x then you are not getting an IP from your router and most likely have a cabling problem.

are these store bought patch cables?
 
Originally posted by: spidey07
well you still haven't posted what your IPconfig is. If it is 169.x.x.x then you are not getting an IP from your router and most likely have a cabling problem.

are these store bought patch cables?
Click to expand...

yup, they have worked for the past 3 years +.

how do i get cmd prompt to spit out a notepad version of ipconfig/all

(im seeing 128.128.0.1 and what not)
 
start/run

cmd

click enter

you now have a command prompt

click the button on the window in the upper left and select 'edit/mark', highlight that text, press enter to copy and then paste into your post.

 
Originally posted by: spidey07
start/run

cmd

click enter

you now have a command prompt

click the button on the window in the upper left and select 'edit/mark', highlight that text, press enter to copy and then paste into your post.
Click to expand...

it was the edit/mark part i didnt know how to do/didnt look for.

Windows IP Configuration

Host Name . . . . . . . . . . . . : steve-o
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : wan

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : wan
Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter
Physical Address. . . . . . . . . : 00-12-17-68-A5-A1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.103
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Tuesday, March 14, 2006 9:24:21 PM
Lease Expires . . . . . . . . . . : Wednesday, March 15, 2006 9:24:21 PM
Click to expand...

thats all i get with ipconfig/all
 
looks like you don't have drivers loaded for you nic. windows is totally unaware that you have a wired network card.

reboot or check device manager and make sure your NIC isn't disabled.

sorry that's about the best I can do. I don't know PCs.
 
Originally posted by: spidey07
looks like you don't have drivers loaded for you nic. windows is totally unaware that you have a wired network card.

reboot or check device manager and make sure your NIC isn't disabled.

sorry that's about the best I can do. I don't know PCs.
Click to expand...

yea, i know the NIC has worked multiple times before, so i think ill reboot.
 
In General, you can debug the Network Settings of a computer by following these steps.

Step One. Check the Network parameters in the Computer's Device Manager. Make sure that the Network Card drivers are installed correctly; i.e. there is No IRQ conflict, and No Ghost installation. http://www.ezlan.net/faq#ghost

Step Two. Verify Basic network setting in the OS: http://www.ezlan.net/Installing#verify If the above two Steps indicates that every thing looks good but functionally it does not work.

Step Three. Check (and repair if necessary) the Socket Layers, Winsock, and or refresh the TCP/IP Stack. http://www.ezlan.net/clean#refreshnet

:sun:
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top