Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How come TCP/IP does not work?

Status
Not open for further replies.

emzabala

MIS
Oct 12, 2002
29
US
I have a peer to peer network.
Windows 2000 Professional which I am using as a file server.
The rest of the PCs are Windows 98SE machines.

I have shares on the Windows 2000 Professional pc which all the 98 pcs map to.

I tried to set it up with just TCP/IP but it does not work. Why?
I had to add NetBeui for all the pcs in order for them to see each other?

When I first had just TCP/IP they would not see each other.
I only gave the pcs an IP address and subnet mask. No default gateway and no DNS since it is only peer to peer. Does TCP/IP just not work in a peer to peer?

Thanks for your help.
 
Of course you can use TCP/IP. You must install File and Printer sharing on each computer and enable it.
 
check also , that NetBIOS is NOT disabled on your NIC.
Subnet Mask MUST be the same on each PC!
can you ping from each pc any other PC?


Victor K
psas@canada.com
MCSE+I;MCSA;MCSE(w2k);CNE(5.1);MCNE(6);CIWSP;CIWSA.
 
Accessdabbler:
I did install File and Printer sharing. It still does not work.

VictorKozlov:
I only want a TCP/IP only peer-to-peer network. I do not want NetBios/Netbeui.

How can I have a peer-to-peer network with Windows 2000 Professional and Windows 98 pcs?
Using only TCP/IP?

 
emzbala,
Yes, you can have a p2p network with only TCP/IP... you may wish to enable NETBIOS over TCP/IP... that should resolve your issues...

What you did not mention about the network shares is whether or not you gave permissions to the everyone group? This is done by default... Do you have logons associated with your win98 machines? If so, do those accounts have id's on your win2k machine...? If not, create id's for them using the same pwords... Have you installed Client for Microsoft Networks on the win98 boxes? debonairOne

"I look in the mirror and what do I see..."
dboneanime.gif
 
Emzabla,

Did you give all the PCs an IP address in the same range? There is no problem using TCP/IP for this type of network (I've been using it in ever changing config with all varieties of Windows with no serious problems, so suspect you just haven't set it up properly. Win98 machines can occasionally 'loose' the network & you sometimes have to remove/reinstall networking for them, but you're suggesting network not working at all. As you say it is working with netbeui, presume other elements like Client for microsoft windows, sharing etc are all properly installed and configured).

PS. Can you ping one PC from another using their IP addresses? What dos ipconfig (2k machine command prompt) or winipcfg (run box on 98) tell you about machine's IP addresses?
 
OK! Definitely you can use TCP/IP protocol only.
I completely agree with Mr.wolluf - check the protocol configuration on ALL PC's. Check IP's and SubnMasks. SubnMasks in your case on all pc's must be the same.


Victor K
psas@canada.com
MCSE+I;MCSA;MCSE(w2k);CNE(5.1);MCNE(6);CIWSP;CIWSA.
 
Debonairone:
Why will I enable Netbios? If I only want TCP/IP?

Well I have already set up the peer to peer using Netbeui so I do have users created so permissions and shares are not the issue.
Yes all the subnet masks are the same and they are all in the same IP address range.

Windows 2000 Professional as a File Server with shares with user accounts and permissions, all users are in the administrators group.
Windows 98 Client pcs.

How can I set it up to be TCP/IP only peer to peer network?
 
How are you defining "Not working"?

Does that mean that the computers cannot ping one another? Or are you saying that they don't appear in one another's "Network Neigborhood"?

If you can ping the computers, but cannot see them in the Network Neighborhood, and do not have either:

1: DNS
2: Wins
3: NetBIOS over TCP/IP

enabled, then it sounds to me as if your system is working as designed. TCP/IP alone does not have a "Friendly Name" facility, so there would be nothing to publish in your network neighborhood.

If you want to use "Friendly Names" on a small network, and don't want to enable another protocol, you can create a "Hosts" file for each computer, which will perform DNS/WINS type functions on a local basis.

I hope that helps
 
It is wierd. When I set it up with just TCP/IP the 98 pcs can all see each other.

No I do not have DNS, WINS, NETBIOS over TCP/IP. All I set up is TCP/IP protocol.
Assigned static ip addresses and matching subnet masks.
File and Printer sharing enabled.

The 98 pcs can see each other but the Windows 2000 Professional machine is not seen by the others.

Wierd huh?
 
Forgive me, but I am still unclear on what you mean by "See".

From one of the Win98 PC's, can you ping the ip address of the Win2KPro PC?

If yes, at the same PC, right-click on Network Neighborhood and choose "Find Computer". Type in the IP address of the Win2kPro computer and click "Find Now".

Does it find the Win2kPro PC with a location "Unknown"?

If yes, replace the IP address with the Win2k PC's name and Click "Find Now" again. Is it found again?

If the first test works, but the others don't, you will almost certainly have to install another protocol. The computer names displayed in Network Neighborhood are the computer's NetBIOS names. If you have File and Printer Sharing installed on your Win98 machines, then you are not running a pure TCP/IP network - you are running NetBIOS over TCP/IP. If TCP/IP is the only protocol installed on your Win2K PC, then THAT is why you can't see it in the Network Neighborhood. Installing NetBEUI on the Win2k Machine should get you going.

Here is a pretty good article that describes how to make your computers play nice together:



Please give these ideas a shot and let us know what the results of each test are and we'll see if we can't get you a workable solution.

Allen
 
Within our Network we also have to add netbeui, It won't work without it. Enabling it does not affect anything, it's not a networkable protocol. So just add NetBeui and all should work.
 
Thanks to all that replied.

I am not sure if it is a bug but I did searches on Google and alot of configurations have to be done in order to just have an all TCP/IP peer to peer.

I will just leave it alone with Netbeui as a protocol.

Thanks for all the suggestions
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top