12 total posts
What OS and which is a server?
Domain networks are things we see with Windows Server 2000 and 2003 or some others. Sometimes an owner installs their network to use a domain by mistake.
The laptop is on xp home, network sets up fine and joins and creates workgroups well. XP pro says its on the workgroup I created but it wont recognize the workgroup. In my network places when I try to view network computers it just gives me a "ding". Doesn't matter if the firewall is on or off or if the ip is fixed or auto. The workgroup doesn't show up. Usually I can see atleast my own comp on the network, nothing here.
Since you have no server the word...
"domain" should never be seen or written about here. If you see "domain" then your install is improper.
Since you have no DHCP server you'll have to assign IP addresses manually. Tell me what you used so the picture of the setup is complete. Also you need to have accounts on both machines and directories shared.
Example. Your account is called 'sam'. 'sam' must have an account on both machines with same password please.
The problem is that the comp won't join or create
workgroup anywhere. With or without a server, the workgroup set up just doesn't work. I hauled the thing to the office and I can get to the internet through the network but again I can't join or create any workgroups. At home, I manually set the ip as
sometimes I leave the bottom empty and i've tried all sorts of combos on the ip numbers, close numbers or far apart. Even without the cable plugged in, I can't set up a workgroup, something I can do with the laptop.
The default route is not used.
Since you don't have a router it's not used at all.
I didn't read how you dealt with accounts and shares so that's an open item. Also you can try the command line and this command if you feel you have the accounts and shares proper.
Think it was a bad install or something
Got desperate and uninstalled and reinstalled all windows components and now the networking works. Sorry for the trouble and thanks for the help. You wouldn't happen to know anything about sharing permissions over a network would you? I'm sharing stuff over a large dispersed network that I don't want just anyone to use but I don't know how to set the permissions for another computer over the network. Thanks
Once you know...
It seems so simple.
We have that Guest account which we rarely enable but that allows everyone to gain access. And the word "Anyone" is anyone with an account, not "everyone" which would be those without an account.
"but I don't know how to set the permissions for another computer over the network."
In short, Windows doesn't do this! But we could add it in by installing OpenSSH so one could stelnet into said 'server' and use the various net and other command line tools to adjust users and more.
Thanks for all the help. When I scrounge up the cash I'll think about getting a "real" network but when you have all the equipment for free, its hard not to try.
did you remember the PAIR switch on the crossover cable
are you using a premade cross over cable or a self made
if self made one pair has to switch in the middle of the connector ends and it easier just to use a store baught cross over cable even as cheap and easy to use a cheap router between the 2 and forget the cross over cable period color code is useless when connecting ethernet cables as long as they are the same match on each end of the connector when using a cross over cable one of the pair has to CROSS OVER in the middle of the connector
if you use a router you will have more security and control over how data flows to and from the other computer and you dont need an INTERNET connection for the router as well it is its OWN DCHP (internet server)
and then you will be NETWOKING the real way and not just from computer to computer and that helps a whole lot in the transfer of DATA along the network path as from computer to computer One of your computers acts as the DCHP and you have to install or turn on the dhcp SERVICE in xp and above WHICH makes the computer you turned it on at THE DHCP \router which causes the cpu 1(DCHP) to work hard as it has to use cpu cycles to do a routers job (routers have cpu in them around 200mhz)RISKS processors and other hardware that do what your computer would have to do to be a router Thus taking the load off your computers period from computer to computer networking you have to one COMPUTER 1\dchp\server to 2 COMPUTER 2\client and if you have to be the server you cpu might not be able to handle the load as most servers use DUAL PROCESSORS for traffic use and the router does the same thing with having to be big and bulky and if your cpu on both machine arent at least a gigahertz or better you will have sluggish preformance on the computer that is the DHCP if you have to use it while both are on and are useing the network and if one of these computers is tied to the internet and not secure in everyway then your computer network can be hacked into easily even if you use software firewalls you can still be hacked and both machines can be turned to zombies causing all kinds of problems for you the user that is why when you network computers that tie to the internet you should always you an access point instead of crossover netwoking most routers these days dont cost 50000 for home netwoking and you can pick them up cheap linksys 99 dlink 99 and so on and that sure beats building a pc just to be your router\DCHP\server then you can also connect both computers as clients to the router head over to cnets netwoking page and read on how to setup a netwok if you need any more help its all there and linksys has one dlink has one cisco does have one but it is more geared toward IT TECHS and some of the info may confuse you if you are just getting started into networking
Free beats pay
Thanks for the info but I already have all the crossover equipment for free. I'll just have to secure the old fashion way for now, unplug the cable.
your are not lost yet
there are other ways to secure them if you must use it
and unplugging is the easiest if you dont know much about netwoking the computer using the crossover connection is somewhat secure JUST USING the crossover cable the PC that is the DHCP is the one that needs to be secure