low conductivity

[officemanager2]

Hi there: Been trying to get a desktop (garage) hooked up with a router in my house. I put the actual device in the slot that had the Cat 5 wire. This was the only input on the mother board that the device would be detected. But, it seems the computer is still trying to communicate through the ethernet adapter and not the d-link adapter. In my adventure I've come across the message that the "IP address you have entered is already assigned to "ethernet adapter name(it's long)" so how can I change the IP address to the d link wifi device. Currently I'm logged into the router but I cannot receive packets, only send them. I have the TCP/IP set up to use the 192 . .... IP address. When it is set to "Obtain an Ip address automatically" it gets low conductivity (yellow yield warning) but still no packets received (only sent). So if I input a 192 ... address I can log into the router, if I let the machine 'automatically' get the address I get low conductivity an still no packets. I'm sending this from a laptop on the same router that is working fine. One final thing to add is when I do ipconfig/all there is no DNS number. Not sure if why of if this matters, but it seems to be part of the problem. Any suggestions?

 

[jimbopalmer]

Which (if any) of these devices are wireless?
If this is wired, premade cable or self made ends?
If this is wireless, are you starting with no security?
At one point it sounds like you are reusing a PCI slot, are there other slots to try?

I tried to remain child-like, all I acheived was childish.

 

[officemanager2]

Hi: There are two other slots but they don't read the desktop adapter as present. I found it is only read in the bottom slot where the Ethernet Adapter was inserted into the mother board.

The Wifi adapter is a D-Link WA-2320

The security is already in place and that is working fine. Even now desktop is on an connected to the router, but no packets are being receive. This problem with packets not being received shows up a lot often tied into DHCP issues, but I haven't been able to figure out if that is the issue or something else. The wifi in the desktop is definitely on the router it is meant to connected with.

 

[edfair]

Delete both of the devices from network properties or device manager or whatever then let it be detected by a reboot.

You might want to check the documentation to see if the software needs to be installed before the wireless device.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[jimbopalmer]

Try the wireless without security, then add security once you have it working.

I tried to remain child-like, all I acheived was childish.

 

[officemanager2]

Hi There: I've tried removing all the fire walls from the computer and still no luck. What I discovered last night was that the computer does not have ipv6 so I'm looking to get that reinstalled. The operating system is XP. As I mentioned before lots of people have problems with packets not being received but rarely is a solution posted. The computer is at a different location then I'm at right now but I'll be back working on it at the end of the day. I'll post the ipconfig at that point and maybe that will provide a direction to the answer.