Howdy all... need some help/instructions:

I have 2 comps w/ Win98SE

Both hooked to a 10/100 Switch. I need to know how to hook these up using the TCP/IP protocol for networking. I tried NetBUI but it is limited to what i want to do which is share fax programs etc etc.

Can some please point me to some detailed, simplified instructions on how do this.

I want to know how to do it fromt he beginning. So please help and post some instructions.

Thanks.

NetBEUI (NetBios Enhanced User Interface) is rubbish it is a broadcast protocol and is not routable.

LOL... okkk, that i know now about NetBUI... so any help with instructions to TCP/IP protocol?

Set up the computers as part of the same WORKGROUP, enable DHCP and share the drives.

NetBEUI is FINE and FAST for small peer to peer networks. The fact that it is not routable has no bearing here. His LAN is LOCAL, not hopping over routers (yeah, he is plugged into the same router but they are both on the same segment)

If each computer were on a separate subnet, then they could not speak to each other, but when on the same LAN, that is totally fine... and VERY fast because the packets do not have all that OSI layer information added to them.

Again, it is only for very small (10 users or less) peer-to-peer networks.

Since he is using the router to dish out the IP's, and he wants to share his internet connection, he needs TCP/IP anyway. So, do as Jason advised and get rid of all protocols that are not important Keep TCP/IP. Set each computer to use DHCP or obtain an IP automatically (DNS/Gateway auto assign as well), and share the directories.

For application sharing, you really can only host applications with Citrix Terminal Server or Win 2000 Server (Using Citrix Terminal Server)

Or look at products like 3AM Labs RemotelyAnywhere http://www.remotelyanywhere.com/

nope.... manny I do not want to share internet... each comp has a 56k modem and can access the net on their own.

I am on a switch not a router (if that makes a difference)

The program i want to share (faxing) has its own faxshare software built into it. But it calls for an IP address for each comp (HOST/CLIENT) on the LAN so I need to use TCP/IP.

I just need to know how to set up TCP/IP with IP's and all that stuff, what uncheck what to leave checked etc etc under WINS, DNS, etc etc.

Instructions on how to set it up w/ example would be great...

Thanks.

Well, your switch is still a router anyway. I assume that both of your "comps" will be on the same subnet (if you don't know what that is, then nevermind, my question will be answered)

Hell, if they aint sharing your broadband, then why the hell hook them to the switch/router at all? If you do, they WILL be able to share your Broadband anyway whether or not you want them to....

One of the machines will have the software you want to share.. correct?

Just use some unsheilded twisted pair cat3 or 5 cable and run the two machines right to eiach other NIC to NIC.

Assign machine one an IP of 192.168.1.11 and the second 192.168.1.12

Assign both the subnet mask's of 255.255.255.0 (default Class C subnet mask)

And there you have it.

Sorry for not giving out more details Odie, but as you will find out, it is quite simple.

A switch is not a router... routers usually have switches built into them, but a switch alone by itself cannot act like a router. You need to setup the IPs on each computer as this example: 10.0.0.1 (first comp) 10.0.0.2 (other comp) with subnet 255.0.0.0 and the same workgroup name as mentioned and it will work.

ok.... what about gateway? nothing in there? its just a LAN and not for the internet.

You won't need a gateway address if not going on the net with the computers.

The gateway address is the address of a router.

we know that. spare him those details which would only serve to confuse. our little linksys and netgears ARE BOTH. They have to be



Maybe he is on a real switch at work but he did not specify. I guess it was wrong of me to assume.

and why use a class A addressing scheme?

i posted the very same information. you added nothing new to this thread except confusing information for Odie.

192.168.1.11 and 192.168.1.12 are FINE with 255.255.255.0 as the subnet mask.

Address: 192.168.1.1
Netmask: 255.255.255.0 = 24
Wildcard: 0.0.0.255
Network: 192.168.1.0/24
(Class C)Broadcast: 192.168.1.255
HostMin: 192.168.1.1
HostMax: 192.168.1.254
Hosts/Net: 254

Why the heck would he need more hosts than that. And that address is allocated for Private LAN's

here is what you told him to use

Address: 10.0.0.1
Netmask: 255.0.0.0 = 8
Wildcard: 0.255.255.255
Network: 10.0.0.0/8
(Class A)Broadcast: 10.255.255.255
HostMin: 10.0.0.1
HostMax: 10.255.255.254
Hosts/Net: 16777214

Is there any good reason he needs 16,777,214 hosts for a peer to peer network unless he is Damlier Chrysler? (and NOBODY would EVER even have more than a dozen comps peer to peer anyway unless they are insane)

maybe you did not read my earlier post


better yet, if he uses the addresses I specified and a subnet mask of 255.255.255.252

he will end up with 2 hosts, which is all he needs.

Didn't mean to cause any arguments... but hey I'll give it a try this morning when i get in to work.

Thanks for the help. I MAY have more questions!!

right.... all your config crap would confuse the crap out of anyone not knowing what they are doing... what i said will work too... geesh

using 10.0.0.x just SIMPLIFIES EVERYTHING. i go for simplification when it comes to computing... thats why my friends LOVE playing at my LAN parties because I don't have three different domains setup with passwords and internet filtering and 5 different IP configurations... SIMPLIFY!

Any of the Private LAN address's would be fine.

10.0.0.0 - 10.255.255.255 (A)
172.16.0.0 - 172.31.255.255 (B)
192.168.0.0 - 192.168.255.255 ©


Most use Class C 192.168 but it really doesn't matter, its 2 computers !!!!

Odie, this is from windows help, configuring computers on your home network. As mandy says set addresing manually use 192.168.0.01 for first computer 02 for second etc. set subnet mask to 255.255.255.0 no gateway. set for file and printer sharing, was easy after the first time. good luck



To assign a private IP address for a simple network


click here, to open the Network dialog box.
Select the TCP/IP Ethernet adapter from the list titled The following network components are installed.
Click Properties.

To assign an automatic IP address, click Obtain an IP address automatically.
To assign a static IP address, click Specify an IP address, and then type in the IP address and subnet mask.
Notes

You can also open the Network dialog box by clicking Start, pointing to Settings, clicking Control Panel, and clicking Network.
If your computer is configured for automatic IP addressing and is connected to a network that does not have a , it automatically assigns itself an IP address. For more information see Related Topics.
If your computer is connected to a network with a DHCP service and a failure occurs, the computer assigns itself a private IP address. When the DHCP service is restored, the computer gets the DHCP address and relinquishes the private address.
Assigning a static IP address overrides the ability to get addresses dynamically from DHCP servers.
Most private automatic IP addresses use the LINKLOCAL network IP address space and the format is 169.254.X.X. Internet Connection Sharing networks use addresses in the 192.168.0.xxx range.

Thanks steve... i didn't have a chance to try it out yesterday at work.. but i will this week.

Thats seems simple enough

isn't that what I said?

why the hell does everyone say the same thing?

If your computer is connected to a network with a DHCP service and a failure occurs, the computer assigns itself a private IP address. When the DHCP service is restored, the computer gets the DHCP address and relinquishes the private address.

It will use APIPA (Automatic Private IP Addressing) if DHCP fails, best to set up two DHCP scopes with different address allocations on 2 different servers, then if 1 server goes down you enable the other scope.

ok... didn't work

Set comp 1 to 192.168.1.10
Set comp 2 to 192.168.1.20

Subnet mask 255.255.255.0

Also tried DHCP.. nothing

Rebooted... and nothing can't ping them can't do anything. ping says not reachable on all four lines, 100% packet loss.

also, the firewalls were down when i did this.

All the rest of the network tabs seem ok (WINS, DNS, etc etc)

workgruop names are the same on both comps.

Removed the old NetBUEI protocol and added TCP/IP nothing...

tried winipcfg /all... and the only adapter that shows up is PPP both NICs don;t on both comps... yet they are installed and work under NetBUEI...

ummm... help!!!

DHCP wouldn't work unless you have set up a scope on a DHCP server such as Win NT server or 2000 server, or using a router.

They would work under NETBEUI as its a broadcast protocol and needs no configuration at all.

There is nothing wrong with the IP's or the subnet masks, how are the PC's connected together that could be the problem.

Are there routers, bridges, firewall, switches etc in between each PC ?

Exactly how are the PC's connected together ?

Odie,

Jason is correct. It is the switch you have them connected to. My suggestions on hooking them up NIC to NIC and using similar addresses would work, but alas, you are hooking them to some "switch".

Jason is right, we need to know more details in order to help you out. The router would need to have it's tables modified for that particular subnetwork you specified to be "seen" by the network.

two comps are hooked to a AOpen 605u http://www.aopen.com/products/network/swit...tch/aow605u.htm 10/100 switch (not a router like my linksys i have at home which has a switch built in to it) with cat5 patch cables 14' long each.

So basically what your trying to tell me is i cannot utilize TCP/IP due to the switch.

Anyway... thats how they are hooked up. nothing complicated you would think eh?

Hey i appreciate the help guys...

seems to me with what you are trying to do you need two 10-100 cards in each comp except the last,so two comps three cards. 1st comp gets an in and out cable,secound just an in.,
thats the advantage of a router,it gets around this.

Arrr... A Clasic Win98 Problem when playing with networks!!!
Right go into network neighberhod and remove all protocal and cards in there for the type of card u have got, dont remove any thing to do with the modems or dial up networking...
Restart windows and let it be redeteceted...
Then install "client for microsoft networks" make sure that its set to share leve security and then install tcp/ip...
restart then set your ips as mandark says...
DO NOT cut corners because it still will not work!!
Try pinging the other pcs addy if it works pat yourself on the back you have a fully working share level network, if not go and cry in the corner..
If you need any help you know where i am on msn


Im sorry if its not very clear but i dont have a 98 pc to hand to walk myself through


AthlonGod

OK... I'll give that whirl tomorrow morning.. THANKS!

Two NIC's would be for a router, VPN or for being a member of 2 subnets.

What on earth are you talking about Pappy? Why not get a cheapo router/switch instead... ... problem solved.


OR like I said BEFORE!!!! NIC to NIC with Crossover Cat5 cable..... I am asuming you want 100 Mbit/sec speeds right? (are there any 10 Mbit/ser NIC's left over? LOL )


So Odie, if you tried to hook em up NIC to NIC and it would not work, that was your problem... you probably did not have Crossover cables (
sorry i left that little ittybitty tid-bit out )

http://www.homenethelp.com/web/explain/abo...t-crossover.asp

Odie, Odie, Odie.....

You need TCP/IP installed. you can use the NetBEUI as well for computer name resolution.

Dude, once you install TCP/IP and set each manchine up... reboot and test the installation by pinging LOCALHOST

You should run a command/dos box and type:

ping localhost and get replies from the 127.0.0.1 address (reserved for localhost)

If you do not see the replies come back but it says request timed out or any other errors, TCP/IP IS NOT CONFIGURED PROPERLY ON YOUR MACHINE.

Please make it a habit to always test TCP/IP on the local machine BEFORE ever trying to connect to anther machine or device..... That way you have ruled out the possibility that it is the fault of the machine.

Hey hey...

pinged local host and got a response... now what?

still no response from 192.168.1.10

ping localhost on both machines.
then make sure you're using crossover Cat5

then go running after manny

That shows the TCP-IP stack is working.

As all the TCP info is setup right, I would look at the configuration of the switch to be the fault.


For such a simple job, which you know it is, its turning into quite a pain

yes huge pain in the ass...

why would a simple switch limit you to not being able to use tcp/ip

tell me something... I pinged the other computer before when it had NETBEUI on it (before i changed it to TCP/IP) with the LOCALHOST and it pinged to the 127.0.0.1 IP as well... should this happen...

Any more suggestions i might try, because if this is going to be a huge hassle... i am going to fling the thing out the window...

Also... on both comps, can you tell me why the only adapter that shows for winipcfg is the PPP Adapter... shouldn't the NICs be displaying as well?

NOTE TO MICROSOFT: PLUG and PLAY MY ASS... should be just install nics, add TCP/IP, hook to comps and switch done... but no.... fifteen million reboots for shit

NETBEUI doesn't use IP address's, pinging the local host is pinging 127.0.0.1 this has nothing to do with NETBEUI.

Could the switch be blocking the packets ?

Install IPX/SPX :wink:

that's the only network protocol DOOM2 supports btw. should be more than enough for you needs odie

And i figure this out by???... :S

IPX/SPX is an old, pre TCP/IP standard.
just ignore Jason. he hasn't taken his medication today

A lot of Novell networks still use it.

Isn't IPX/SPX a Novell protocol to begin with?

yes... Internet Packet Exchange/Sequenced Packet Exchange was developed by Novel and was the defacto standard for many small/medium business using Novel Directory Servers.

Microsoft did not want to license that stuff so developed their own client and compatible protocols.... NWLINK and crap like that