Still need an MVP answer for XP Pro file share

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

I cant access shares after running critical updates on the
XP machine. I could before. ICF is turned off. Now I get
promted for a username and password, but nothing works.
XP can see shares on all other machines (2000 and 98)but
they cant see the XP shares. All machines have the same
admin user and password.
I have ran the OS repair and reinstalled SP1 and checked
ICF again. Didnt do any good
 
Mike,

Are you using Simple File Sharing and disabled Guest account [in case?]. For faster and accurate response, you may post this in Networking groups.

--
Ramesh - Microsoft MVP
http://www.mvps.org/sramesh2k


I cant access shares after running critical updates on the
XP machine. I could before. ICF is turned off. Now I get
promted for a username and password, but nothing works.
XP can see shares on all other machines (2000 and 98)but
they cant see the XP shares. All machines have the same
admin user and password.
I have ran the OS repair and reinstalled SP1 and checked
ICF again. Didnt do any good
 
I am using simple sharing but the guest account is not
disabled. I looked at the fix described by PA Bear and
this has nothing to do with web sharing.
-----Original Message-----
Mike,

Are you using Simple File Sharing and disabled Guest
account [in case?]. For faster and accurate response, you
may post this in Networking groups.
--
Ramesh - Microsoft MVP
http://www.mvps.org/sramesh2k


"Mike" <[email protected]> wrote in
message news:[email protected]...
 
I cant access shares after running critical updates on the
XP machine. I could before. ICF is turned off. Now I get
promted for a username and password, but nothing works.
XP can see shares on all other machines (2000 and 98)but
they cant see the XP shares. All machines have the same
admin user and password.
I have ran the OS repair and reinstalled SP1 and checked
ICF again. Didnt do any good

Realize that this is a peer support group and it takes time for posts
to propogate through the system. Being impatient is considered rude
and not generally well regarded. Waiting less than 24 hours then
complaining that you are still waiting is just getting even more rude
(and you barely waited what, 6 hours?).

Oh, and BTW, people answered your last post. I suggest you go back
and look before blathering that nobody is helping you.
 
I cant access shares after running critical updates on the
XP machine. I could before. ICF is turned off. Now I get
promted for a username and password, but nothing works.
XP can see shares on all other machines (2000 and 98)but
they cant see the XP shares. All machines have the same
admin user and password.
I have ran the OS repair and reinstalled SP1 and checked
ICF again. Didnt do any good

You can't access ANYTHING from the xp machine on that machine?


Have a nice week...

Trent

What do you call a smart blonde?
A golden retriever.
 
Thank you for your rude reply.
I have read all of the replys to no avail.
The patch referred by PA Bear pertains to web sharing
which is not my situation.
This is the only viable venue to address issues without
having to pay for it when Microsoft screws up.
Microsoft refers us to this site and we depend on the
MVP's to answer questions as they have access to resources
that we dont. I do my testing of updates at home to screen
out problems. I also administer a 500 node WAN. I may seem
impatient but I need an answer and this would not be the
first time Microsoft has failed to provide one in a timely
manner. I recently found out the hard way that Publisher
2002 will not open Pub 2000 files and Microsoft has no
intentions of fixing it. Now I get to explain that to 150
users.
 
The XP machine shows up in computers near me but can not
be accessed without a username and password. I use the
same admin user and password for all machines and it
doesnt work. I am using simple file sharing and the guest
account is enabled. The shares worked fine before
installing the updates from microsoft.
 
Mike said:
Thank you for your rude reply.
I have read all of the replys to no avail.
The patch referred by PA Bear pertains to web sharing
which is not my situation.
This is the only viable venue to address issues without
having to pay for it when Microsoft screws up.
Microsoft refers us to this site and we depend on the
MVP's to answer questions as they have access to resources
that we dont. I do my testing of updates at home to screen
out problems. I also administer a 500 node WAN. I may seem
impatient but I need an answer and this would not be the
first time Microsoft has failed to provide one in a timely
manner. I recently found out the hard way that Publisher
2002 will not open Pub 2000 files and Microsoft has no
intentions of fixing it. Now I get to explain that to 150
users.

Mike - Let's get this completely clear - We MVP's are completely
volunteers. We do not get paid for our time here. We do not work for
Microsoft. Every one of us has our own reasons for posting, although I
think you'll find that most of us are like me, posting because 1) the
knowledge gained will help my clients; 2) the knowledge gained will
help me; 3) I like helping people. While MS recognizes that the MVP's
are a good tech support resource for them and they do try to provide us
with as much information as possible so we can help people, most of our
knowledge comes from our life-experiences in fixing computers,
gathering information from many sources available to everyone (Google,
MSKB, etc.), and networking with each other and other techs in our
lives.

If you didn't get an answer from one of us (or anyone else, for that
matter), it's because either the person who might know isn't reading
this ng right now and/or no one *knows* the answer. I understand you're
frustrated and I sympathize. However, no one is purposely withholding
information from you; additionally, no one in this ng *owes* you an
answer, either. It is very difficult to troubleshoot subtle problems
like the one you've described in a Usenet posting. Sometimes the best
thing to do is call someone in to take a look at things. This is not
impugning your skills - sometimes a fresh pair of eyes will catch
something you didn't. I'm sorry I don't have the magic answer for you,
and wish you good luck.

Malke
 
Malke said:
Mike - Let's get this completely clear - We MVP's are completely
volunteers. We do not get paid for our time here. We do not work for
Microsoft. Every one of us has our own reasons for posting, although I
think you'll find that most of us are like me, posting because 1) the
knowledge gained will help my clients; 2) the knowledge gained will
help me; 3) I like helping people. While MS recognizes that the MVP's
are a good tech support resource for them and they do try to provide us
with as much information as possible so we can help people, most of our
knowledge comes from our life-experiences in fixing computers,
gathering information from many sources available to everyone (Google,
MSKB, etc.), and networking with each other and other techs in our
lives.

If you didn't get an answer from one of us (or anyone else, for that
matter), it's because either the person who might know isn't reading
this ng right now and/or no one *knows* the answer. I understand you're
frustrated and I sympathize. However, no one is purposely withholding
information from you; additionally, no one in this ng *owes* you an
answer, either. It is very difficult to troubleshoot subtle problems
like the one you've described in a Usenet posting. Sometimes the best
thing to do is call someone in to take a look at things. This is not
impugning your skills - sometimes a fresh pair of eyes will catch
something you didn't. I'm sorry I don't have the magic answer for you,
and wish you good luck.

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"


Well stated, and without rancor.................:-)
 
I had no intention of slamming the MVP's and if it was
taken that way I am sorry.
The last MVP to help me had access to people at Microsoft
and got answers for me off line. The service he provided
was exceptional even though the problem was not going to
be addressed by Microsoft. I figured all of you had
similar contacts. I also had no idea what your level of
participation was as it is not explained anywhere of note.
Please forgive my ignorance and keep up the good work you
do.
 
Mike said:
I had no intention of slamming the MVP's and if it was
taken that way I am sorry.
The last MVP to help me had access to people at Microsoft
and got answers for me off line. The service he provided
was exceptional even though the problem was not going to
be addressed by Microsoft. I figured all of you had
similar contacts. I also had no idea what your level of
participation was as it is not explained anywhere of note.
Please forgive my ignorance and keep up the good work you
do.

Thank you for the graceful reply, Mike.

Best of luck,

Malke
 
Mike said:
...we depend on the
MVP's to answer questions as they have access to resources
that we dont

We wish. /Some/ MVPs have established "inside" industry contacts over the
years but for the most part we use the very same resources which are
available to you and all users.

If you feel a recent update caused the problem, all you have to do to
confirm your suspicions is to go to Add/Remove Programs and Uninstall it.
If all is well after doing so, chances are the update /may/ have at least
contributed to the problem. If the problem persists, something else is to
blame (often PEBUAK).

To assure a clean install, your anti-virus application should be disabled
and /all/ other running processes closed before going to Windows Update and
when downloading/installing from any MS page.
--
Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE), AH VSOP

What You Should Know About the Mydoom Worm Variants:
Mydoom.A, Mydoom.B, and Mydoom.C (a.k.a. Doomjuice)
http://www.microsoft.com/security/antivirus/mydoom.asp

Before You Connect a New Computer to the Internet
http://www.cert.org/tech_tips/before_you_plug_in.html
 
The XP machine shows up in computers near me but can not
be accessed without a username and password. I use the
same admin user and password for all machines and it
doesnt work. I am using simple file sharing and the guest
account is enabled. The shares worked fine before
installing the updates from microsoft.

Here's a few ideas, Mike...you decide how good they are. lol

1. Go back to a restore point.

2. Uninstall the update.

3. Set up a new share.

4. Make sure the share name on your xp machine is the same as the log
off name you get on the pop-up when you click on Start.

Any idea what update it was?


Have a nice week...

Trent

What do you call a smart blonde?
A golden retriever.
 
On Mon, 16 Feb 2004 07:29:58 -0800, "Mike"
This is the only viable venue to address issues without
having to pay for it when Microsoft screws up.

That's as may be, but as usual, some else is paying for what looks
like your free lunch.
Microsoft refers us to this site and we depend on the
MVP's to answer questions as they have access to resources
that we dont.

Chances are you have access to most of the resources we do, via the
online knowledge base and so on. It's a bit like drinking from a fire
hydrant, I know - and if you are modem-bound, it's pretty grim.
I do my testing of updates at home to screen out problems.
I also administer a 500 node WAN. I may seem impatient
but I need an answer ...

I'm sure that 500-node WAN can cover the costs of paid 3rd-party
support, if that's what you need.
...and this would not be the first time Microsoft has
failed to provide one in a timely manner.

MS provides the "place" for these forums, not the content. Neither
they, nor the volunteers who assist here, are under any obligation to
you (or any other poster) whatsoever.
I recently found out the hard way that Publisher 2002
will not open Pub 2000 files and Microsoft has no
intentions of fixing it. Now I get to explain that to 150
users.

That's a big nasty! In fact, you've hit an important nail squarely on
the head - the whole issue of which versions of what will botch data
files for older versions is AFAIK quite poorly documented.

Which critical updates?

At what point are you password-prompted; when you start up XP, or when
you first access a share?

Are the XP systems using simple file sharing, or something more
baroque a la XP Pro?

Those steps will have thrown out your patches.

Put it this way; many of spend the day doing this sort of work for ppl
who pay us for it. Then we come home and pitch in on the newsgroups.
If that's 6hrs+ late, will we feel obliged to grovel for forgiveness?

I don't think so.

Anyway - sorry if my advice here is a bit general; it's a topic that's
outside what I usually do. More info on your LAN (i.e. are there any
domain servers, remote registries etc. involved?) would help, as info
on what patches you applied. I seem to remember an old patch that
beefed up the way passwords were stored, and this broke "remembered"
passwords - perhaps that's what's biting you here.

I might try taking passwords off the shares, then re-applying them.


-------------------- ----- ---- --- -- - - - -
Tip Of The Day:
To disable the 'Tip of the Day' feature...
 
I did all of that and I still have the problem.
As for which update it was I really dont know.
I have cable and like a dummy after SP1 I told it to
install everything Microsoft said it needed.
Im wondering if the TCP stack is fubar or something crazy
like that after reading that some people installed IPX and
got their shares working.
I will probably install a second instance of XP, move
profiles and give up. I had intended to use SUS for
updates at work and now Im worried about automating.
 
If you read my reply to Malke I have explained my
ignorance of this system.
As for money available for third party help, try working
for a Public Library, in addition the Library uses volume
licensing and because of that is not entitled to support
without paying for it.
Anyway, I have cable so like a dummy after installing SP1
I told it to install everything Microsoft said it needed.
So I dont know which one caused the problem.
Starting from network Places/computers near me/XP machine
I used to double click the XP machine and the shared files
would show up. Now I get prompted for a username and
password and no combination works(this is from a 2000 and
98 machine). From the XP machine I can follow the same
route to shares on the 2000 and 98 machines and everything
opens like it used to. \\xpmachine\c$ doesnt work either
even though I use the same admin and password on all
machines.
 
I did all of that and I still have the problem.
As for which update it was I really dont know.
I have cable and like a dummy after SP1 I told it to
install everything Microsoft said it needed.
Im wondering if the TCP stack is fubar or something crazy
like that after reading that some people installed IPX and
got their shares working.
I will probably install a second instance of XP, move
profiles and give up. I had intended to use SUS for
updates at work and now Im worried about automating.

I think you may have a different problem, Mike. I've kept current
with all the updates...as have thousands of other people. Not
everyone is having the problem that yer havin'. But, as I said
before...and as you know...xp is pretty flaky yet.

Are you absolutely yer logged in as administrator?...that the logout
on Start/ matches the settings for administrator?

Also, try logging into the Repair Console. See if that password
takes.

I think you said yer not running any Norton stuff...correct?

Good luck.


Have a nice week...

Trent

What do you call a smart blonde?
A golden retriever.
 
Positive about the admin even in the repair console, I use
InoculateIT/etrust
 
Anyway, I have cable so like a dummy after installing SP1
I told it to install everything Microsoft said it needed.
So I dont know which one caused the problem.
Starting from network Places/computers near me/XP machine
I used to double click the XP machine and the shared files
would show up.

I'm just curious why you do this.
Now I get prompted for a username and
password and no combination works(this is from a 2000 and
98 machine).

Are you saying that its the *XP* machine that you can't access?...from
the 2000 and 98 machines?
From the XP machine I can follow the same
route to shares on the 2000 and 98 machines and everything
opens like it used to. \\xpmachine\c$ doesnt work either
even though I use the same admin and password on all
machines.

On the xp machine, you need to have a user account set up that matches
the start/log off name on each of the other machines. But I think you
said you've double checked that. You may want to remove all the user
accounts on the xp machine...and reinstall them.

Let us know how you do.


Have a nice week...

Trent

What do you call a smart blonde?
A golden retriever.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top