Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows Vista / Networking / May 2008

Tip: Looking for answers? Try searching our database.

Networking - Weird Bug

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
tjasko5041 - 29 May 2008 21:01 GMT
Hi Everyone,

I have one the strangest bugs ever created; and no one else seems to get it.
I cannot detect any (very very few; not even my XP Machines, will explain
soon) of my computers on any network (wireless) I connect to. When I
installed Vista bare clean, it did detect my netword computers, even the XP
ones. But now, I feel like I should reinstall Vista. But, I really don't want
to restore all (I have over 40gb) of my data. That would just take forever.
Is there anyway at all to restore ALL Vista's Networking features/software to
normal. Or back to default. I cannot restore using System Restore. I have
been having this for about a month now, and it really messes me up! Over a
week of using it, I just cannot detect any of my Networks. I can in Ubuntu;
but not in Vista (my primary OS). I really love Windows. But, this is one of
the worst glitches I have ever had with it.

Is it possible to reinstall Vista's Network and Sharing Center? I really
want to detect my XP machines again. You might say, install LTDD (??) onto
the XP machines. Well, the problem is, it still does not work. When I was
using this PC a while ago, they were detected fine. But now, I cannot find
any PC (hardly any; dunno why) on my network. This even happens at my Local
Library. My friend searched, and he found over 200. I found only 5! Wow,
something is wrong, and I really would appreciate it if anyone would help me
fix this.
tjasko5041 - 29 May 2008 21:11 GMT
By the way, this might help (In command prompt)

_____________________________
net veiw 192.168.0.1, I get:

System error 53 has occuerred.
The network path was not found.
_______________________________

Wow, I don't know what to do. This is on my laptop too by the way.
tjasko5041 - 29 May 2008 21:11 GMT
SystemBy the way, this might help (In command prompt)

_____________________________
net veiw 192.168.0.1, I get:

System error 53 has occuerred.
The network path was not found.
_______________________________

Wow, I don't know what to do. This is on my laptop too by the way.
GTS - 29 May 2008 21:58 GMT
Are you able to connect to your wireless router and access the Internet
through your wireless card?

Error 53 means the network path was not found.   If your connection
otherwise works, do you have a 3rd party firewall?  If so, is it properly
configured?    Can you ping another machine on your network by IP?

There are various possibilities but the starting point is to report whether
you have general connectivity.
--

> Hi Everyone,
>
[quoted text clipped - 28 lines]
> me
> fix this.
GTS - 29 May 2008 22:06 GMT
Addendum
 Posting the output of ipconfig /all would be helpful.

--
tjasko5041 - 29 May 2008 23:26 GMT
C:\Users\Taylor Jasko>ipconfig /all

Windows IP Configuration

  Host Name . . . . . . . . . . . . : TJ-PC
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : *************

Wireless LAN adapter Wireless Network Connection:

  Connection-specific DNS Suffix  . : ***************
  Description . . . . . . . . . . . : Atheros AR5007 802.11b/g WiFi Adapter
  Physical Address. . . . . . . . . : ***************
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::54c6:632e:3686:6dce%14(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.0.100(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : Thursday, May 29, 2008 3:01:33 PM
  Lease Expires . . . . . . . . . . : Thursday, May 29, 2008 9:01:32 PM
  Default Gateway . . . . . . . . . : 192.168.0.1
  DHCP Server . . . . . . . . . . . : 192.168.0.1
  DNS Servers . . . . . . . . . . . : 192.168.0.1
  NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
  Physical Address. . . . . . . . . : **************
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  IPv6 Address. . . . . . . . . . . :
2001:0:4137:9e50:2cec:3205:3f57:ff9b(Pref
erred)
  Link-local IPv6 Address . . . . . : fe80::2cec:3205:3f57:ff9b%8(Preferred)
  Default Gateway . . . . . . . . . : ::
  NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . : *************
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
  Physical Address. . . . . . . . . : *******************
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

C:\Users\Taylor Jasko>

> Addendum
>   Posting the output of ipconfig /all would be helpful.
tjasko5041 - 29 May 2008 23:22 GMT
Yes, I am able to connect the the wireless router and access the internet
fine. No third party firewall. Actually, I just tried to ping my XPS; it
worked fine. Now, how do I get this to work... :)

THANKS FOR YOUR HELP!

Taylor Jasko

> Are you able to connect to your wireless router and access the Internet
> through your wireless card?
[quoted text clipped - 39 lines]
> > me
> > fix this.
Mick Murphy - 30 May 2008 03:06 GMT
http://technet.microsoft.com/en-us/library/bb727037.aspx

Have a read of the above link re Vista File and Printer Sharing.

Permissions/Share info is there as well.

If using Norton, McAfee, Trend Micro I.S., make sure file and printer
sharing is enabled in THEIR firewall.

1st thing to do is make sure that the Workgroup Name of ALL the computers is
the SAME.

In Vista Network and Sharing:

Network Discovery: ON (So it can see the other computers)

Network set to Private (Public is for hotspots, airports, etc)

File Sharing: ON

Public Folder Sharing: ON (Vista’s Public Folder is the same as XP’s Shared
Docs)

Password Protected: OFF (unless you want to set up identical usernames and
passwords on ALL computers in your Network) If you have it ON, you will be
asked for a username and password when you try to access a Vista computer
from an XP computer.

Also, run the XP’s Home Network File and Printer Sharing Wizard to include
Vista in your “New” Network, even if you had an XP Network set up prior to
adding a Vista computer to it.

Signature

Mick Murphy - Qld - Australia

> Yes, I am able to connect the the wireless router and access the internet
> fine. No third party firewall. Actually, I just tried to ping my XPS; it
[quoted text clipped - 47 lines]
> > > me
> > > fix this.
tjasko5041 - 30 May 2008 03:53 GMT
I hate to say this, but I have tried all of that.

Honestly; I really have. That is why I titles this "Weird Bug".

I have no 3rd party firewall on this computer, only the Vista's default app.

I saw that link you posted before. I added those ports to the Windows
Firewall, and still, to no success.

Right now, I'm just thinking to my self, why can't Windows be more like
Linux. You can uninstall/reinstall any component in Linux no matter what it
is. That would be great if Windows could add that support to "add and remove
windows features". This would solve my problem just as if I could reinstall
my networking back to default. I spent over an hour trying to find out an
answer to this question; but to no avail.

Also, I do not set up sharing on the Vista machine. I only want to access
the shared files on the 3 desktops/servers in my household. It worked with a
clean Vista install from what I can remember; but not anymore. Wow, I really
I could fix this without restoring Windows to a clean install (reinstalling).

Thanks for your help; I really appreciate it. But, does anyone have any more
ideas? I contacted support about this issue; but I have to pay for the
"networking" support. Dunno why....

You know, I think this is a SP1 glitch. This never happened when I was not
using SP1. That might be the problem... But, I cannot prove that...

-Taylor-

> http://technet.microsoft.com/en-us/library/bb727037.aspx
>
[quoted text clipped - 79 lines]
> > > > me
> > > > fix this.
tjasko5041 - 30 May 2008 03:57 GMT
**Honestly; I really have. That is why I (titled) this "Weird Bug".**

Need to watch my typing sometimes. :)
GTS - 30 May 2008 04:28 GMT
You're welcome.   That's  helpful information.  Since you can ping the XPS
by IP, it sounds like a likely name resolution problem.  I suggest next you
open a command prompt and run this  start \\xxx.xxx.xxx.xxx where x is the
IP address of XPS.   Please report the result.  It should either open a
window showing it's shares or report an error.   Please post the result
including any error code.

If that does access the shares, I suggest you enable Net BIOS over TCP/IP on
all the machines (in the TCP properties of the connection) and then retry by
name.
Signature


> Yes, I am able to connect the the wireless router and access the internet
> fine. No third party firewall. Actually, I just tried to ping my XPS; it
[quoted text clipped - 62 lines]
>> > me
>> > fix this.
GTS - 30 May 2008 04:36 GMT
Addendum - You may need to use an elevated command prompt for the start
start \\xxx.xxx.xxx.xxx command.  Also, BTW, there is a way to rebuild the
TCP stack in Vista (several actually) but I think it's premature.  Please
try these items first and we'll pick it up from there.
Signature


> You're welcome.   That's  helpful information.  Since you can ping the XPS
> by IP, it sounds like a likely name resolution problem.  I suggest next
[quoted text clipped - 6 lines]
> on all the machines (in the TCP properties of the connection) and then
> retry by name.
tjasko5041 - 30 May 2008 11:10 GMT
I ran CMD as an administrator, same result.

What to do now?

I'm saying, this is not my settings on my desktops. Because my friends Vista
computer can access it fine...

> Addendum - You may need to use an elevated command prompt for the start
> start \\xxx.xxx.xxx.xxx command.  Also, BTW, there is a way to rebuild the
[quoted text clipped - 10 lines]
> > on all the machines (in the TCP properties of the connection) and then
> > retry by name.
tjasko5041 - 30 May 2008 11:08 GMT
C:\Users\Taylor Jasko>\\192.168.0.105
The filename, directory name, or volume label syntax is incorrect.

Actually, I know netbios is enabled by default on this machine (vista).
And, I'm pretty sure it's on the XPS's too...

The thing is, this worked when I first installed Vista... So, it's not my
network settings on my desktops, it's the settings on my laptop. I could
install Vista on a separate partition, and see (it probably will) if it'll
detect my XPS. It usually does.

> You're welcome.   That's  helpful information.  Since you can ping the XPS
> by IP, it sounds like a likely name resolution problem.  I suggest next you
[quoted text clipped - 72 lines]
> >> > me
> >> > fix this.
GTS - 30 May 2008 15:24 GMT
That's a very peculiar error.  Try running the following command in an
elevated command prompt and rebooting.  This rebuilds the TCP stack.  The
last part (iplog.txt) is optional - it creates a log of actions taken.
netsh int ip reset iplog.txt

> C:\Users\Taylor Jasko>\\192.168.0.105
> The filename, directory name, or volume label syntax is incorrect.
[quoted text clipped - 97 lines]
>> >> > me
>> >> > fix this.
GTS - 30 May 2008 16:38 GMT
Oops - I see you type the comand incorrectly - you left out start.  That
would cause the error you saw.  It should be
> C:\Users\Taylor Jasko>start  \\192.168.0.105
Signature


> That's a very peculiar error.  Try running the following command in an
> elevated command prompt and rebooting.  This rebuilds the TCP stack.  The
[quoted text clipped - 108 lines]
>>> >> > me
>>> >> > fix this.
tjasko5041 - 30 May 2008 21:41 GMT
OMG!

WOW!

It brought up my XPS's shared documents! Wow. That's really great!

Now, to find out why it isn't putting this in explorer.....

> Oops - I see you type the comand incorrectly - you left out start.  That
> would cause the error you saw.  It should be
> > C:\Users\Taylor Jasko>start  \\192.168.0.105
tjasko5041 - 30 May 2008 21:42 GMT
> Oops - I see you type the comand incorrectly - you left out start.  That
> would cause the error you saw.  It should be
[quoted text clipped - 111 lines]
> >>> >> > me
> >>> >> > fix this.
tjasko5041 - 30 May 2008 19:51 GMT
Actually, I done that before. Does nothing for me. It isn't fixed.

Yeah, it's some weird error, isn't it?

I don't know what to do...

No sources online helped me. So, I think I'm stuck with it. :(

> That's a very peculiar error.  Try running the following command in an
> elevated command prompt and rebooting.  This rebuilds the TCP stack.  The
[quoted text clipped - 102 lines]
> >> >> > me
> >> >> > fix this.
GTS - 30 May 2008 21:31 GMT
Did you retry the >start \\###.###.###.### with correct syntax?
Signature


> Actually, I done that before. Does nothing for me. It isn't fixed.
>
[quoted text clipped - 132 lines]
>> >> >> > me
>> >> >> > fix this.
tjasko5041 - 30 May 2008 21:43 GMT
Yes, I just did.

And, it works fine.

Now, why isn't it putting this in the networking window....

> Did you retry the >start \\###.###.###.### with correct syntax?
> > Actually, I done that before. Does nothing for me. It isn't fixed.
[quoted text clipped - 133 lines]
> >> >> >> > me
> >> >> >> > fix this.
GTS - 30 May 2008 22:08 GMT
Now, as I mentioned previously, check your NetBIOS setting.  Set it to
Enable NetBIOS over TCP/IP on all machines.
Signature


> Yes, I just did.
>
[quoted text clipped - 157 lines]
>> >> >> >> > me
>> >> >> >> > fix this.
tjasko5041 - 30 May 2008 22:49 GMT
I did this; and it does not work still...

Not an easy fix... Am I the only one having this issue? It's this computer,
I can tell you that. It works on another Vista PC though... So, it's
something with Vista that I don't know what's up. Hey, at least I have my XPS
in My Computer now. I appreciate that. But, I go mobile a lot; and connect to
other PC's/Printers. It doesn't detect printers either. Well, very few of
them. I don't know what is up. Here's my friend next to me detecting over 200
printers, and here I am up with 6... There's something wrong with Vista.......

Thanks for all your help by the way ;). Were solving it slowly.. Worst case,
I will have to reinstall. :( Which, would take ages to get it the way I have
it now...

> Now, as I mentioned previously, check your NetBIOS setting.  Set it to
> Enable NetBIOS over TCP/IP on all machines.
[quoted text clipped - 159 lines]
> >> >> >> >> > me
> >> >> >> >> > fix this.
GTS - 31 May 2008 18:40 GMT
You're welcome.
  It's clear at this point that the problem is in network discovery and
probably related NetBIOS communication since you can access shares by IP.
It might be interesting to see if it's the same (in the printers example you
mentioned) with a wired connection.   I have no other ideas at the moment.
Signature


>I did this; and it does not work still...
>
[quoted text clipped - 206 lines]
>> >> >> >> >> > me
>> >> >> >> >> > fix this.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.