WIRELESS CONNECTION IN XP/FILE PRINTER SHARING

[Guest]

WHY IS WIRELESS CONNECTION SUCH A HASSLE IN XP. ARE MICROSOFT BURYING THEIR
LARGE CORPORATE HEADS IN THE SAND REGARDING SETTING UP A WIRELESS NETWORK
USING XP SP2 AND SHARING FILES AND PRINTERS.

I HAVE A DESKTOP PC RUNNING XP PRO AND A NEW LAPTOP RUNNING XP HOME BOTH
SP2. HAVE INTERNET CONNECTION RUNNING THU WIRELESS ROUTER (TREND).BUT AS SEEN
IN VARIOUS OTHER QUESTIONS I AM UNABLE TO SEE WORKGROUP PCS' OR SHARED FILES
OR FOLDERS. I AM CAPABLE OF MOST PC TASKS BUT THIS IS HEAD BANGING ON THE
WALL TIME.

 

[Chuck]

WHY IS WIRELESS CONNECTION SUCH A HASSLE IN XP. ARE MICROSOFT BURYING THEIR
LARGE CORPORATE HEADS IN THE SAND REGARDING SETTING UP A WIRELESS NETWORK
USING XP SP2 AND SHARING FILES AND PRINTERS.

I HAVE A DESKTOP PC RUNNING XP PRO AND A NEW LAPTOP RUNNING XP HOME BOTH
SP2. HAVE INTERNET CONNECTION RUNNING THU WIRELESS ROUTER (TREND).BUT AS SEEN
IN VARIOUS OTHER QUESTIONS I AM UNABLE TO SEE WORKGROUP PCS' OR SHARED FILES
OR FOLDERS. I AM CAPABLE OF MOST PC TASKS BUT THIS IS HEAD BANGING ON THE
WALL TIME.

Shuggie,

To start, please don't type in all capital letters. It's hard to read what
you're reporting.
<http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#Grammar>
http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#Grammar

Now then, are you certain that your problem is related to wireless connectivity?
Visibility problems, like you're describing, have many causes that are present
in wired LANs too. One of the most common causes of this problem would be a
misconfigured or overlooked personal firewall, but there are other possibilities
too.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

If no help yet, provide "browstat status" and "ipconfig /all" from each
computer, so we can diagnose the problem. Read this article, and linked
articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

 

[Guest]

PC1. CONNECTED AS FOLLOWS REALTEK CARD, ETHERNET CABLE TO TREND WIRELESS
ROUTER CONNECTED WIRELESSLY TO PC2 (NOTEBOOK) INTERNET CONNECTION OK.

Windows IP Configuration FOR PC1.



Host Name . . . . . . . . . . . . : hugh-7t5ybpg95d

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast
Ethernet NIC

Physical Address. . . . . . . . . : 00-05-1C-16-CD-B3

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : 11 January 2006 15:27:50

Lease Expires . . . . . . . . . . : 14 January 2006 15:27:50

 

[Guest]

I am sorry for the large type but I only have 50% sight. I will try to
remember to downsize when communicating via emal.
Shuggie

Windows IP Configuration FOR LAPTOP (PC2)



Host Name . . . . . . . . . . . . : HUGHNOTEBOOK

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network Connection

Physical Address. . . . . . . . . : 00-13-CE-77-16-6D

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.4

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Lease Obtained. . . . . . . . . . : 11 January 2006 15:34:26

Lease Expires . . . . . . . . . . : 14 January 2006 15:34:26



Ethernet adapter Local Area Connection:



Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Marvell Yukon 88E8036 PCI-E Fast
Ethernet Controller

Physical Address. . . . . . . . . : 00-E0-B8-99-74-A9



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 00-00-F8-3B-A7-92-D5-24

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . :
3ffe:831f:4004:1956:0:f83b:a792:d524

IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5

Default Gateway . . . . . . . . . : ::

NetBIOS over Tcpip. . . . . . . . : Disabled



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-00-04

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.4%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

 

[Chuck]

I am sorry for the large type but I only have 50% sight. I will try to
remember to downsize when communicating via emal.
Shuggie

Shuggie,

OK, much better. Now, to start, HUGHNOTEBOOK has IPV6 aka Teredo Tunneling.
This is known to cause problems, and should be removed. Follow instructions in
this article.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

And make sure that NetBIOS Over TCP/IP is enabled.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components

Type size is not a problem - I use a Usenet reader, which ignores type size (and
other GUI tweaks). But Usenet does pickup on type case, and posting with all
capital letters is considered shouting. So thanks for not shouting.

 

[Guest]

Okay fine. now have network showing on both desktop and laptop. But will not
let me access workgroup as I do not have permission, contact administrator.I
also find that I am signed on as a "GUEST"

 

[Chuck]

Okay fine. now have network showing on both desktop and laptop. But will not
let me access workgroup as I do not have permission, contact administrator.I
also find that I am signed on as a "GUEST"

OK, so now you are using Guest authentication. You need to enable Guest for
network sharing. Read this article, and follow the links, where you need
further explanation about any subject being discussed.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help