wireless network not connecting fully

CDsDontBurn · Sep 2, 2007, 08:45 AM

so, i'm setting up an office network for a client of mine. the router being used is the common Linksys WRT54G router. I have already set up the SSID, set up a WEP key, DHCP is enabled, and placed in order a class A internal network.

the easy part is already done. all the wired machines are connected and they can all communicate with each other perfectly fine. the part that is stumping me is the single laptop that is supposed to be connected to the network as well. it picks up a signal and attempts to connect via use of the DHCP provided by the router. that's where the problem occurs. the laptop will detect the network, but not obtain a proper IP address; meaning, it won't obtain an IP address that is to be part of the network it's supposed to be in. if i manually set the IP address under the alternative IP address settings, it will connect to the router, but not go online, nor detect the other computers in already in the network.

although, while writing this, i just had the idea of changing the last octet of the subnet mask to allow more computers in the network. i did not set the default subnet of 255.255.255.0. although, i do not see why since all the computers in this network are still below the limit of maximum computers. i'll give it a shot still though.

the last thingi can try is that dumb "run this CD first" CD that comes with the router. honestly, i'd rather not have to use that. i'm smarter than that

Dyre Straits · Sep 5, 2007, 09:07 PM

Hi, CDs!

I see no one has responded to this yet. Have you gotten the problem resolved?

We use the LinkSys Wireless WRT54G here at the house. Most of our PCs are connected via CAT5 cables. However, there's a MAC notebook that connects via Wireless and it's kind of "iffy" due to where we have the router located. We're going to be relocating the router and hubs soon to a central closet hoping this resolves the problem.

Also, when my son brings a notebook home from work, he also connects via wireless and it can sometimes be a problem for the same reason.

Good luck!

**temeteus82** · Sep 5, 2007, 11:00 PM

why you need class A internal network ? when you are good with class C ... (255.255.255.0 subnet) (class A 255.0.0.0 subnet)

CDsDontBurn · Sep 6, 2007, 08:11 AM

Quote:

Originally Posted by Dyre Straits

Hi, CDs!

I see no one has responded to this yet. Have you gotten the problem resolved?

We use the LinkSys Wireless WRT54G here at the house. Most of our PCs are connected via CAT5 cables. However, there's a MAC notebook that connects via Wireless and it's kind of "iffy" due to where we have the router located. We're going to be relocating the router and hubs soon to a central closet hoping this resolves the problem.

Also, when my son brings a notebook home from work, he also connects via wireless and it can sometimes be a problem for the same reason.

Good luck!

i think i got the issue resolved. i think it's the router that's going out. the router will broadcast a signal to wireless devices, but will not allow them to connect. i tried two different laptops to verify this. neither of the two would connect to the network nor would they go online.

the laptop would have been no more than 15ft. away from the router at most.

also, another reason why i think that it's going out, is because of what happened to one of the wired, all 3 wired machines are connectected via cat5e cable, where one of the machines would give a "limited or no connectivity" message, even though it was working perfectly fine 20min. earlier. eventually i tried another port on the router and it connected to the internal network and internet just perfectly.

Quote:

Originally Posted by temeteus82

why you need class A internal network ? when you are good with class C ... (255.255.255.0 subnet) (class A 255.0.0.0 subnet)

well, i guess i'm tricking people who would attempt to hack the network

. i have a class A IP address set up, 10.0.0.1, with a class C subnet, 255.255.255.0. i would have used a true class A subnet if the router allowed it.

anyways, the reason why i did that is because this client of mine is set up for a business, and security is an issue.

Dyre Straits · Sep 6, 2007, 09:05 AM

Just out of curiosity, do you live in an area with lots of lightning? I think you get my point.

CDsDontBurn · Sep 6, 2007, 09:31 AM

southern california and lots of lightning? lol, no

so cali is not a place with much of weather. we have quakes

.

**temeteus82** · Sep 6, 2007, 10:25 AM

Quote:

Originally Posted by CDsDontBurn

i think i got the issue resolved. i think it's the router that's going out. the router will broadcast a signal to wireless devices, but will not allow them to connect. i tried two different laptops to verify this. neither of the two would connect to the network nor would they go online.

the laptop would have been no more than 15ft. away from the router at most.

also, another reason why i think that it's going out, is because of what happened to one of the wired, all 3 wired machines are connectected via cat5e cable, where one of the machines would give a "limited or no connectivity" message, even though it was working perfectly fine 20min. earlier. eventually i tried another port on the router and it connected to the internal network and internet just perfectly.

well, i guess i'm tricking people who would attempt to hack the network

. i have a class A IP address set up, 10.0.0.1, with a class C subnet, 255.255.255.0. i would have used a true class A subnet if the router allowed it.

anyways, the reason why i did that is because this client of mine is set up for a business, and security is an issue.

Sounds like something is wrong with the antenna.... I have Linksys ADSL router with WLAN and I can use it all the way out side. I live in four story building.

Dyre Straits · Sep 6, 2007, 10:27 AM

Quote:

Originally Posted by temeteus82

Sounds like something is wrong with the antenna.... I have Linksys ADSL router with WLAN and I can use it all the way out side. I live in four story building.

That would possibly be true except that CDs mentioned that some of the wired connections are also flaky.

**temeteus82** · Sep 6, 2007, 10:29 AM

Quote:

Originally Posted by Dyre Straits

That would possibly be true except that CDs mentioned that some of the wired connections are also flaky.

heh, Just woke up and didn't notice that.. Thanks. Yeah sounds like the router might need to be replaced with new one...

CDsDontBurn · Sep 6, 2007, 11:36 AM

yea, i will probably end up replacing that router eventually.

oh, i did have another issue with the network. two of the computers were required to share folders. well, only one computer worked for this. the method i used was to map a network drive on the computers requiring the data. two computers are sharing data, and there is one computer just simply sharing the local shared folder for transferring data purposes.

anyways, the issue is that one of the two computers that i set up for sharing data is not allowing the data to be shared. meaning, when i go to any other computer to set up the mapped network drive, whenever i go click on the + symbol to expand that computer, i just get the hour glass for a few seconds and then nothing happens other than the + symbol going away and nothing expanding. the other computer that is also sharing data, works fine to map the shared folder though on the other computers.

yea, those are some of the other issues i encountered with this network setup. probably one of the most difficult i've ever set up due to all the issues i encountered.

**temeteus82** · Sep 6, 2007, 11:40 AM

I've found out that if you are in workgroup the file sharing in pain in the but. But it can be done nicely when the easy file sharing function is disabled and workstations has accounts that are used only to access shares. If you got Domain then it's much easier to do, but you need server for that.

CDsDontBurn · Sep 6, 2007, 11:45 AM

yea, this network was a domain. none of them had any version of windows server installed.

i don't see why sharing folders across multiple computers is a PITA though. IMO, it's a simple task.

Sep 2, 2007, 08:45 AM	#1
CDsDontBurn 127.0.0.1 Join Date: May 2003 Location: Southern California Posts: 22,458 Rep Power: 202 System Specs	wireless network not connecting fully so, i'm setting up an office network for a client of mine. the router being used is the common Linksys WRT54G router. I have already set up the SSID, set up a WEP key, DHCP is enabled, and placed in order a class A internal network. the easy part is already done. all the wired machines are connected and they can all communicate with each other perfectly fine. the part that is stumping me is the single laptop that is supposed to be connected to the network as well. it picks up a signal and attempts to connect via use of the DHCP provided by the router. that's where the problem occurs. the laptop will detect the network, but not obtain a proper IP address; meaning, it won't obtain an IP address that is to be part of the network it's supposed to be in. if i manually set the IP address under the alternative IP address settings, it will connect to the router, but not go online, nor detect the other computers in already in the network. although, while writing this, i just had the idea of changing the last octet of the subnet mask to allow more computers in the network. i did not set the default subnet of 255.255.255.0. although, i do not see why since all the computers in this network are still below the limit of maximum computers. i'll give it a shot still though. the last thingi can try is that dumb "run this CD first" CD that comes with the router. honestly, i'd rather not have to use that. i'm smarter than that __________________ Her First Day \| A year later

Sep 6, 2007, 09:31 AM	Thread Starter #6
CDsDontBurn 127.0.0.1 Join Date: May 2003 Location: Southern California Posts: 22,458 Rep Power: 202 System Specs	southern california and lots of lightning? lol, no so cali is not a place with much of weather. we have quakes . __________________ Her First Day \| A year later

Sep 6, 2007, 11:36 AM	Thread Starter #10
CDsDontBurn 127.0.0.1 Join Date: May 2003 Location: Southern California Posts: 22,458 Rep Power: 202 System Specs	yea, i will probably end up replacing that router eventually. oh, i did have another issue with the network. two of the computers were required to share folders. well, only one computer worked for this. the method i used was to map a network drive on the computers requiring the data. two computers are sharing data, and there is one computer just simply sharing the local shared folder for transferring data purposes. anyways, the issue is that one of the two computers that i set up for sharing data is not allowing the data to be shared. meaning, when i go to any other computer to set up the mapped network drive, whenever i go click on the + symbol to expand that computer, i just get the hour glass for a few seconds and then nothing happens other than the + symbol going away and nothing expanding. the other computer that is also sharing data, works fine to map the shared folder though on the other computers. yea, those are some of the other issues i encountered with this network setup. probably one of the most difficult i've ever set up due to all the issues i encountered. __________________ Her First Day \| A year later

Sep 6, 2007, 11:45 AM	Thread Starter #12
CDsDontBurn 127.0.0.1 Join Date: May 2003 Location: Southern California Posts: 22,458 Rep Power: 202 System Specs	yea, this network was a domain. none of them had any version of windows server installed. i don't see why sharing folders across multiple computers is a PITA though. IMO, it's a simple task. __________________ Her First Day \| A year later