Interesting problem - ping loop ok but not ping IP address

  • Thread starter Thread starter Julian
  • Start date Start date
J

Julian

I have an XP machine (ORANGE) connected to a WIN 98
machine (BLUE). On orange I can see and access files on
blue ok. On orange, my network ip address local is
192.168.0.1 as set up by the wizard. On orange, I can
ping 127.0.0.1 ok. But I can't ping 192.168.0.1, and I
can't ping the computer name "orange" - it times out. I
can't ping orange from blue, and I can't connect to
orange from blue.

But I have been using this setup for weeks without
realising this problem because I only needed to sit at
orange and get files from blue - no difficulty at all.

I have re-installed my NIC (REALTEK RTL8139 on-board an
ASUS motherboard) in device manager but no change. ALso
have repeated the network wizard several times, no change.

Anyone have any ideas what could be wrong?
 
I updated driver and now both computers can ping orange,

BUT I still can't access orange from outside, and I still
can access blue from orange. When I try to access orange
from blue, I get

"\\ORANGE is not accessible. Unknown error 31"

Any ideas anyone?
 
"Julian" said:
I updated driver and now both computers can ping orange,

BUT I still can't access orange from outside, and I still
can access blue from orange. When I try to access orange
from blue, I get

"\\ORANGE is not accessible. Unknown error 31"

Any ideas anyone?
Click to expand...

Error 31 occurs if you set up a user account without a password and
then attempt to log in across the network. By default, Windows XP
doesn't permit remote users to connect from the network without a
password. To allow access without a password:

1. Go to Control Panel | Performance and Maintenance | Administrative
Tools | Local Security Policy.

2. Expand Local Policies | Security options.

3. Double-click Accounts: Limit local account use of blank passwords
to console login only, which is enabled by default.

4. Disable this option.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

Adding Windows XP to an Existing Network
http://www.practicallynetworked.com/sharing/xp/addxp.htm

Windows XP Internet Connection Sharing
http://www.practicallynetworked.com/sharing/xp_ics

Windows XP Professional File Sharing
http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm

Windows XP Network Troubleshooting
http://www.practicallynetworked.com/sharing/troubleshoot
 
Steve thank you very much for this answer, I am sure I'd
never have found this answer any other way.

What I really don't understand is how anyone, any normal
mortal, is supposed to find out such things. I am more
knowledgable than most computer users, and I was setting
up a very boring small network the same as a zillion
other microsoft customers must do, but I swear I had NO
chance of finding this bit of important information.

How come this is not covered by the Network Wizard? WHy
is there no reference to error 31 in the "Help and
Support Centre" or in Knowledgebase? Why do the "problem
fix" wizards not mention this? Why does my $130 book on
XP not mention it? It can't be a rare problem, in fact
it must happen for EVERY XP user who sets up a small
network without passwords.

I ask these questions sincerely because I was hoping to
become self sufficient in running windows computers, but
when something like this happens I realise I have no
chance if I can't even find simple information like this.

How did you know about this? And is there a database of
error code explanations somewhere?

Thanks again for taking the time to answer my original
problem, it was much appreciated.

Cheers,

Julian

-----Original Message-----
Click to expand...
 
Hi Steve,

Thank you for the tip. I have been trying to find the solution for "Unknown
error 31". Do you know if MS has the article regarding this issue?

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
"Julian" said:
Steve thank you very much for this answer, I am sure I'd
never have found this answer any other way.

What I really don't understand is how anyone, any normal
mortal, is supposed to find out such things. I am more
knowledgable than most computer users, and I was setting
up a very boring small network the same as a zillion
other microsoft customers must do, but I swear I had NO
chance of finding this bit of important information.

How come this is not covered by the Network Wizard? WHy
is there no reference to error 31 in the "Help and
Support Centre" or in Knowledgebase? Why do the "problem
fix" wizards not mention this? Why does my $130 book on
XP not mention it? It can't be a rare problem, in fact
it must happen for EVERY XP user who sets up a small
network without passwords.

I ask these questions sincerely because I was hoping to
become self sufficient in running windows computers, but
when something like this happens I realise I have no
chance if I can't even find simple information like this.

How did you know about this? And is there a database of
error code explanations somewhere?

Thanks again for taking the time to answer my original
problem, it was much appreciated.

Cheers,

Julian
Click to expand...

You're welcome, Julian.

I learned about Error 31 while researching Windows XP Professional
networking for an article that Ron Lowe and I wrote:

Windows XP Professional File Sharing
http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm

Blank passwords are mentioned in file READ1ST.TXT on the Windows XP
Pro CD-ROM:

3.2.2 Restrictions on the Use of Blank Passwords

----------------------------------------------------------------------
Windows XP has a new default security feature that helps protect
users with blank passwords from network-based attacks. Users who do
not password-protect their accounts can only log on at their
physical computer console: the monitor, keyboard, and mouse that is
physically connected to their computer.

More people don't run into this because Windows XP Home Edition
doesn't have the restriction. I don't remember for sure, but Ron or I
might have read that and then tried logging in over the network with a
blank password to see what would happen.

I don't know why Microsoft has neglected to document the actual error
message.

I just found some references to Error 31 using this search string in
Google:

"Error 31" network xp
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
"Robert L said:
Thank you for the tip. I have been trying to find the solution for "Unknown
error 31". Do you know if MS has the article regarding this issue?
Click to expand...

You're welcome, Robert. I can't find anything on the Microsoft web
site about the error. Maybe Ron Lowe will see this message and have
something to add.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Thanks.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
Back
Top