Networking

[trevorjd]

You'll probably think that I am as think as a plank, but, although I have a network card in each of my two computers and a cable link between them, I still can't get them to talk to each other and share my DSL internet connection. The system I have is a basic belkin network. Can anyone out there help me? Thanks in advance for your help.

[nickc]

What OS are you using? Is it the right cable - if you are using a standard cable then you will need a hub to join them.

Nick

[trevorjd]

Hi there and thanks for the reply. I am using Win ME and the Belkin kit included the connecting cable which links my two computers. I think that the physical set up is right but I don't have any success with the Belkin Networking wizard which is supposed to set up the correct interface. Hope you can help. Trevorjd.

[voodooboy]

Have you gone here?
http://web.belkin.com/support/

Type in Window ME into the search box. I got a ton of references refering to ME issues with the Belkin system.

This is going to be your best resource.

[SyrenSong]

I've just moved this topic to IT Discussion forum, in the hope that you'll get some answers to your problem, trevorjd.

Hope it helps! :)

[southplatte]

First off, what type of dsl connection do you use? do you have a dsl router or switch, or do you have a dsl card in one of the computers?

This will help determine which steps to take to finish the setup. Most likely the belkin network setup disc will not setup the internet sharing if one of the machines has a dsl card in it.

Once we know this, we can then determine the appropriate setup for the network and components.

[Dragonsi]

On the same subject but a different setup, I have my win2000pro (acting as server) and my laptop (XP home) and printer networked (at last) via a 10/100 ethernet via a hub. I have just got an old PC up and going running win98 with a new 10/100 card installed. After several hours of playing with the IP/TCP settings, the win98 box is seen by the network but a path cannot be established. Any suggestions please?

[redcircle]

I would suggest a router that has DHCP. This will auto-assign IP's to the computer. also make sure that all the computers are on the network. Run any available updates such as tcp/ip etc. There is a good one by linksys that also includes a firewall.

in order to be seen on the network make sure you have file & printer sharing turned on in the network options and try sharing a folder.

[southplatte]

Recircle brings up an excellent point, use a router with dhcp.

Alternatively, with win98 forward, you can use internet connection sharing and have windows itself act as a simple router/dhcp server for your network, provided that machine has two nics (one for internet and one for internal network).

Drgonsi -- on your setup, verify the following networking components on each system:

file and printer sharing
client for microsoft networks
tcp/ip

tcp/ip >> you will want private ip address on all systems (if a system has multiple nics, you need to set the binding for each nic as well)

192.168.0.100-192.168.0.103 with default subnet of 255.255.255.0

try pinging from a command prompt
c:\>ping 192.168.0.100

as well as

c:\>ping *hostname*

If the ip ping works, but the hostname doesn't then check the client for microsoft networks installation on the 98 machine. I have had trouble in the past getting 2k/xp to connect up with 98 since both 2k/xp use more security.

Win2K and XP both can use automatic ip addressing, where if you do not specify the ip and do not have dhcp on the network win auto assigns one. Win98 implements this to some extent, but it will be better to specify one to match your 2k/xp systems.

Dragonsi & trevorjd -- if either of you need extra help feel free to pm. I can make a visual to show the network setups that should exist to accomplish what you want, as well as the ip addressing based upon the hardware present.

[redcircle]

Originally Posted by southplatte

If the ip ping works, but the hostname doesn't then check the client for microsoft networks installation on the 98 machine. I have had trouble in the past getting 2k/xp to connect up with 98 since both 2k/xp use more security.

To get past the problem ith 98 machines connecting to 2k/xp simply create a username on the 2k/xp machine and make sure you use that name when logging into the 98 machines.

note: on xp home there is a max of I think 2 users at a time and 10 with xp pro. Also xp home cannot connect to a domain.

[southplatte]

Redcircle has it right again -- I wasn't thinking on that one.

BTW - are you by chance ms certified redcircle? Just curious as I am working on the mcse path....

[netman4ttm]

Go to the command prompt on each machine

Type ipconfig at the prompt

Tell us what you get

[netman4ttm]

Check the following:
1 is workgroup name the same on the each machine, if it isn't make it so

2. Is the machine name differrent for each machine, if not make it so.

3. Is each machine uniquely named, that means no machine has the same name as a user, if not make it so.

4. Is there a common user/password on each machine, not the Administrator, if not make it so.

5. Does each machine have an ip number (192.168.1.x) and is each number unique x, x+1 x+2 etc.

6. The ipconfig command will answer that question.

[Dragonsi]

Here's my setup, this is from the top of my head as it's late, I've been sat here about 18 hours getting my system back up after a fatel crash (see my thread on W2K & SP4) and I need some sleep.

Please note, I have no network training, this has been done through trial and error...

Win 2000 pro:
Using a proxy server (AlegroSurf) with a preset IP 192.168.0.x - subnet 255.255.255.0 - gateway 192.168.0.x+1 > all this under TCP/IP settings
File & Print scharing is on and so is Microsoft Client Network.
I have also set WINS to the same IP address (?).
No DNS has been set & no domain name has been set except nameing the unit under Network ID.
All local settings are listed as 'localhost'.
This unit is being treated as the server and connect to the net.

Win XP Home:
Same setup, IP number = x+2
Gateway is same as w2k unit
WINS is same IP as w2k unit
no DNS listed
unit is named via Network ID

This was working fine until the reinstall of w2k last night and then nothing. I installed IPX/SPX NetBios on both units (auto number) and the network is working but a bit slow on the hunt.

I tried the same setup with win98 but nothing, it wont evan see itself under 'My Network Places'

Everything connect through a LAN hub (no router) including my HP printer, which has always worked ok - this also has a preset IP 192.168.0.xxx

Before I added the IPX/SPX - the 2 main units (w2k & XP) would see each other but neither would let each other in (no permission message). Each unit could enter itself and view shared folders but not the other unit.

I hope this makes sence, cos not much makes sence at the moment....

Now - where's my bed...

[southplatte]

Hmm....

Remove the Wins IP/Server info on all machines - unless you are running a Wins server (on NT/2k Server) you do not need this name resolution service.

Also, on the gateway, unless the alegrosurf requires you to set this, or it does it automatically, you should not need this on these machines (unless your isp requires you to do so, though most don't any more).

Remove the ipx/spx service - this is where the connectivity is coming from possibly, however should not be needed.

The possibility of the slowness comes from the Wins server info coupled with the ipx/spx. Your machines are trying to "find" each other using wins (windows internet? naming service) which does not exists, then it uses the microsoft client and is deciding on tcp/ip or ipx/spx.

system configs should have the following networking components:

client for microsoft networks
file & printer sharing (if you use this)
tcp/ip

tcp/ip config:

win2k:
IP: 192.168.0.1
Sub: 255.255.255.0
wins: none
dns: none (unless required by alegrosurf or isp)
gateway: none (unless required by alegrosurf or isp)

winXPhome:
IP: 192.168.0.2
Sub: 255.255.255.0
wins: none
dns: none (same)
gateway: none (same)

win98:
IP: 192.168.0.3
Sub: 255.255.255.0
wins: none
dns: none (same)
gateway: none (same)

all machines named different, all part of the same workgroup name (workgoup, or homenet etc)

win2k/xp home will need accounts for each of the other computers (win2k needs: xp/98, xp needs: 2k/98)
to allow connections to the shared resources. This account should be for what ever username/pw you use from the client machine( winxp logon is xpuser, win2k needs a winxpuser account) unless you connect as an admin or enable guest access, neither of which is recommended.

win98: try the setup as above, then see if it sees itself, also try to run at a command prompt window:
c:\> ping 127.0.0.1

This verfies the tcp/ip on the Win98 machine. If you get echo replys good, if not, remove and reinstall the networking components on the win98 machine.

The hub should not need an IP address, and the printer should follow suit with a 192.168.0.4 or similar address.

Hopefully you get this figured out!

If all else fails, what I do after this much frustration is remove all the networking components from all the machines and start over from scratch. Get the win2k going first, connected to the ineternet, then the xp then the 98 machines. Build each one identical on the networking components.

[Dragonsi]

Thanks - I originaly tried what you listed above but found that (w2k & xp only) both units were seen by each other but would not let each other in. Would this be because I was login in with the same user name and password on both units?

I did notice that once, the w2k unit let me in under the same login (as was being used on the w2k unit) and let me browse the shared drives/folders - if I then tried accessing one of these files, the w2k unit crashed - this is a login conflict I take it?

If this is the problem (same user/password) I think I now know where I was going wrong. I shall try what you have suggested and let you know how it goes..

:)

[Dragonsi]

That's done it!

I've created different logins for each unit on each unit... blar blar blar... and now everything is working ok, evan Linux can see the w2k unit and internet... cool - silly mistake but there you go..

I haven't tried win98 yet, that's my next mission.

Thanks all, couldn't ov done it wit ou chou...

[Dragonsi]

Nope...

I just tried setting up the network as describe above by southplatte... I removed everything (IPX, QoS, WINS) except IP numbers and submaks for both w2k and the xp unit (no win98 yet)

Tried 'My Network Places > Windows Network' - nothing, neither unit showing up.

I then added a default gateway that matched each units IP addess > they both showed up, the w2k unit could access both machines but the xp unit could only access itself with a 'no permission' warner when trying to access the w2k unit.

All this with the firewall down... What's happening now?

[southplatte]

sorry it has been a while since I was on here -- I have had a rough two weeks in school with tests and projects.

Let me know if you are still having some trouble or if you got it to work Dragonsi

[Dragonsi]

I've sent you an email...