XP - Network Shares not working wireless

[Abet Computers]

I have a question for you, it maybe simple ( simple is always the most complex) anyway, I have a workgroup of computers on a network shares a new laptop was just brought in and needs access to the shared network but its unable to do so, VIA wireless but it can VIA wired


So I got \\Primary\C$

I can access it when its plugged in ethernet, but when its connected to the wireless connection it says is not accessible. You might not have permission to use this network resource. Getting frustrated anyone have any suggestions?

It has to be an easy fix that I am looking over but not sure what it is.

 

[Abet Computers]

really no input?

I have it connected like this

Cable Modem, cisco wireless router/ 4 port , IP phone, Switch, connected, Switch has 20 ports which have 6 desktops connected into it, all set to share which they do just fine. ( the new computer is for servicing out in the 1 mile field they have ( have an omidir antenna up on a 60ft pole and it works just fine, but its unable to connect to the network shares - It will connect via ethernet but not wireless , what am I missing?

 

[YOCS]

Just a shot in the dark. Is the wireless connection set as public?

 

[coffee]

Im assuming some things about your setup so correct me if Im wrong.

1. You have a cable modem with a wireless router connected to it. All computers are hard wired to the router or cable box. You have a laptop that will connect wirelessly but cannot access shares.

My .02c on this is this:

Your wireless laptop is connecting on a different network segment. Therefore, It is not seeing any shares because the shares are available on the other subnet - not the one the laptop is on. Example: Your wired network is on 10.0.1.0 and the wireless router puts your laptop on 192.168.0.0.

What I would do is go into the setup of your wireless router and turn off DHCP. Set your router address to the same subnet as your wired. Example: your cable modem is handing out DHCP to wired connections and its internal ip is 10.0.1.1 . Therefore, Give your router a static ip of 10.0.1.2 and turn off DHCP on the router. Then move the network cable you have plugged into the WAN port of the router to just one of the other ports on the router. Leave the wireless area in the router as is. Then reboot router. Now the router is acting like a AP and you should see your shares as long as a firewall isnt blocking them.

My shop setup is as follows (as an illistration):

router -----------> My linux (iptables,DHCP) router
10.0.1.2 ------------------ 10.0.1.1

I have my dhcp setup to only give out a total of 5 network addresses. All my other boxes are networked with static ips. The 5 dynamic ips are for connecting computers that are in the shop for service.

Hope this helps.

coffee

 

[Abet Computers]

you got it, thanks!!

 

[nlinecomputers]

you got it, thanks!!

Got what? What was the problem and the fix so others reading this no for certain.

 

[brandonkick]

Sounds like the wireless connection was putting the laptop onto a different subnet

 

[nlinecomputers]

Sounds like the wireless connection was putting the laptop onto a different subnet

Yes but I didn't want to make assumptions.

 

[NETWizz]

... and what difference would it make?

Provided the computer is reachable on both subnets, the name resolves, and the firewall (i.e. public) isn't blocking file sharing, all should be happy.

Now, obviously, you could have two different network adapters setup differently and they might just happen to be on different subnets/neetworks... and potentially those different networks might not allow the same authentication (i.e. if you have a domain and one subnet isn't on the domain).

 

[nlinecomputers]

... and what difference would it make?

Provided the computer is reachable on both subnets, the name resolves, and the firewall (i.e. public) isn't blocking file sharing, all should be happy.

Now, obviously, you could have two different network adapters setup differently and they might just happen to be on different subnets/neetworks... and potentially those different networks might not allow the same authentication (i.e. if you have a domain and one subnet isn't on the domain).

Making assumptions here but most network routers by default use 255.255.255.0 mask so each subnet would be cut off from each other. OP's noted that they wanted to access shares wired or wireless. So obviously they are not happy.

 

[coffee]

... and what difference would it make?

Provided the computer is reachable on both subnets, the name resolves, and the firewall (i.e. public) isn't blocking file sharing, all should be happy.

Now, obviously, you could have two different network adapters setup differently and they might just happen to be on different subnets/neetworks... and potentially those different networks might not allow the same authentication (i.e. if you have a domain and one subnet isn't on the domain).

Broadcast messages do not travel across subnets.

 

[SAG]

This is odd though.
OP never mentioned the model of Cisco, but I've never seen a wireless router that put wireless clients on a different subnet than wired as a DEFAULT setting. It has to be configured so.

 

[coffee]

This is odd though.
OP never mentioned the model of Cisco, but I've never seen a wireless router that put wireless clients on a different subnet than wired as a DEFAULT setting. It has to be configured so.

I have seen it alot. Seems alot of routers like the default 192.168.*.* network. If your running something a bit different like 10.0.0.0 or even 172.0.0.0 then you would run into this.

If you want to use a router as an AP then just dont use the WAN port on it and turn off DHCP. Thats assuming you have a DHCP server already running.



coffee

 

[NETWizz]

Making assumptions here but most network routers by default use 255.255.255.0 mask so each subnet would be cut off from each other. OP's noted that they wanted to access shares wired or wireless. So obviously they are not happy.

You are making assumptions. Most home networks do, but most commercial networks do not.

There are class A, B, and C, which have default masks of 255.0.0.0, 255.255.0.0, and 255.255.255.0 respectively.

Nothing is stopping access to shares via 10.1.2.3/255.0.0.0 and 192.168.1.32/255.255.255.0, sure they most certainly do not overlap in the slightest and are completely separate subnets, but the networking is totally separate from file sharing.

Bottom Line:
If the host is reachable via IP and name it will work provided sharing is setup properly. That is to say Host A can reach Host B if they are both in the same network subnet and directly connected (i.e. via switch, crossover cable...).

That said, let's say host A is 10.1.2.3/8 and host B is 172.16.4.5/16 and host C is 192.168.100.17/24 they CAN ALL communicate just fine with each other if there is a router in the network connecting those networks together. Similarly, nothing precludes a host i.e. Host B from being connected to multiple sub-nets with multiple network adapters.


******************

True, broadcasts do not travel across subsets (unless specifically configured on the network device to force that - stupid idea), but it doesn't matter because any proper network is going to utilize DNS not broadcasts to find hosts.

 

[SAG]

I have seen it alot. Seems alot of routers like the default 192.168.*.* network. If your running something a bit different like 10.0.0.0 or even 172.0.0.0 then you would run into this.

If you want to use a router as an AP then just dont use the WAN port on it and turn off DHCP. Thats assuming you have a DHCP server already running.



coffee

I guess I was assuming the router was the only ting doing DHCP.

 

[nlinecomputers]

You are making assumptions. Most home networks do, but most commercial networks do not.

There are class A, B, and C, which have default masks of 255.0.0.0, 255.255.0.0, and 255.255.255.0 respectively.

Nothing is stopping access to shares via 10.1.2.3/255.0.0.0 and 192.168.1.32/255.255.255.0, sure they most certainly do not overlap in the slightest and are completely separate subnets, but the networking is totally separate from file sharing.

Bottom Line:
If the host is reachable via IP and name it will work provided sharing is setup properly. That is to say Host A can reach Host B if they are both in the same network subnet and directly connected (i.e. via switch, crossover cable...).

That said, let's say host A is 10.1.2.3/8 and host B is 172.16.4.5/16 and host C is 192.168.100.17/24 they CAN ALL communicate just fine with each other if there is a router in the network connecting those networks together. Similarly, nothing precludes a host i.e. Host B from being connected to multiple sub-nets with multiple network adapters.


******************

True, broadcasts do not travel across subsets (unless specifically configured on the network device to force that - stupid idea), but it doesn't matter because any proper network is going to utilize DNS not broadcasts to find hosts.

Yes I know all that. Why are jumping down my butt about this?