Ethernet adapter/modem issues

Author
Discussion

hornet

Original Poster:

6,333 posts

251 months

Saturday 8th April 2006
quotequote all
Right, any gurus around? I'm trying to get a new ADSL modem working, having just put an ethernet adapter PCI card in the computer, but I'm having problems. The lights on the modem and network card are all present and correct, but when I come to the "configure modem using web broswer" (http://192.168.1.1) bit, nothing happens - no configuration window, nothing. Also, unless I'm being blone, if the network card and driver are installed ok, I should have a "Local Area Network" option appear in the Network Connections window, which I haven't. I've tried looking in device manager, and there's no sign of either modem or NIC. Obvious answer is that the card isn't in properly, but then if that were the case, surely the activity lights wouldn't be illuminated?

Computer is 1.6ghz P4, XP Pro (for now), modem is D-Link DSL-300T, ethernet adapter card is D-Link 530TX, user is confused...

GreenV8S

30,210 posts

285 months

Saturday 8th April 2006
quotequote all
Modern systems should recognise the new hardware as soon as you reboot, but if yours has missed it for some reason you may need to go through the 'add/remove hardware' wizard.

hornet

Original Poster:

6,333 posts

251 months

Saturday 8th April 2006
quotequote all
Right, progress...network card is now installed properly and I have a High Speed Internet/LAN option in Network Settings. Still can't use the web browser (Firefox or IE) to launch the modem configuration though. The network card is trying to acquire an IP address, but doesn't seem to be getting anywhere.

GreenV8S

30,210 posts

285 months

Saturday 8th April 2006
quotequote all
Are you using a crossover ethernet cable?

hornet

Original Poster:

6,333 posts

251 months

Saturday 8th April 2006
quotequote all
Er, pass...just using the cable which came boxed with the modem.

hornet

Original Poster:

6,333 posts

251 months

Monday 10th April 2006
quotequote all
Bump...

Can someone please confirm if I'm understanding this correctly?

After hours of trawling around online, I'm led to believe that because my PC (2001 vintage) didn't originally have a network card, there's probably an issue with the port on the card I've installed and the port on the modem being arse about face as far as the regular (supplied with modem) ethernet cable is concerned, and in true Star Trek fashion, by using a crossover cable to reverse the polarity, everything should work?

_dan_

2,388 posts

280 months

Monday 10th April 2006
quotequote all
Check your DHCP service it turned on (control panel - administrative tools - services)

Also check the TCP/IP settings in the network settings panel and make sure it's set to obtain an IP address automatically.

You could try also opening a command prompt window and type NETSH INT IP RESET this resets the TCP/IP protocol (only in XP I think)

Try uninstalling the NIC card (remove drivers, take out card, reboot, shutdown, put card back in, reinstall drivers)

See if any of that has made any difference.

Zad

12,704 posts

237 months

Monday 10th April 2006
quotequote all
Crossover cables are only used to connect two pieces of equipment of the same type. e.g. PC to PC or Hub to Hub. Connecting your Ethernet card to your modem/router should be done with a standard straight through cable.

You aren't trying to connect this whilst still connected to the net by other means are you? That would screw up the routing and really confuse it.

ErnestM

11,615 posts

268 months

Monday 10th April 2006
quotequote all
Make your NIC card's IP static (192.168.1.5 would be good just to avoid any issues subnet mask 255.255.255.0 - gateway 192.168.1.1)

Try it then...

ErnestM

PS: No crossover cable...

hornet

Original Poster:

6,333 posts

251 months

Tuesday 11th April 2006
quotequote all
_dan_ said:
Check your DHCP service it turned on (control panel - administrative tools - services)


"Could not start DHCP Client service on local computer"
Error 1068: The dependency serive or group failed to start

_dan_ said:

Also check the TCP/IP settings in the network settings panel and make sure it's set to obtain an IP address automatically.


Already done that, although doesn't that contradict the other advice about setting a static IP?

_dan_ said:

You could try also opening a command prompt window and type NETSH INT IP RESET this resets the TCP/IP protocol (only in XP I think)

Try uninstalling the NIC card (remove drivers, take out card, reboot, shutdown, put card back in, reinstall drivers)

See if any of that has made any difference.


Not trying to do this while connected by the way! Case of unplug the USB modem, shut down, connect ethernet cable and modem, reboot. All the lights are on, but nobody is home...

_dan_

2,388 posts

280 months

Tuesday 11th April 2006
quotequote all
hornet said:
_dan_ said:
Check your DHCP service it turned on (control panel - administrative tools - services)


"Could not start DHCP Client service on local computer"
Error 1068: The dependency serive or group failed to start


This isn't a particually good sign as DHCP is the service that controls assigning you an IP address I believe. I'll dig around the web and see if I can find anything.

_dan_

2,388 posts

280 months

Tuesday 11th April 2006
quotequote all
Might be worth you have a read of the below page

http://windowsxp.mvps.org/dhcp.htm

hornet

Original Poster:

6,333 posts

251 months

Tuesday 11th April 2006
quotequote all
The power of PH!

Useful info, thanks...an Easter weekend of geekery beckons. Still, I enjoy learning this stuff, so it's all useful.

malman

2,258 posts

260 months

Tuesday 11th April 2006
quotequote all


right click local area connection in network connections and look at status does it say connected? Click on properties make sure the name specified at the top corresponds to your new NIC

does it say what speed its connected and for how long and packet counts?

If you set the IP to the static above you should be able to open a command prompt and type ipconfig /all

This will confirm your settings and give other useful info. In the command prompt you should be able to ping your own address eg

ping 192.168.1.5

you should get 4 replies - try ping to the router address what happens? any error?

>> Edited by malman on Tuesday 11th April 15:28

hornet

Original Poster:

6,333 posts

251 months

Friday 14th April 2006
quotequote all
Right, back on the old connection....

Progress of sorts, in that the network card is now saying it's connected and I've followed the setup instructions for the modem. However, now I have a new problem...neither Firefox nor IE will give me web pages. All I get is a popup prompting for a network connection, showing the USB one I'm using at the moment and some old dial-up connections I really ought to delete. The network connection window in XP is showing the LAN and saying it's up and running, but neither browser is getting through. Also, noticed that the NIC still says "connected" when I take the ADSL line out of the modem, so not sure what that's about?

Here's the NIC status, if that helps :-

Physical Address: (some letters/numbers)
IP Address: 192.168.1.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DHCP Server: 192.168.1.1
Lease Obtained: 14/04/2006 01:07:26
Lease Expires: 14/04/2006 01:08:26
DNS Server: 192.168.1.1
WINS Server:

Help! This is driving me mad...

aldi

9,243 posts

238 months

Friday 14th April 2006
quotequote all
Control Pannel, Internet Options, Connections, 'Never Dial', OK.

HTH
neil

GreenV8S

30,210 posts

285 months

Friday 14th April 2006
quotequote all
If you have a LAN connection to an ADSL router then you don't need to use dial-up. From the sound of it, your Internet Connection properties have been set to always dial a connection. Change it to 'never dial a connection' and see if that helps.

Also try pinging the router and see if you get a reply e.g.

> ping 192.168.1.1

hornet

Original Poster:

6,333 posts

251 months

Friday 14th April 2006
quotequote all
You beauty

Really should have occured to check the "never dial a connection" setting, but I'd somehow convinced myself it would be more complicated than that.