Home Network
Mar 26, 2006 | 06:57 PM
#1
Thread Starter
Registered User
Joined: Sep 2002
Posts: 1,520
Likes: 1
From: woodstock, ga
Home Network
I need some help as I am obviously missing something. I want to set-up a home network so we can access files off of my desktop and print using our Laptop. I will take you through the hardware i currently have and how it is currently set-up and you can tell me what I am doing wrong.
DSL Modem-->Linksys Wireless Broadband Router-->My Desktop connects to this Router via firewire and my wife's laptop via the wireless PCMCIA card that came with the router.
I ran the "Setup a wireless network for a home or small office" in Windows and have the same settings transferred to both computers however I can't get the computer to show up on "View Workgroup Computers" on my PC and vice versa with my desktop on the Laptop.
What gives?
I also would like to share my printer but have already selected it as shared under its properties tab.
DSL Modem-->Linksys Wireless Broadband Router-->My Desktop connects to this Router via firewire and my wife's laptop via the wireless PCMCIA card that came with the router.
I ran the "Setup a wireless network for a home or small office" in Windows and have the same settings transferred to both computers however I can't get the computer to show up on "View Workgroup Computers" on my PC and vice versa with my desktop on the Laptop.
What gives?
I also would like to share my printer but have already selected it as shared under its properties tab.
Mar 27, 2006 | 05:17 AM
#2
Registered User
Joined: Jan 2003
Posts: 4,087
Likes: 1
From: Hattiesburg, MS
Are you sure your'e connected via firewire? I've yet to see a router that accepts a firewire connection. Maybe you mean a Cat5 cable?
Usually from my experience, 90% of the reason home networks don't work are firewall issues. Do you have a software firewall running? If so, you'll need to open the necessary ports for sharing.
All you really have to do to set up a network is to put both computers on the same workgroup. You can check this by right clicking My Computer, then Properties, then Computer Name. Click the "Change" to see which workgroup you're on and change it if needed. The actual computer name itself doesn't matter as long as it's not something extremely long. Once you do that and reboot if necessary, you can select which folders and printers you want to share.
This site has a wealth of information you could use to read up more on this topic: www.ezlan.net.
Usually from my experience, 90% of the reason home networks don't work are firewall issues. Do you have a software firewall running? If so, you'll need to open the necessary ports for sharing.
All you really have to do to set up a network is to put both computers on the same workgroup. You can check this by right clicking My Computer, then Properties, then Computer Name. Click the "Change" to see which workgroup you're on and change it if needed. The actual computer name itself doesn't matter as long as it's not something extremely long. Once you do that and reboot if necessary, you can select which folders and printers you want to share.
This site has a wealth of information you could use to read up more on this topic: www.ezlan.net.
Mar 27, 2006 | 06:43 AM
#3
Thread Starter
Registered User
Joined: Sep 2002
Posts: 1,520
Likes: 1
From: woodstock, ga
Originally Posted by Churnd
Are you sure your'e connected via firewire? I've yet to see a router that accepts a firewire connection. Maybe you mean a Cat5 cable?
Usually from my experience, 90% of the reason home networks don't work are firewall issues. Do you have a software firewall running? If so, you'll need to open the necessary ports for sharing.
All you really have to do to set up a network is to put both computers on the same workgroup. You can check this by right clicking My Computer, then Properties, then Computer Name. Click the "Change" to see which workgroup you're on and change it if needed. The actual computer name itself doesn't matter as long as it's not something extremely long. Once you do that and reboot if necessary, you can select which folders and printers you want to share.
This site has a wealth of information you could use to read up more on this topic: www.ezlan.net.
Usually from my experience, 90% of the reason home networks don't work are firewall issues. Do you have a software firewall running? If so, you'll need to open the necessary ports for sharing.
All you really have to do to set up a network is to put both computers on the same workgroup. You can check this by right clicking My Computer, then Properties, then Computer Name. Click the "Change" to see which workgroup you're on and change it if needed. The actual computer name itself doesn't matter as long as it's not something extremely long. Once you do that and reboot if necessary, you can select which folders and printers you want to share.
This site has a wealth of information you could use to read up more on this topic: www.ezlan.net.
Mar 27, 2006 | 06:50 AM
#4
Registered User
Joined: Jan 2003
Posts: 4,087
Likes: 1
From: Hattiesburg, MS
Something is blocking communication between the computers. If you set up two XP machines and put them on the same workgroup, they will see each other straight out of the box. It doesn't take much at all to make this happen. So, software firewall? Antivirus?
Mar 27, 2006 | 06:51 AM
#5
Registered User
Joined: Mar 2006
Posts: 2,276
Likes: 1
From: Montana USA
Make sure your windows firewall is off when you are trying to do any networking, and if you are using an antivirus, make sure you have its firewall off as well (Norton is a real crappy one when it comes to that, since you have to go through a lot of stuff just to find the firewall.) After you do all that, you should reboot your machines, and it should work right after that.
Mar 27, 2006 | 07:32 AM
#6
Thread Starter
Registered User
Joined: Sep 2002
Posts: 1,520
Likes: 1
From: woodstock, ga
both computers are running zone alarm and the windows firewall. i guess i will just have to play around with it some more tonight when i get home from work. they do recognize each other now (atleast they both show up under workgroup computers) i just can't access either one from the other computer.
Trending Topics
Mar 27, 2006 | 10:30 AM
#8
Contributing Member
Joined: Mar 2006
Posts: 1,775
Likes: 0
From: San Antonio, TX
Call Linksys if all else fails or use the chat for help, that is what I ended up doing. be sure to encrypt and turn on security in the router.
support website
http://www.linksys.com/servlet/Satel...VisitorWrapper
support website
http://www.linksys.com/servlet/Satel...VisitorWrapper
Last edited by kmcc78240; Mar 27, 2006 at 10:31 AM.
Mar 27, 2006 | 10:48 AM
#9
Thread Starter
Registered User
Joined: Sep 2002
Posts: 1,520
Likes: 1
From: woodstock, ga
Originally Posted by kmcc78240
Call Linksys if all else fails or use the chat for help, that is what I ended up doing. be sure to encrypt and turn on security in the router.
support website
http://www.linksys.com/servlet/Satel...VisitorWrapper
support website
http://www.linksys.com/servlet/Satel...VisitorWrapper
Mar 27, 2006 | 11:48 AM
#10
Sponsor
Joined: Jul 2004
Posts: 9,173
Likes: 6
From: Puyallup WA.
I have my computer set up the same way. i have my 2 external hard drives connected to my desktop which are then shared so i can access the drives wirelessly anyhwere in the house. i then have the printer hooked up to another computer also shared.
one thing you can try is enter the IP address directly. goto start > Run > type "cmd" (without the " "s) this will open a dos window, then type ipconfig <enter> this will show you the IP address. since you are going through the router it probably will be a 192.168.x.x (where x is a number between 0 and 255) once you get the IP of the desktop, using the laptop open My Computer and in the address bar type \\192.168.x.x (assuming your internal IP address is 192.168. something) this should open a window that will show "shared printers" "shared pictures" shared etc, open the printers folder and double click on the printer. of couse you need to have the printer shared for it show up. but it will then add the shared printer to the laptop's printers, open printers/faxes and make sure its set as the default printer.
you then can now add a network drive for the folders/ drives you want to access on the desktop from the laptop. do this by clicking on my computer, then goto tools > Map Network Drive. follow the set up wizard to get it set up.
hope this helped, if you have any more questions feel free to PM me or send me an message on AIM.
one thing you can try is enter the IP address directly. goto start > Run > type "cmd" (without the " "s) this will open a dos window, then type ipconfig <enter> this will show you the IP address. since you are going through the router it probably will be a 192.168.x.x (where x is a number between 0 and 255) once you get the IP of the desktop, using the laptop open My Computer and in the address bar type \\192.168.x.x (assuming your internal IP address is 192.168. something) this should open a window that will show "shared printers" "shared pictures" shared etc, open the printers folder and double click on the printer. of couse you need to have the printer shared for it show up. but it will then add the shared printer to the laptop's printers, open printers/faxes and make sure its set as the default printer.
you then can now add a network drive for the folders/ drives you want to access on the desktop from the laptop. do this by clicking on my computer, then goto tools > Map Network Drive. follow the set up wizard to get it set up.
hope this helped, if you have any more questions feel free to PM me or send me an message on AIM.
Last edited by ToferUOP; Mar 27, 2006 at 11:51 AM.
Mar 27, 2006 | 11:52 AM
#11
Registered User
Joined: Dec 2002
Posts: 9,048
Likes: 2
From: Seattleish, WA
{Chris just posted up the same basic question(s). I'm gonna post anyway 'cause of the example text}
Did you try turing off ZoneAlarm?
Past that... with the router in place, can both the desktop and laptop reach the Internet?
If so... (assuming that we're talking about Windows XP) from each machine, do this:
Then... While you're still at the command prompt:
Again, please post the results from each machine.
You can cut & paste out of the command window - you'll want to set "quick edit" mode on the window:
Once you set that, then you can use the mouse to highlight the window text, then CTRL-C to copy, switch to a message here, and CTRL-V to paste.
Originally Posted by justinh
My internet network works fine, I don't think that Linksys will be able to help with the problems i am having.
Past that... with the router in place, can both the desktop and laptop reach the Internet?
If so... (assuming that we're talking about Windows XP) from each machine, do this:
- Start button
- "Run"
- "cmd" {enter}
- ipconfig /all {enter}
- you'll get something like:Code:
c:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : xxxx Primary Dns Suffix . . . . . . . : ???.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : ???.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : ???.com Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-xx-D3-FC-xx-E8 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : xxx.xx.xx.xxx Subnet Mask . . . . . . . . . . . : 255.255.252.0 Default Gateway . . . . . . . . . : xxx.xx.xx.xxx DHCP Server . . . . . . . . . . . : xxx.xx.xx.xxx DNS Servers . . . . . . . . . . . : xxx.xx.xx.xxx xxx.xx.xx.xxx Primary WINS Server . . . . . . . : xxx.xx.xx.xxx Secondary WINS Server . . . . . . : xxx.xx.xx.xxx xxx.xx.xx.xxx Lease Obtained. . . . . . . . . . : Monday, March 27, 2006 4:39:18 AM Lease Expires . . . . . . . . . . : Tuesday, March 28, 2006 4:39:18 AM
Then... While you're still at the command prompt:
- "net config workstation" {enter}
- you'll get something like:Code:
c:\>net config workstation Computer name \\xxxxxxxxx Full Computer name xxxxx.com User name xxxxx Workstation active on NetbiosSmb (000000000000) NetBT_Tcpip_{E31F24E6-BB43-4856-BFE4-9BA3DB8B5D89} (0013D3FCDFE8) Software version Windows 2002 Workstation domain xxxxxx Workstation Domain DNS Name xxxxxx.com Logon domain xxxxxx
Again, please post the results from each machine.
You can cut & paste out of the command window - you'll want to set "quick edit" mode on the window:
- Right click on the title bar (red circled area):
- Click PROPERTIES
- Check "QuickEdit Mode"
- Click OK
- Select "Save... for future"
- Click OK
Once you set that, then you can use the mouse to highlight the window text, then CTRL-C to copy, switch to a message here, and CTRL-V to paste.
Last edited by midiwall; Mar 27, 2006 at 11:54 AM.
Mar 27, 2006 | 12:40 PM
#12
Contributing Member
Joined: Feb 2006
Posts: 61
Likes: 0
From: Waxhaw, NC
What OS are both pcs running? The guys are on the right path with the firewall and IP questions, once you have established that both pcs can ping each other, then it is going to turn into a rights/permissions issue. Post the results as midiwall suggests and we will have you running in no time.
Mar 27, 2006 | 01:12 PM
#13
Thread Starter
Registered User
Joined: Sep 2002
Posts: 1,520
Likes: 1
From: woodstock, ga
thanks for all of the advice. when i get home i will try turning the zone alarm off and see if that works. fyi, they are both running XP Home. Like i said, neither computer has any problem connecting to the internet, this is the second wireless internet network i have set-up and neither has had any problems in the last 3 years. The whole purpose for this was so that my wife can conveniently print from her laptop instead of unplugging the printer from the desktop and plugging it into the laptop and work on the same files from either computer.
Mar 27, 2006 | 01:34 PM
#14
Registered User
Joined: Dec 2002
Posts: 9,048
Likes: 2
From: Seattleish, WA
Okay, then I'll shortcut the verbose examples. 
Check to be sure that both machines are on the same workgroup. Control Panel | System | Computer Name | Change. Be sure that "workgroup" is checked and that both machines are set the same. (Chris pointed this out earlier)
Once you know the machine names, and that they're in the same workgroup, you can validate WINS by pinging them with the names... From a prompt, ping {machinename} (no brackets). If you don't get a response __FROM BOTH DIRECTIONS__ then you have a WINS issue that needs to be resolved. That's why one machine can't see the other.
You can also try to bypass name resolution... Get the IP's for both machines, then from a prompt: net view xxx.xxx.xxx.xxx That should give you a list of shares on each machine, (storage or printer). If it doesn't, then you have a basic comm issue _between_ the machines.
Given that you can get outside, then we can pretty much assume that both machines are running DHCP and that they're on the same subnet.
Like JD said - if you can ping each machine from the other (and I'll toss in that you need it to work by name) then you'll looking at a permissions issue. But, XP Home doesn't have a lot of the options (read, "potential for trouble") that XP Pro does, so this shouldn't be the problem.
And, that would bring us back to ZoneAlarm.
...which btw, you don't need. I HATE software firewalls. argh.
Check to be sure that both machines are on the same workgroup. Control Panel | System | Computer Name | Change. Be sure that "workgroup" is checked and that both machines are set the same. (Chris pointed this out earlier)
Once you know the machine names, and that they're in the same workgroup, you can validate WINS by pinging them with the names... From a prompt, ping {machinename} (no brackets). If you don't get a response __FROM BOTH DIRECTIONS__ then you have a WINS issue that needs to be resolved. That's why one machine can't see the other.
You can also try to bypass name resolution... Get the IP's for both machines, then from a prompt: net view xxx.xxx.xxx.xxx That should give you a list of shares on each machine, (storage or printer). If it doesn't, then you have a basic comm issue _between_ the machines.
Given that you can get outside, then we can pretty much assume that both machines are running DHCP and that they're on the same subnet.
Like JD said - if you can ping each machine from the other (and I'll toss in that you need it to work by name) then you'll looking at a permissions issue. But, XP Home doesn't have a lot of the options (read, "potential for trouble") that XP Pro does, so this shouldn't be the problem.
And, that would bring us back to ZoneAlarm.
...which btw, you don't need. I HATE software firewalls. argh.
Mar 27, 2006 | 01:55 PM
#15
Sponsor
Joined: Jul 2004
Posts: 9,173
Likes: 6
From: Puyallup WA.
Originally Posted by midiwall
And, that would bring us back to ZoneAlarm.
...which btw, you don't need. I HATE software firewalls. argh.
...which btw, you don't need. I HATE software firewalls. argh.
Mar 27, 2006 | 02:03 PM
#16
Registered User
Joined: Dec 2002
Posts: 9,048
Likes: 2
From: Seattleish, WA
Originally Posted by ToferUOP
agreed. most people think they need one.. but really they dont. you only need a firewall if you are acting as a server.
Running a nice little Linksys/Netgear box will handle most of the general user's firewalling needs. If not, then move on up to Cisco or somesuch. But don't let rogue packets contaminate your network - at all!
Last edited by midiwall; Mar 27, 2006 at 02:07 PM.
Mar 27, 2006 | 02:14 PM
#17
Registered User
Joined: Jan 2003
Posts: 4,087
Likes: 1
From: Hattiesburg, MS
I'm with Mark... the only time I ever recommend a software firewall is when the user is on dialup, which I hate to do because dialup is slow enough as it is and a firewall is only gonna slow things down a little more. But if they insist on dialup (or can't get anything else), then it's a very necessary pain.
Mar 27, 2006 | 03:29 PM
#18
Thread Starter
Registered User
Joined: Sep 2002
Posts: 1,520
Likes: 1
From: woodstock, ga
Originally Posted by midiwall
Okay, then I'll shortcut the verbose examples.
Check to be sure that both machines are on the same workgroup. Control Panel | System | Computer Name | Change. Be sure that "workgroup" is checked and that both machines are set the same. (Chris pointed this out earlier)
Once you know the machine names, and that they're in the same workgroup, you can validate WINS by pinging them with the names... From a prompt, ping {machinename} (no brackets). If you don't get a response __FROM BOTH DIRECTIONS__ then you have a WINS issue that needs to be resolved. That's why one machine can't see the other.
You can also try to bypass name resolution... Get the IP's for both machines, then from a prompt: net view xxx.xxx.xxx.xxx That should give you a list of shares on each machine, (storage or printer). If it doesn't, then you have a basic comm issue _between_ the machines.
Given that you can get outside, then we can pretty much assume that both machines are running DHCP and that they're on the same subnet.
Like JD said - if you can ping each machine from the other (and I'll toss in that you need it to work by name) then you'll looking at a permissions issue. But, XP Home doesn't have a lot of the options (read, "potential for trouble") that XP Pro does, so this shouldn't be the problem.
And, that would bring us back to ZoneAlarm.
...which btw, you don't need. I HATE software firewalls. argh.
Check to be sure that both machines are on the same workgroup. Control Panel | System | Computer Name | Change. Be sure that "workgroup" is checked and that both machines are set the same. (Chris pointed this out earlier)
Once you know the machine names, and that they're in the same workgroup, you can validate WINS by pinging them with the names... From a prompt, ping {machinename} (no brackets). If you don't get a response __FROM BOTH DIRECTIONS__ then you have a WINS issue that needs to be resolved. That's why one machine can't see the other.
You can also try to bypass name resolution... Get the IP's for both machines, then from a prompt: net view xxx.xxx.xxx.xxx That should give you a list of shares on each machine, (storage or printer). If it doesn't, then you have a basic comm issue _between_ the machines.
Given that you can get outside, then we can pretty much assume that both machines are running DHCP and that they're on the same subnet.
Like JD said - if you can ping each machine from the other (and I'll toss in that you need it to work by name) then you'll looking at a permissions issue. But, XP Home doesn't have a lot of the options (read, "potential for trouble") that XP Pro does, so this shouldn't be the problem.
And, that would bring us back to ZoneAlarm.
...which btw, you don't need. I HATE software firewalls. argh.
Mar 27, 2006 | 03:49 PM
#19
Contributing Member
Joined: Feb 2006
Posts: 61
Likes: 0
From: Waxhaw, NC
My 2 pennies, midiwall seems to know his stuff along with churnd, I might debate software firewall versus hardware (way too long a discussion), XP home is somewhat difficult to deal with sometimes, I would suggest that the same user accounts exist on both pcs, share the printer on the main computer, my guess from what you have provided is that ZA is blocking the print traffic, you will probably disable Zone Alarm and everything will work like a champ. If not, then it is very likely a authority issue, which means granting access to the other computers logged in user account will clear up the issue. My kids are ready for bed, I can help tommorrow if need be. The guys on this forum seem to be as good with CPUs as they are with Toyotas so I'm guessing this will be solved by morning.
Mar 27, 2006 | 06:16 PM
#20
Registered User
Joined: Dec 2002
Posts: 9,048
Likes: 2
From: Seattleish, WA
(thanks for the confidence JD!)
Okay, this means that the browse info is okay, so WINS is working.
or... ???
Ummm.. that's REALLY confusing.
I know you said that you've done this before, but I truely believe that MS has made network installs too difficult with their "configure wireless connection" crap. It's just ... argh.
I'll be installing my upteenth wireless network tomorrow night. This is what I'm looking to do:
Laptop will be wireless - it's already been known to work on another network.
I think it'll take me 20 minutes, most of that time will be waiting for the Linksys to power up and the machines to reboot if I have to change a workgroup name ("shouldn't have to...").
My point here is that I've NEVER used that Wireless Network Setup Wizard thing... I don't get it. I think it confuses more crap than it solves.
USB? Flashed a profile? A disc? eeek.
Originally Posted by justinh
quick question though that might save me some time later on. When i got to "view workgroup computers" on either computer both computers show up. I just get the error stating that "I can't access the network device."
or... ???
However, I am not sure that this means they are seeing each other or if this is a result of me using the USB option to set-up the network (main computer, then additional computers, then back to main) so I wasn't srue if that flashed the profile on to the disc and made it available when it actually isn't.
I know you said that you've done this before, but I truely believe that MS has made network installs too difficult with their "configure wireless connection" crap. It's just ... argh.
I'll be installing my upteenth wireless network tomorrow night. This is what I'm looking to do:
- Unpack Linksys router and power it up
- Disconnect cable modem from desktop
- Connect Linksys to cable modem
- Connect Desktop to port on Linksys
- Verify desktop configured for DHCP
- Note name of workgroup while I'm in the general area
- Hit shell prompt, "ipconfig /release", "ipconfig /renew". Shouldn't HAVE to do this, but I like knowing it actually happened.
- Note that IP address was assigned
- ping cnn.com (I don't care about getting packets, I just wanna see DNS work)
- Load browser, hit CNN.com
- Control Panel | Printers
- Right click on default, "Sharing", "Share this printer", enter name, OK.
- From browser, hit 192.168.1.1 (router config)
- Set SSID, set WEP (yeah, I know), set channel if possible
Laptop will be wireless - it's already been known to work on another network.
- Hit Control Panel | System | Computer Name | Change
- Set workgroup to be same as desktop
- Load laptop's wireless setup (usually an icon in systray)
- "Discover networks" or some such
- Find the new network's SSID
- Click - enter WEP password
- Should be connected
- START - Run - "\\{desktop name}", should see shares.
- Right click on printer
- "Map network device" (I think that's the pick)
- Printer should install
I think it'll take me 20 minutes, most of that time will be waiting for the Linksys to power up and the machines to reboot if I have to change a workgroup name ("shouldn't have to..."
).My point here is that I've NEVER used that Wireless Network Setup Wizard thing... I don't get it. I think it confuses more crap than it solves.
USB? Flashed a profile? A disc? eeek.
Last edited by midiwall; Mar 27, 2006 at 06:18 PM.
