posted on Oct, 3 2006 @ 11:41 AM
Just a thought but I have run across instances where XP after a clean build has used an incorrect network driver getting the chip ID right but not the
specific vendor implimentation (Macronix instead of SOHware or Realtek or something like that)... the Macronix driver would ping and give all
semblance of normalcy but no Net and no LAN. If you need NetBEUI (for machine to machine look in the valueadd\msft\net\netbeui folder on the XP
CD... it works if you copy over the nbf.sys and NETNBF.INF to the specs in NetBEUI.txt.
Maybe see what the NIC is and try and get a fresh driver... all the other recommendations sound fine. BTW: there are significant firmware upgrades for
some routers depending on the harware and firmware revisions... look yours up.
The default IP for that router is 192.168.0.1 check the manual.
Cords (RJ-45) can sometines be a hassle same with individual LAN connectoin points on routers... try a different LAN port and a known good cable... if
all else fails you might consider uninstalling and re-installing TCP/IP... that used to fix stuff on earlier OS's pretty good but I've never had any
trouble to speak of with TCP in MS XP pro...
Please be aware that sharing a whole hard drive from it's root can be more risky that sharing a discreet folder on a hard drive especially on an OS
drive . Perhaps use a lower level directory as a share say sommething like C:\temp.
You can find the manual and other stuff about your router at the following link:
Let us know how it works out.
[edit on 3-10-2006 by V Kaminski]