Can't connect PC with router

[Henri]

Please forgive any wrong or bad english.

I have a problem getting my PC connected with a newly bought wireless
modem/router (SMC 7804WBRA). I have an ADSL connection and used an USB modem
(Speedtouch 330). My networkcard is: SiS 900-Based PCI Fast Ethernet
Adapter. I've disabled another networkdevice (1394 IEEE). The system runs on
XP Home SP1. By the way: I did disable the firewall (PC Cillin).

I can't get the networkcard to connect with the router. I've set properties
to obtain IP and DNS automaticly and ran the program WinsockXPFix. Then I
gave the command ipconfig/renew. The answer (translated): "An error occurred
bu renewing this interface: <name interface> (access denied)."

The IP-adres (was 0.0.0.0) then changed to 169.254.0.0 and the subnet to
255.255.0.0. This indicates that the DHCP-server could not be reached.

The router does function, because I could get things going (including
accessing the internet) on an other PC running on W98SE (after a fully new
install). I don't feel much for reïnstalling XP.

I am a bit tiered from searching the enourmes amount of information on the
internet. Could anyone please give me the solution for my problem?

Many thanks in advance.



Henri H.

 

[Chuck]

Please forgive any wrong or bad english.

I have a problem getting my PC connected with a newly bought wireless
modem/router (SMC 7804WBRA). I have an ADSL connection and used an USB modem
(Speedtouch 330). My networkcard is: SiS 900-Based PCI Fast Ethernet
Adapter. I've disabled another networkdevice (1394 IEEE). The system runs on
XP Home SP1. By the way: I did disable the firewall (PC Cillin).

I can't get the networkcard to connect with the router. I've set properties
to obtain IP and DNS automaticly and ran the program WinsockXPFix. Then I
gave the command ipconfig/renew. The answer (translated): "An error occurred
bu renewing this interface: <name interface> (access denied)."

The IP-adres (was 0.0.0.0) then changed to 169.254.0.0 and the subnet to
255.255.0.0. This indicates that the DHCP-server could not be reached.

The router does function, because I could get things going (including
accessing the internet) on an other PC running on W98SE (after a fully new
install). I don't feel much for reïnstalling XP.

I am a bit tiered from searching the enourmes amount of information on the
internet. Could anyone please give me the solution for my problem?

Many thanks in advance.



Henri H.

Henri,

Can you run the Wireless Network Connection wizard on the problem computer?
Does the wireless network associated with the router show up in the Available
wireless networks list? Do you observe any errors from the problem computer
when trying to associate with the router wireless network? How about the router
log - any clues there?

How far away is the problem computer when trying to connect with the router?
How about the Win98 computer?

 

[spin0650]

Chuck,

Thanks for your reply, but it will not take me further, because I have not
been compleet in my description. Sorry. The router is connected with a cable
wich came with the router (also was the other PC (W98SE) when testing and
things worked). So I asume there is nothing wrong with the cable or the
router. I want to use the router connected using a cable to the PC with XP
and the PC with W98SE wireless on a remote destination. The problem is that
the networkcard in de XP-machine can not or will not - while using a cable -
connect to the router. Pinging on the routers IP (192.168.2.1) gives a time
out.

Henri

 

[Chuck]

Chuck,

Thanks for your reply, but it will not take me further, because I have not
been compleet in my description. Sorry. The router is connected with a cable
wich came with the router (also was the other PC (W98SE) when testing and
things worked). So I asume there is nothing wrong with the cable or the
router. I want to use the router connected using a cable to the PC with XP
and the PC with W98SE wireless on a remote destination. The problem is that
the networkcard in de XP-machine can not or will not - while using a cable -
connect to the router. Pinging on the routers IP (192.168.2.1) gives a time
out.

Henri

Henri,

Pinging the router, if no ip address is on the network card, won't work. Good
try though.

Things to check, in general.
1) Logical connectivity. LSP / Winsock or TCP/IP on the WinXP computer.
2) Physical connectivity. Bad network card, cable, or router port.
3) DHCP server on router. Either not working, or configured to ignore the
WinXP computer.

You ran WinsockXPFix. How about LSP-Fix <http://www.cexx.org/lspfix.htm> or
WinsockFix <http://www.tacktech.com/display.cfm?ttid=257>?

How about you reset TCP/IP?
http://support.microsoft.com/?id=299357

Start - Run - "cmd". Type "netsh int ip reset c:\netsh.txt" into the command
window.

Just to clarify, when you connect The WinXP computer, you're using the same
cable and router port that you successfully used with the Win98 computer.

Has the WinXP computer ever successfully connected to anything? Have you run
the hardware diagnostics for the network card? Have you loaded the correct /
latest drivers for the card? What results do you get from pinging 127.0.0.1?

If you manually assign an ip address to the card, say 192.168.2.7 (mask
255.255.255.0), what do you get from pinging the router?

Any clues on the router? When you connect the WinXP computer, do the router
status lights reflect a connection? Anything in the router log?

 

[Henri]

Hello Chuck,

Guess what ..........................it's working!!!!
I don't know what exactly did the trick (probobly the new drivers), but this
post is mailed using my router. Even the second computer (W98) is already
wireless connected. I think the new drivers were the answer to my problem.
These are my latest actions:
As before giving the "netsh" command, folowed by "ipconfig/release" and
"ipconfig/renew" didn't change anything. WinsockFix turned out to be the
same as WinsockXPFix, wich I previously unsuccessfull have used. Now it also
didn't make any difference. I ran LSP-Fix. Result: No namespace provider
entries or protocol provider entries were removed or renumbered. I didn't
dare using the advanced options (to dangerous for a non-specialist like
myself).
I downloaded and installed the newest drivers for SiS900, where the card is
Sis900 based. Then (a hint I've read before on a forum) I pushed the
reset-button, powered off the router for a few seconds and the "miracle"
happened: I was able to access the set-up from the router. And it's working
like it should, besides perhaps finetuning settings.
Thank you very, very much for your time and effort to help me and give me
the directions for solving the problem I was facing.

Henri Hoenderboom (The Netherlands)

 

[Chuck]

Hello Chuck,

Guess what ..........................it's working!!!!
I don't know what exactly did the trick (probobly the new drivers), but this
post is mailed using my router. Even the second computer (W98) is already
wireless connected. I think the new drivers were the answer to my problem.
These are my latest actions:
As before giving the "netsh" command, folowed by "ipconfig/release" and
"ipconfig/renew" didn't change anything. WinsockFix turned out to be the
same as WinsockXPFix, wich I previously unsuccessfull have used. Now it also
didn't make any difference. I ran LSP-Fix. Result: No namespace provider
entries or protocol provider entries were removed or renumbered. I didn't
dare using the advanced options (to dangerous for a non-specialist like
myself).
I downloaded and installed the newest drivers for SiS900, where the card is
Sis900 based. Then (a hint I've read before on a forum) I pushed the
reset-button, powered off the router for a few seconds and the "miracle"
happened: I was able to access the set-up from the router. And it's working
like it should, besides perhaps finetuning settings.
Thank you very, very much for your time and effort to help me and give me
the directions for solving the problem I was facing.

Henri Hoenderboom (The Netherlands)

Henri,

Aright! Excellent news! Yes, the driver update would be my guess too. I've
not to date used the advanced settings in LSP-Fix either, but you didn't need to
anyway.

Thanks for the feedback, and stay safe.