Urban75 Home About Offline BrixtonBuzz Contact

Linking computers.....

run a packet trace of the 95 machine connecting to the router. let's see what's going on here. also, this may be an obvious question but the router *is* a switch too, isn't it?
 
I love these threads where people pile in with answers before asking questions. Please don't spoil it :mad: ;)

But yeah, I've been thinking that the very first thing I'd do would be to try things out with a dumb hub (that does not need its own ip address). We know the crossover cable worked, so a dumb hub must also do the trick. Surely? :hmm:

That will confirm that the ip stacks on the client machines are OK, and configuring the router/switcher is the only problem.
 
Yep.

And I'd not worry about netBIOS myself. It's inessential and very insecure (mind you, I'm a bit :eek: at the thought of Win95/98 on the net at all).

As I understand it the present position is
I can now ping the server from the windows 95 PC and I can ping the 95 PC from [the win98] PC but the router hasn't picked up the 95 PC's name.
I'm thinking this means the router has assigned a name to the win98 PC using bind (DNS) based on the MAC code of its network interface card. In that case, a similar entry somewhere in the router's management interface, but for the win95 machine, should help.
 
wouldn't it just

"look, just let me at it to thrash around and to mess with the kit and settings until it works, ok?" :)
 
If you're having to fuck about with NetBEUI, best of luck...

Tbh, it's getting to the point where the answer is "get an OS that isn't 12 years out of date".
 
One doesn't need to. The ip stack is all that's needed for internet (tcpip) stuff.

But yeah, do check Puppy Linux (or maybe Damn Small Linux). You can boot and install them from CD. And keep all your windows stuff. Either will run fine on your hardware, and give you the best of modern software for your purposes.
 
No, I'd imagine if NetBIOS is ticked, you shouldn't need to be messing with NetBEUI (although it's been a long while since I tried to actually hookup a Win95 machine).

An OS which uses TCP/IP and DNS, instead of NetBIOS and WINS would be even better, though. :)
 
The point about loading Netbeui is to get the two machine talking. We can sort out the technicalities later.
 
:eek:

And for all modern networking purposes its just the tcpip stuff that's needed, that's why I'm leery of introducing complications with other protocols and applications. But perhaps it would help deployment in this instance.

It does seem the problem's half sorted at least. Any news WouldBe?
 
netbeui... wow there is a blast from the past

without reading the rest of the thread I am guessing authentication or personal firewall

oh and bin off all that new fangled Ethernet stuff.. Token ring adapters and a MAU are what you need
 
As I understand it the present position is I'm thinking this means the router has assigned a name to the win98 PC using bind (DNS) based on the MAC code of its network interface card. In that case, a similar entry somewhere in the router's management interface, but for the win95 machine, should help.

Can't find any settings like that on the router.


It needs to be on both.
Netbeui is on both and still not working.

No, I'd imagine if NetBIOS is ticked, you shouldn't need to be messing with NetBEUI (although it's been a long while since I tried to actually hookup a Win95 machine).

With it being greyed out I'm not sure it applies it.

sometimes windows wont let computers talk if they arent on the same workgroup...

They are. I've even changed the workgroup name on one PC to uppercase the same as the other PC just in case it's case sensitive and it's still not working.




On the router it's set up as

Auto Ip - disabled
DHCP server - enabled.

Yet doesn't seem to like DHCP on the 2 PC's. :confused:
 
This is interesting ...
Win95 supplies a program (\Windows\Winipcfg.exe) that displays the DHCP info in a nice graphical way. By examining the strings in winipcfg.exe, I discovered that it has undocumented options that will also write the information to a file ("Winipcfg.out", by default).
source
It sounds as if you may be able to find out and post the DHCP configuration for each of the client machines. Someone may spot something if you do!
 
I've run winipcfg.exe on both machines and get
Code:
Host name                          95PC.aoldsl.net      98PC.aoldsl.net
DNS Servers                       192.168.1.254        192.168.1.254
Node type                          Hybrid                   Broadcast
NetBIOS scope ID                blank                     blank
IP Routing enabled               unticked                 unticked  
WINS proxy enabled             unticked                 unticked
NetBIOS resolution uses DNS  ticked                    unticked

Ethernet adaptor info           NDIS 4.0 driver         PPP adapter
Adapter address                  00-e0-7d-a5-69-be  44-45-53-54-00-00
IP adress                           192.168.1.65           0.0.0.0
subnet mask                       255.255.255.0         0.0.0.0
default gateway                  192.168.1.254         blank
DHCP server                        blank                     255.255.255.255
Primary WINS server             192.168.1.254         blank
Sec WINS server                  blank                     blank
Lease obtained                     blank                    blank
Lease expires                       blank                    blank
 
tbh with just two machines i would use a staic ip address

95pc

192.168.1.20/24*
default gateway 192.168.1.254 (assuming this is the router)
wins server 192.168.1.254

98pc the same except

ip address 192.168.1.21/24*



just for good measure add the relevant entries into the hosts file on both PCs



then see if you can connect.

also seriously look at ANY personal firewall settings with particular regard to any entries for:

netbios
files and printer sharing


then on each pc create a folder and share it (initially can set read\write access for anonymous and lock it down afterwards). use this to test rather than the C$ share as you will be able to mess about with permissions better



eta the /24 denotes a 255.255.255.0 netmask
 
I booted up AOL on the 95 machine last night as I'd 'lost' an e-mail address and wondered if it was stored on the PC. AOL installed some extra software on detecting an ethernet broadband service and momentarily it all worked OK. Nothing appears to have been changed under any of the protocol or adapter properties but some values have changed using winipcfg.exe. Both PC's are now using PPP adapter and Broadcast node type.

Something then went wrong and my 95 PC cant see the network neighbourhood but can ping the router. The router sees to 98 PC's both with the same name plugged into different ethernet ports.

Anyway the 98 PC now sees the 95 PC in the network neighbour hood and can access the shared drive so I can now transfer files from 1 PC to another without having to resort to floppy disks. :eek: :)
 
Back
Top Bottom