Windows

General discussion

Gravatar
0 Votes
Locked

network, no domain, no server.

By dnvrtechgrrl ·
I'm making a futile attempt at file sharing. I have a network in place. Two OS's are running, win2k pro and win98. They won't let me have a server, they won't put us on a domain, all we have is a workgroup, and a spare computer set up to reach the shared drive in Dallas. (This is supposed to be our server.)

On the server, I can see some computers, but not all. On the computers:
Some can't see the server-
Some can see the server but nothing shared-
Some can see the server and the shared files-
None of them can see the server, the shared files or all of the other computers on the network-

So far, the best file sharing I've been able to do is to enter the IP into the run command and literally copy the info off the shared drive. Thatis not a permanent solution though.

Is there any way to set this up without being on a true network?

Thanks

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

gravatar
Collapse -

network, no domain, no server.

by bigwon20 In reply to network, no domain, no se ...

YOU CAN CREATE A DFS. DISTRIBUTE FILE SYSTEM. YOU CAN ASSESS YOUR SHARED DRIVES IN DALLAS. BY CREATING A DFS LINK.

gravatar
Collapse -

network, no domain, no server.

by dnvrtechgrrl In reply to network, no domain, no se ...

Poster rated this answer

gravatar
Collapse -

network, no domain, no server.

by dnvrtechgrrl In reply to network, no domain, no se ...

Poster rated this answer

gravatar
Collapse -

network, no domain, no server.

by sgt_shultz In reply to network, no domain, no se ...

first, the LAN:
here is what you need to have all the computers see each other and share resources. you know all this already but i would double-check this stuff:
a) same workgroup name
b) same protocol (tcpip)--recommend the ONLY protocol
c) unique ip addresses, with
d) same subnet mask (eg. 255.255.255.0)
on same 'segment' (i.e. all have same first 3 octets: eg. 10.0.0.x)
e) have netBIOS enabled over tcpip (the default: allows you see computers in the network neighborhood and access byname (as opposed to ip address) at the 'run' command)
f) have shared resources with appropriate user rights (implies 'file and print sharing services' in win98 and 'server' service in win2kpro, these come in by default usually when installing the network card drivers)
once you have all this double-checked, go to each machine and establish you can ping the other machines, especially any you can't see in network neighborhood.
now the WAN. i think all you are lacking is a 'static' route to 'server' in dallas. I don't know if you are ever going to be able to 'browse' for that computer in the network neighborhood, but you could make a shortcut to the resource...
map a drive, etc...
let us know a little more about exactly which os's can't ping or browse, the tcpip address scheme you are using (what is dallas using?)
and maybe we can help more...

gravatar
Collapse -

network, no domain, no server.

by dnvrtechgrrl In reply to network, no domain, no se ...

That did it, thank you!!! Between not having the workgroup allocated correctly and some of the wid98 machines not having file and print sharing as an option, most of the issues are now corrected and I can see all from the server, and most importantly, the pc'c can finally see the server. Thank you both for your time!

gravatar
Collapse -

network, no domain, no server.

by curlergirl In reply to network, no domain, no se ...

What you are doing is called "peer to peer" networking - all of the machines on your network could theoretically serve as either clients or servers. "sgt. schulz" seems to have covered everything except one omission - you have to have File and Printer Sharing turned on on the Win2K machines as well as the Win98 machines in order to be able to see and browse them in Network Neighborhood. Also, if the "server" is a Win2K machine, you will need to be sure that you have appropriate user IDs set up on this machine so that they can acccess the machine itself; and if the file system is NTFS, that they have appropriate access permissions to the resources on the machine so that they can browse, read/write, etc. If it's a Win98, you don't have toworry about the logon or file permissions. Hope this helps!

gravatar
Collapse -

network, no domain, no server.

by dnvrtechgrrl In reply to network, no domain, no se ...

Between not having the workgroup allocated correctly and some of the wid98 machines not having file and print sharing as an option, most of the issues are now corrected and I can see all from the server, and most importantly, the pc'c can finally see the server. Thank you both for your time!

gravatar
Collapse -

network, no domain, no server.

by dnvrtechgrrl In reply to network, no domain, no se ...

This question was closed by the author

Back to Windows Forum

Start or search

Related Discussions

Related Forums