Unable to establish home network after reinstall of OS on XPS Gen4

TomAZ

unread,

Jan 4, 2010, 6:21:56 PM1/4/10

to

I think this is the wrong forum for this question but can't get an
answer on windows forum (yet).

I had a fatal error in Windows XP MCE SP3 last month.
Ran chkdsk /r to repair and get back into windows.
Did a repair install from original OS DVD that came with machine (Dell
XPS4).
Applied all the security fixes to get back to currency.
Since doing his, I can't access network places or create network
successfully. All other computers on my home network are still
accessible to each other.

Details: The affected computer is xps home desktop connected to
linksys
WRT54gs router and motorola modem. None of my router settings have
been changed and I can still log into it. I am able to access
internet from this computer but when I try to view workgroup computers
I get the "workgroupname is not accessible. You might not have
permission to use this network resource. etc." message.
If I go through the process of trying to set up a home office network
the process completes but nothing shows up. The other computers in
house are XP laptops. They can see each other on the workgroup but
can't see the affected desktop. My firewall on the desktop is set up
to allow the network, but to test, I have turned off the firewall
(McAfee) and have made sure that Windows firewall is not on.

I'm thinking that there is a missing or corrupted windows component
but I haven't been able to yield specific enough information with any
search.

Thanks in advance if anyone has an idea of what might have gone wrong
of if there is a better place to get assistance.

BillW50

unread,

Jan 4, 2010, 6:34:05 PM1/4/10

to

In news:qpt4k5t3894jopjn5...@4ax.com,
TomAZ typed on Mon, 04 Jan 2010 16:21:56 -0700:

> Did a repair install from original OS DVD that came with machine (Dell
> XPS4).

I think this is your problem. Repair installs are great as they can save
your bacon. But they don't work 100% of the time. I think you might be
better off doing a fresh install. Although you can try to fix this. And
maybe others might have a solution for you. But in the end, I think this
is the best way to go.

And before ever doing a chkdsk /r, I would make a backup. As chkdsk has
screwed up files in the past. I don't know, like 1 or 2% of the time
anyway. <sigh>

--
Bill
Gateway MX6124 ('06 era) 2 of 3 - Windows XP SP3

Father Justin

unread,

Jan 4, 2010, 6:39:05 PM1/4/10

to

I think running a complete check on the hard drive is a good idea as well.
Something caused this "fatal error" and sometimes the hard drive can be
the culprit.
Also a RAM check might be in order.
http://www.memtest.org/

Microsoft's memory checker is shit - don't use it.
http://technet.microsoft.com/en-us/magazine/2008.09.utilityspotlight.aspx?pr=blog

--
http://www.vatican.va

TomAZ

unread,

Jan 4, 2010, 7:34:56 PM1/4/10

to

Thanks for the response and suggestions. I did back up before doing
the checkdisk and have been regularly backing up since restore. I
got a replacement drive to do do a full reinstall as soon as I have
time to go through the hassle. I think (per another response) that
there is problem with drive as I've also had some odd write errors
since restoring. I was hoping to get networking back and limp along
until building from scratch. Thanks again.

TomAZ

unread,

Jan 4, 2010, 7:36:07 PM1/4/10

to

Thanks for response. Will try memory check. I assume by checking
hard drive (drives actually, I forgot to mention that this is dual
drive RAID 0 system) you mean running chkdsk again?

Ben Myers

unread,

Jan 4, 2010, 11:13:35 PM1/4/10

to

I would go even further. After backing up all the important data from
the computer, I would run the hard drive manufacturer's diagnostics (not
the skimpy Dell diagnostics! NOT EVER Microsoft's diagnostics for
cretins and by cretins!) I would also run HDAT2 to examine the drive's
SMART data to see if there are any (literally) red flags like
reallocated sectors, sectors waiting to be reallocated but not done yet,
etc. If the drive is failing, trying to use it is a losing cause.

Let's go a step further. Buy another drive. They are cheap. Install
Windows on it, plus all your software applications and the myriad of
Windows updates, patches, corrections, bubble gum, rubber bands and
paper clips needed to hold Windows together. Then scavenge all your
data from the original drive connected up as a secondary drive for which
you may need another drive cable since it is probably SATA.

You may end up buying a replacement drive anyway, if the original is
hosed... Ben Myers

Ben Myers

unread,

Jan 4, 2010, 11:16:53 PM1/4/10

to

Chkdsk is a piece of manure. Manufacturer's diagnostics plus HDAT2,
both free downloads... Ben Myers

OG

unread,

Jan 5, 2010, 7:19:56 AM1/5/10

to

"TomAZ" <t...@home.org> wrote in message
news:qpt4k5t3894jopjn5...@4ax.com...

>I think this is the wrong forum for this question but can't get an
> answer on windows forum (yet).
>
> I had a fatal error in Windows XP MCE SP3 last month.
> Ran chkdsk /r to repair and get back into windows.
> Did a repair install from original OS DVD that came with machine (Dell
> XPS4).
> Applied all the security fixes to get back to currency.
> Since doing his, I can't access network places or create network
> successfully. All other computers on my home network are still
> accessible to each other.
>

Are you getting any networking on it? If not try running WinSock XP Fix.
http://www.snapfiles.com/get/winsockxpfix.html

Christopher Muto

unread,

Jan 5, 2010, 9:44:03 AM1/5/10

to

i wonder if this issue is as simple as the rebuilt computer having a
different workgroup name than the others. your repair/install may have
rebuilt the networking and set the workgroup name back to the default
'workgroup' whereas your other machines that are presumably windows xp
home have the workgroup name set to 'mshome'. or you could try this
microsoft networking fix... http://support.microsoft.com/kb/903267

RnR

unread,

Jan 5, 2010, 5:49:45 PM1/5/10

to

From my own experience not too long ago I'd agree with the missing or
corrupted windows components. That said, like some others, I'd do a
new reinstall because the time it will take to find and fix will be
longer. Of course if you have a good backup, that's the way to go.
And of course if you suspect your drive is bad, do this on a good
drive.

TomAZ

unread,

Jan 5, 2010, 7:38:48 PM1/5/10

to

Thanks for the response. Workgroup name wasn't changed but following
on from your comment, I changed it to a different name, then removed
all shared directories, then changed it back to original name, readded
shares and voila was now able to see shares on other computers.
Weirdly, in My Network Places on the desktop I can see all network
shared resources but if I click "View workgroup computers" I still get
the error message. But this is good enough for now. I will
eventually replace drive and do clean install. Thanks again.

TomAZ

unread,

Jan 5, 2010, 7:40:29 PM1/5/10

to

Thanks to all for the advice. Got this working in crippled fashion
after another disk check and some tinkering with shares. I agree that
there is something corrupted and will eventually do new install on
clean drive.

Christopher Muto

unread,

Jan 5, 2010, 8:30:15 PM1/5/10

to

excellent. i haven't seen it since windows 98, but that really brings
back memories of how the network applet reported one thing but was in
reality doing something else. i would be inclined to delete the entire
network stack, restart the machine and rebuild it. something is
definitely screwy in there. but congrats on getting to the bottom of it.