What is wong with XP netwroking?

[Brian Lynn]

I am seeing a lot of posts concerning XP networking issues. I too am having
trouble.

I run a peer-to-peer network of 2 xp home and 2 xp pro boxes. Everything was
running fine the last 3 months. After changing no settings I have suddenly
lost the ability for the computers to see each other. DCHP and DNS is
handled by the router and all the computers can still access the internet
through the router. They just all droppped off the network as available
resources. Even my shared network printer is offline.

What the heck is going on in WinXP?? I have had this problem in other
networks as well and so far I have not seen a good reason or explanation.
After several posts on the same issue I am very frustrated.

And its not like I don't know how to network:I am MCSE for Win2k.... but
things seem to not be working properly in XP... SOME ONE PLEASE HELP!! I AM
TEARING MY HAIR OUT OVER THIS DAILY!!

The networks always work... then drop out after a time. Why?

 

[Guest]

Brian
If you find out please post the answer. I have been trying to get two xp systems to talk to each other using a netgear router and they don't seem to want to do this

Dennis

 

[Steve Winograd [MVP]]

Brian ,
If you find out please post the answer. I have been trying to get two xp systems to talk to each other using a netgear router and they don't seem to want to do this.

Dennis

Dennis, run XP's Network Setup Wizard on both computers and tell it
that they connect to the Internet through a "residential gateway". It
will make all the right settings.

Un-install (don't just disable) all firewall programs, such as Norton
Internet Security and ZoneAlarm, while troubleshooting the network.
Your Netgear router protects the computers from access by other
Internet users. Note that some recent antivirus programs also have
firewall capabilities built in. Don't un-install the antivirus
program, but do disable its firewall while troubleshooting.
--
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

 

[Guest]

Steve,
I did all this , in view workgroup computers I can see both systems. When I click on local system it shows me shared folders. when I click on remote system to view shared folders I receive error "\\remotesystemname is not accessible. you might not have permission to use this resource. contact the admistrator of this system to find out if you have access permissions." "the network path was not found". The shared folder son remote system have "everyone full control".
It seems like this was a lot eas

 

[Guest]

I have a similar problem, and to judge by what I see on various boards, we're not alone. My machines were able to talk to each other a few months ago, but no longer. I'm convinced that one of the numerous security updates I've applied must have broken the networking in some way, since these are the only software changes that have been made since it was working, and there've been no hardware changes

My two XP machines are completely unable to talk to each other - even ping doesn't seem to work. At least they can still both talk to the network at large (through my Linksys router/switch/firewall). The only machine either of them can ping successfully is the router at 192.168.1.1 - but of course, it's not running XP. I have done all of the suggested things, including

1. Running the network setup wizard for residential gateway mode on both systems
2. Disabling the XP software firewall on both systems (there are no others on my machines)
3. Making sure that NetBIOS (or was that NetBEUI) over TCP/IP is enabled on both systems
4. Making sure that the Computer Browser and Server services are running on both systems
5. Making sure that the networking components "Client for MS Windows" and "File and Printer sharing" are installed on both machines
6. Eliminating the router as a suspect by connecting the machines through a local hub that has no other connections and no internet connection

In short, you name it, I've tried it, everything short of dancing around the computers shaking a rattle and chanting. There's no way to contact Microsoft about this problem even though it's pretty clear this is a major cock-up affecting large numbers of XP users. I can't find anything other than the usual pablums in the knowledge base (basically many variants of the above suggestions). If anyone from Microsoft is reading this board, HELP

P.S. although it won't fix the TCP problems, one suggestion I've not tried is installing IPX/SPX networking, which it's been suggested I do as a way to at least share files and printers. Even if this works, it won't really fix the underlying problem, as (for instance) TCP-based games that I used to play on my home LAN will no longer work.

 

[Guest]

I have a similar problem, and to judge by what I see on various boards, we're not alone. My machines were able to talk to each other a few months ago, but no longer. I'm convinced that one of the numerous security updates I've applied must have broken the networking in some way, since these are the only software changes that have been made since it was working, and there've been no hardware changes

My two XP machines are completely unable to talk to each other - even ping doesn't seem to work. At least they can still both talk to the network at large (through my Linksys router/switch/firewall). The only machine either of them can ping successfully is the router at 192.168.1.1 - but of course, it's not running XP. I have done all of the suggested things, including

1. Running the network setup wizard for residential gateway mode on both systems
2. Disabling the XP software firewall on both systems (there are no others on my machines)
3. Making sure that NetBIOS (or was that NetBEUI) over TCP/IP is enabled on both systems
4. Making sure that the Computer Browser and Server services are running on both systems
5. Making sure that the networking components "Client for MS Windows" and "File and Printer sharing" are installed on both machines
6. Eliminating the router as a suspect by connecting the machines through a local hub that has no other connections and no internet connection

In short, you name it, I've tried it, everything short of dancing around the computers shaking a rattle and chanting. There's no way to contact Microsoft about this problem even though it's pretty clear this is a major cock-up affecting large numbers of XP users. I can't find anything other than the usual pablums in the knowledge base (basically many variants of the above suggestions). If anyone from Microsoft is reading this board, HELP

P.S. although it won't fix the TCP problems, one suggestion I've not tried is installing IPX/SPX networking, which it's been suggested I do as a way to at least share files and printers. Even if this works, it won't really fix the underlying problem, as (for instance) TCP-based games that I used to play on my home LAN will no longer work.

 

[Guest]

I've tried this, it didn't clear the problem up. I have no antivirus software running, no software firewalls, and yes I ran the network setup wizard on both machines. They still won't talk to each other. According to Windows Update both machines have all the latest "critical updates" and "driver updates". In the not-too-distant past these machines were able to ping each other, connect TCP-based games, browse a web server running on one from the other, and share files (at least in one direction, though for reasons I never understood it didn't work in the other direction)

Any other ideas? Do you think it's possible one of the critical updates has broken the TCP stack in some fundamental way that's killing peer-to-peer operation for these home lans?

 

[XPUSER]

I have a similar problem, and to judge by what I see on various boards,

we're not alone. My machines were able to talk to each other a few months
ago, but no longer. I'm convinced that one of the numerous security updates
I've applied must have broken the networking in some way, since these are
the only software changes that have been made since it was working, and
there've been no hardware changes.

My two XP machines are completely unable to talk to each other - even ping

doesn't seem to work. At least they can still both talk to the network at
large (through my Linksys router/switch/firewall). The only machine either
of them can ping successfully is the router at 192.168.1.1 - but of course,
it's not running XP. I have done all of the suggested things, including:

1. Running the network setup wizard for residential gateway mode on both systems.
2. Disabling the XP software firewall on both systems (there are no others on my machines).
3. Making sure that NetBIOS (or was that NetBEUI) over TCP/IP is enabled on both systems.
4. Making sure that the Computer Browser and Server services are running on both systems.
5. Making sure that the networking components "Client for MS Windows" and

"File and Printer sharing" are installed on both machines.

6. Eliminating the router as a suspect by connecting the machines through

a local hub that has no other connections and no internet connection.

In short, you name it, I've tried it, everything short of dancing around

the computers shaking a rattle and chanting. There's no way to contact
Microsoft about this problem even though it's pretty clear this is a major
cock-up affecting large numbers of XP users. I can't find anything other
than the usual pablums in the knowledge base (basically many variants of the
above suggestions). If anyone from Microsoft is reading this board, HELP!

P.S. although it won't fix the TCP problems, one suggestion I've not tried

is installing IPX/SPX networking, which it's been suggested I do as a way to
at least share files and printers. Even if this works, it won't really fix
the underlying problem, as (for instance) TCP-based games that I used to
play on my home LAN will no longer work.
===============================================
Where did you get the idea that there is no way to contact Microsoft?

NOTE:
http://support.microsoft.com/default.aspx?scid=sz;[ln];top
===============================================

 

[S Green]

I have a similar problem, and to judge by what I see on various boards,

we're not alone. My machines were able to talk to each other a few months
ago, but no longer. I'm convinced that one of the numerous security updates
I've applied must have broken the networking in some way, since these are
the only software changes that have been made since it was working, and
there've been no hardware changes.

My two XP machines are completely unable to talk to each other - even ping

doesn't seem to work. At least they can still both talk to the network at
large (through my Linksys router/switch/firewall). The only machine either
of them can ping successfully is the router at 192.168.1.1 - but of course,
it's not running XP. I have done all of the suggested things, including:

1. Running the network setup wizard for residential gateway mode on both systems.
2. Disabling the XP software firewall on both systems (there are no others on my machines).
3. Making sure that NetBIOS (or was that NetBEUI) over TCP/IP is enabled on both systems.
4. Making sure that the Computer Browser and Server services are running on both systems.
5. Making sure that the networking components "Client for MS Windows" and

"File and Printer sharing" are installed on both machines.

6. Eliminating the router as a suspect by connecting the machines through

a local hub that has no other connections and no internet connection.

In short, you name it, I've tried it, everything short of dancing around

the computers shaking a rattle and chanting. There's no way to contact
Microsoft about this problem even though it's pretty clear this is a major
cock-up affecting large numbers of XP users. I can't find anything other
than the usual pablums in the knowledge base (basically many variants of the
above suggestions). If anyone from Microsoft is reading this board, HELP!

P.S. although it won't fix the TCP problems, one suggestion I've not tried

is installing IPX/SPX networking, which it's been suggested I do as a way to
at least share files and printers. Even if this works, it won't really fix
the underlying problem, as (for instance) TCP-based games that I used to
play on my home LAN will no longer work.


You say you have all the latest updates etc.

I was in the same position. I had installed a WiFi update onto my desktop.
Once I removed this I found that the problem went away.

 

[Ken Wickes [MSFT]]

Concentrate on getting the machines to ping each other. Workgroups,
NetBIOS, Computer Browser, Server, Client for MS Windows, and F&P sharing
are all unnecessary for this.

Are you pinging by name or by IP address? Try by IP address. What are the
IP addresses of the machines.

This problem almost always end up being firewalls, have you ever had a 3rd
party firewall on your system, even if you uninstalled it?



--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

I have a similar problem, and to judge by what I see on various boards,

we're not alone. My machines were able to talk to each other a few months
ago, but no longer. I'm convinced that one of the numerous security updates
I've applied must have broken the networking in some way, since these are
the only software changes that have been made since it was working, and
there've been no hardware changes.

My two XP machines are completely unable to talk to each other - even ping

doesn't seem to work. At least they can still both talk to the network at
large (through my Linksys router/switch/firewall). The only machine either
of them can ping successfully is the router at 192.168.1.1 - but of course,
it's not running XP. I have done all of the suggested things, including:

1. Running the network setup wizard for residential gateway mode on both systems.
2. Disabling the XP software firewall on both systems (there are no others on my machines).
3. Making sure that NetBIOS (or was that NetBEUI) over TCP/IP is enabled on both systems.
4. Making sure that the Computer Browser and Server services are running on both systems.
5. Making sure that the networking components "Client for MS Windows" and

"File and Printer sharing" are installed on both machines.

6. Eliminating the router as a suspect by connecting the machines through

a local hub that has no other connections and no internet connection.

In short, you name it, I've tried it, everything short of dancing around

the computers shaking a rattle and chanting. There's no way to contact
Microsoft about this problem even though it's pretty clear this is a major
cock-up affecting large numbers of XP users. I can't find anything other
than the usual pablums in the knowledge base (basically many variants of the
above suggestions). If anyone from Microsoft is reading this board, HELP!

P.S. although it won't fix the TCP problems, one suggestion I've not tried

is installing IPX/SPX networking, which it's been suggested I do as a way to
at least share files and printers. Even if this works, it won't really fix
the underlying problem, as (for instance) TCP-based games that I used to
play on my home LAN will no longer work.

 

[Guest]

At last! Thanks to an anonymous poster on one of about a dozen boards I've been reading through. The problem was that the IPSEC service wasn't started. Once I started it, everything started working again. This tip should definitely be added to the checklists for networking problems, I haven't seen it mentioned anywhere else.

 

[Guest]

I was using IP addresses. But see my other post, the problem was the IPSEC service. This should definitely be added to the troubleshooter, which I ran through a few times unsuccessfully trying to solve the problem myself.

Thanks,

Doug

 

[Ken Wickes [MSFT]]

Glad you got it working. Was it not set to Automatic start?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

I was using IP addresses. But see my other post, the problem was the

IPSEC service. This should definitely be added to the troubleshooter, which
I ran through a few times unsuccessfully trying to solve the problem myself.

 

[Guest]

----- Brian Lynn wrote: ----

I am seeing a lot of posts concerning XP networking issues. I too am havin
trouble

I run a peer-to-peer network of 2 xp home and 2 xp pro boxes. Everything wa
running fine the last 3 months. After changing no settings I have suddenl
lost the ability for the computers to see each other. DCHP and DNS i
handled by the router and all the computers can still access the interne
through the router. They just all droppped off the network as availabl
resources. Even my shared network printer is offline

What the heck is going on in WinXP?? I have had this problem in othe
networks as well and so far I have not seen a good reason or explanation
After several posts on the same issue I am very frustrated

And its not like I don't know how to network:I am MCSE for Win2k.... bu
things seem to not be working properly in XP... SOME ONE PLEASE HELP!! I A
TEARING MY HAIR OUT OVER THIS DAILY!

The networks always work... then drop out after a time. Why


Brain: Trying going back to restore your computer to a previous time when your computer last worked properly. Go to the control panel look under help and support then click on system restore and follow the commands. For example: If your computer work properly on December 13, 2003 then use that date or however date that was your last date when your computer worked. If necessary go back even further it all depends on where your last network date worked properly. If you don't remember when it was last working properly go back and look at the history of your computer to help you. I hope this information is helpful to you

 

[Guest]

-----Original Message-----
I have a similar problem, and to judge by what I see on

various boards, we're not alone. My machines were able
to talk to each other a few months ago, but no longer.
I'm convinced that one of the numerous security updates
I've applied must have broken the networking in some way,
since these are the only software changes that have been
made since it was working, and there've been no hardware
changes.

My two XP machines are completely unable to talk to each

other - even ping doesn't seem to work. At least they
can still both talk to the network at large (through my
Linksys router/switch/firewall). The only machine either
of them can ping successfully is the router at
192.168.1.1 - but of course, it's not running XP. I have
done all of the suggested things, including:

1. Running the network setup wizard for residential gateway mode on both systems.
2. Disabling the XP software firewall on both systems

(there are no others on my machines).

3. Making sure that NetBIOS (or was that NetBEUI) over

TCP/IP is enabled on both systems.

4. Making sure that the Computer Browser and Server

services are running on both systems.

5. Making sure that the networking components "Client

for MS Windows" and "File and Printer sharing" are
installed on both machines.

6. Eliminating the router as a suspect by connecting the

machines through a local hub that has no other
connections and no internet connection.

In short, you name it, I've tried it, everything short

of dancing around the computers shaking a rattle and
chanting. There's no way to contact Microsoft about this
problem even though it's pretty clear this is a major
cock-up affecting large numbers of XP users. I can't
find anything other than the usual pablums in the
knowledge base (basically many variants of the above
suggestions). If anyone from Microsoft is reading this
board, HELP!

P.S. although it won't fix the TCP problems, one

suggestion I've not tried is installing IPX/SPX
networking, which it's been suggested I do as a way to at
least share files and printers. Even if this works, it
won't really fix the underlying problem, as (for
instance) TCP-based games that I used to play on my home
LAN will no longer work.How about the Workgroup Name. Is it the same on both
computers? If not change the workgroup names on both
computers so they match and then reboot them.