Nintendo Wifi Connector disables Guest access to file shares

[devzeromail]

I installed the Nintendo Wifi connector on my computer. Its essentially
an USB based access point that connects a Nintendo DS to the computer.
The install script sets up internet connection sharing so as the
Nintendo DS has access to the internet. Unfortunately as soon it
installs, Guest access to the host machine from another xp machine
isn't allowed. The files are still shared and guest access is still
enabled as an account. By typing \\nameofmachine from the machine I
want to connect to I can still long in to the share but its done
through the account i'm currently using.

Any ideas?

 

[devzeromail]

Just to clarify. A normal wifi adapter supplies my network/internet
connection to the computer in question.

 

[devzeromail]

Its also the case now that I can't even "view workgroup computers".

 

[devzeromail]

The other pc in the house can't browse the local workgroup at the
moment. Below is the printout of ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : mypc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11a/b/g WLAN
Physical Address. . . . . . . . . : *****************
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.35
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 128.0.12.0
Secondary WINS Server . . . . . . : 39.123.0.0
Lease Obtained. . . . . . . . . . : 29 March 2006 13:07:58
Lease Expires . . . . . . . . . . : 01 April 2006 13:07:58

Ethernet adapter Nintendo WFC:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Nintendo Wi-Fi USB
Connector
Physical Address. . . . . . . . . : ********************
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.0.1
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

 

[devzeromail]

Ok, I figured it out. It was a firewall problem. ICF was restricting
access to the wrong subnet.I specified the ips individually that I
wanted into ICF and everything works. Does anyone know how to specify
an ip range though as opposed to explicitly stating the ip.

 

[Ron Lowe]

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . . . . : 128.0.12.0
Secondary WINS Server . . . . . . : 39.123.0.0

Do you really have a WINS server in your house?
Most people don't. (I do, but that's another matter! )

Those IP addresses are spurious ( they are not even the IP addresses of
machines, they are network addresses. )
Go into the IP configuration and remove these spurious WINS server addresses
for a start.

If they are not coming from the local IP configuration, then look at the
DHCP server ( presumably a router at 192.168.1.1 )and see if it is issuing
spurious WINS server addresses.

 

[Ron Lowe]

Ok, I figured it out. It was a firewall problem. ICF was restricting
access to the wrong subnet.I specified the ips individually that I
wanted into ICF and everything works. Does anyone know how to specify
an ip range though as opposed to explicitly stating the ip.

In the 'Change Scope' dialog, you specify a range by using an IP address and
either a subnet mask, or a network prefix length.
So for example you could specify the range 192.168.0.0 thru 192.168.0.255
like this:

192.168.0.0/255.255.255.0
192.168.0.0/24

If you have a specific range you want to specify, and can't figure it out,
post it and we'll give you the closest you can do.

 

[devzeromail]

Thanks for the reply Ron. Nope, I don't have a Wins server, that was
just assigned by the dhcp for some reason. Can you explain the second
way of assigning ip ranges again. I got the first one but the second
one baffles me. Are you saying 192.168.0.0/24 takes in the range from
192.168.0.0 thru 192.168.0.255 or 192.168.0.0 thru 192.168.0.24

 

[Ron Lowe]

Thanks for the reply Ron. Nope, I don't have a Wins server, that was
just assigned by the dhcp for some reason. Can you explain the second
way of assigning ip ranges again. I got the first one but the second
one baffles me. Are you saying 192.168.0.0/24 takes in the range from
192.168.0.0 thru 192.168.0.255 or 192.168.0.0 thru 192.168.0.24

Both mean the range 192.168.0.0 thru 192.168.0.255
They are just different notations for the same thing.

192.168.0.0/24 is the same as 192.168.0.0/255.255.255.0

/24 means : the number of bits of the IP address which correspond to the
Network ID is 24. ( in otherwords, the 192.168.0 part. )

A subnet mask of 255.255.255.0 says the same thing.


/8 = mask 255.0.0.0 ( binary 11111111 00000000 00000000 00000000 )
/16 = mask 255.255.0.0 ( binary 11111111 11111111 00000000 00000000 )
/24 = mask 255.255.255.0 ( binary 11111111 11111111 11111111 00000000 )

You don't have to align on 8-bit boundaries, either.

/28 = mask 255.255.255.240 ( binary 11111111 11111111 11111111 11110000 )

Here's some tutorial stuff:
http://www.learntosubnet.com/

 

[devzeromail]

Thanks, you've been a great help.