Can I create a home network over a router, like I can over a hub? I've tried for countless hours myself, and have searched the web for help with no luck.
I have a D-Link DI-604 broadband internet router
Thanks in advance,
-Adam
Printable View
Can I create a home network over a router, like I can over a hub? I've tried for countless hours myself, and have searched the web for help with no luck.
I have a D-Link DI-604 broadband internet router
Thanks in advance,
-Adam
yes you can.
set all your computers to obtain an ip address automatically (your router prolly supports DHCP)
Plug all the computers into the router with straight thru or patch cables not crossover
Then set the workgroup on each computer to something simple like Network, workgroup, Home, ect.
Make sure each computer has a different computer name
Make sure file and print sharing is enabled
ask if you need any further help
I do all that and it says:
"Homenet is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The list of servers for this workgroup is not currently available"
What should I do now?
how many computers you got and what os's are each of them
what what os was the computer you were trying to access and what was the os of the computer trying to access it.
what is Homenet? the workgroup or a computer or printer?
I have 3 computers....two Windows XP home and one Windows 2000 Professional
I was just trying to access the 'view workgroup computers' when I got that error message
Homenet is the name of my workgroup
Any firewall applications running?
First lets check if TCP/IP protocol is working...
goto Start > Run
Type command
then type
Ping 127.0.0.1
do this for each computer
make sure that it says
Code:Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\ABX>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\DOCUME~1\ABX>
Do that for each computer if the result in bold is the same as what you get then TCP/IP is working
Now...
Goto Start > Run
Type Command
Click OK
Type ipconfig
Press Enter
Write down the number in bold or remember it (it will not be in bold when you do this)Code:Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.
C:\DOCUME~1\ABX>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
C:\DOCUME~1\ABX>
Then Type Ping [Number]
For Me it would look like this:
The IP address in bold should be replaced with yours and then next bold statement should be the same as mine if not you have got a problem with the network card in this machineCode:
C:\DOCUME~1\ABX>ping 192.168.2.101
Pinging 192.168.2.101 with 32 bytes of data:
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Reply from 192.168.2.101: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.2.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\DOCUME~1\ABX>
Do this for each computer and make a little table of the values so i can tell you exacally what to do, also tell me the results of each test
eg)
Computer Name | IP Address | OS
--------------------------------------------------
Computer 1 192.168.2.1 WINXP-PRO
Computer 2 192.168.2.1 WINXP-HOME
.....
OK Here's the table
celeron950 192.168.0.100 WINXP-HOME
hpnotebook 192.168.0.101 WINXP-HOME
pii300 192.168.0.102 WIN2K-PRO
the last entry, pii300, is not on the network yet....but will be added once I get enough cat5 to reach its location in the house
Did you run the test on each computer? What were the results?
Double check each computers workgroup and network card duplex settings.
if you want me to talk you though it add me on msn ([email protected])
Disable the Windows XP Firewall, to do this goto Control Panel>Network Connections>Goto Properties on the LAN connection.
On the advanced tab deselect "Protect my computer...".
Now on the Authentication tab deselect "Enable IEEE 802.1x..."
That should help..... Hopefully
No, the windows firewall will NOT cause such an error. I run it myself with no problems.Quote:
Originally posted by Admiral Michael
Disable the Windows XP Firewall, to do this goto Control Panel>Network Connections>Goto Properties on the LAN connection.
On the advanced tab deselect "Protect my computer...".
Now on the Authentication tab deselect "Enable IEEE 802.1x..."
That should help..... Hopefully
Just make sure all of the computers have the EXACT same workgroup name and they were all restarted so you can check
t may, it does on my computer. It depends on the configuration. Just disable it to see if its the problem.
In Windows 2000:
Under the Network and Dialup Connections, under Local Area Connection, add the protocol "File and Printer Sharing for Microsoft Networks"
In Windows XP:
Under Networking (I think, don't have an XP Box here), select the option "Allow this computer to share files and folders with others on the network"
Make sure you router has a built in switch. If it doesnt then it wont work.
How do I find out if my router is/has a switch?
It would say it on the router box, mine says "EtherFast® Cable/DSL Router with 4-Port Switch"
Mine just says "DI-604 Express EtherNetwork Broadband Router", so I guess its not a switch then
Whether it has a switch or not is irrelevant. All routers contain at least a hub.
A switch is a type of hub, but it inspects each packet being sent and only sends the packet to the intended destination. A hub on the other hand forwards the packet to all connected nodes.
The problem you're experiencing, imnsho, is that of Windows Networking - in terms of workgroups and domains and all that.
I'd start by finding out which is setup as the master browser of your little workgroup.
You can do this by, from dos :
nbtstat -a computer_name
And check which is the master browser. That computer is then the one that is basically in control of the workgroup.
You'd also want to ensure that there exists the same username and passwords on each of the machines.
Now obviously if these were all WinXP Pro machines things would be a lot easier.
I suggest that in your startup folder on each machine you create a batch file to authenticate yourself with each of the other machines.
So, assuming you have 3 computers, PC1, PC2 and PC3, and that you're using the username & password - Administrator & blahblah respectively :
Code:ON PC1 :
net use \\PC2 /USER:Administrator blahblah
net use \\PC3 /USER:Administrator blahblah
ON PC2 :
net use \\PC1 /USER:Administrator blahblah
net use \\PC3 /USER:Administrator blahblah
ON PC3 :
net use \\PC1 /USER:Administrator blahblah
net use \\PC2 /USER:Administrator blahblah
That will authenticate each machine with each other machine on the network at startup.
If the other machines aren't going to be on all the time, then I'd suggest simply creating a batch file in your root folder with an easy to remember name, and run that when you want to use file sharing etc. on your network.
If this was a Windows NT or 2000 network, with a WindowsNT or Windows2000 Server acting as the PDC, then it would be a lot easier. But alas, such are the woes of home networks!
I was planning on upgrading the three machines to XP pro. How would that make things easier?
It should do yes.
Ideally, if I were to be setting up a home network, I would just use the Administrator account and ensure the same password on each machine.
Therefore when one machine tried to authenticate with another machine with the current username&password there should be no problems.
But home networks are a pain in the ass. Don't worry that you're the only one having problems or that you're doing something wrong!
Windows XP Pro would be preferable over Windows XP Home.