Network Address?

[Lee]

I have (or would like to have) a simple dirct 2 computer ethernet cable Lan
using
TCP\IP with addresses 192.168.1.1 and 192.168.1.2 between a desktop STUDY
with OS Wxp SP2 and a laptop using OS W98 but I can't get the two of them to
see
each other. The the IP conection works fine with apps like Fastlynx and
Maxivista. I have read and and attempted many of the remedies I've seen
offered to others here and elsewhere without success. I did get them going
briefly but changed something and now they are blind to each other although
previously I was able share resources.

A few questions I can't seem to find answers for anywhere:
1 In the Properties\Advanced tab of the Realtek PCMCIA a number of
options are available:
APM Wake up
Early Tx Threshold
Link down Power saving
Link speed/Duplex Mode
Network Address
WakeUp Frame

What should I put in these, in particular the Network Address which has a
value of twelve zeros at the moment.

2 In XP Admin\Services I tried to activate the TCP\IP NetBios Helper but
get the error: 1068 Startup Unsuccseful (my sysytem is in Italian) . Should
I have this running? How do I get it to run?

4 On the Laptop (W98) the Enable NetBios over TCP\IP is greyed out
although it does have a tick in it. Is that OK?

5 I have no gateway (it is a direct connection) is that right or should
I put something in there?

Any help will be greatly appreciated.

 

[Guest]

Hi Lee,

Are you using a crossover cable ? Are both computers in the same workgroup
and do they both have unique names ? Do you have File & Printer Sharing
enabled on both computers ? Are there any software firewalls blocking
incoming connections ? Have you tried using NetBEUI instead of TCP/IP to
establish a connection (for what you need, this would be ideal) ?

Regards Colin.

 

[Guest]

Install netbui in both the computers.

 

[Guest]

install netbui.

 

[Malke]

install netbui.

Netbeui is absolutely unnecessary.

Lee, from the above it looks like you are trying to make a peer-to-peer
connection using Windows Internet Connection Sharing (ICS). I'm not
sure what you mean by "works fine with appls like Fastlynx and
Maxivista" however. If you are using ICS, the gateway computer needs to
be assigned 192.168.0.1 and the other computer 192.168.0.xx (your
choice). You need two network adapters in the gateway computer, one
going to the Internet and one going to the client computer. The
gateway-client connection must be done with a crossover cable.

An alternative to ICS is a simple router, which would then be connected
to the cable/dsl modem. In that case, only one nic in a machine is
necessary and you would set the computers to get their IP addresses
automatically from the router.

Since you haven't told us exactly what you are doing, how you connect to
the Internet, or what you've tried, it's hard to be more specific.

Frankly, in all the networking I've done, I've never had to change
anything in those properties. Neither should you if the network is set
up correctly.
So here you're saying you are not using a router, but are using ICS? In
that case, you've got the IP addresses set wrong. I don't believe ICS
will work with anything but the 192.168.0.xx range.

Here are some links to help you. MVP Steve Winograd's site (bcmaven)
covers ICS very well:

http://www.bcmaven.com/networking/faq.htm
http://www.michna.com/kb/wxnet.htm - Small Network Troubleshooter by
Hans-Georg Michna

http://www.practicallynetworked.com/howto/

Malke

 

[Lee]

Netbeui is absolutely unnecessary.


Lee, from the above it looks like you are trying to make a peer-to-peer
connection using Windows Internet Connection Sharing (ICS). I'm not
sure what you mean by "works fine with appls like Fastlynx and
Maxivista" however. If you are using ICS, the gateway computer needs to
be assigned 192.168.0.1 and the other computer 192.168.0.xx (your
choice). You need two network adapters in the gateway computer, one
going to the Internet and one going to the client computer. The
gateway-client connection must be done with a crossover cable.

An alternative to ICS is a simple router, which would then be connected
to the cable/dsl modem. In that case, only one nic in a machine is
necessary and you would set the computers to get their IP addresses
automatically from the router.

Since you haven't told us exactly what you are doing, how you connect to
the Internet, or what you've tried, it's hard to be more specific.


Frankly, in all the networking I've done, I've never had to change
anything in those properties. Neither should you if the network is set
up correctly.

So here you're saying you are not using a router, but are using ICS? In
that case, you've got the IP addresses set wrong. I don't believe ICS
will work with anything but the 192.168.0.xx range.

Here are some links to help you. MVP Steve Winograd's site (bcmaven)
covers ICS very well:

http://www.bcmaven.com/networking/faq.htm
http://www.michna.com/kb/wxnet.htm - Small Network Troubleshooter by
Hans-Georg Michna

http://www.practicallynetworked.com/howto/

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

Thanks for the response. I am sorry I was not clear. I am trying simply to
connect a laptop directly (no router) to a desktop by cable using TPC/IP as
the only protocol. The desktop is has a DSL connection to internet through
its own adaptor but being a newbie to networking I was not attempting at
this stage to connect the laptop to the internet through the destop but
merely to share resources. However, if I can use ICS for that, it would be
a bonus.

By mentioning Fastlynx and Maxivista I meant that the IP connection between
the computers works with these third party applications, I asume this
confirms
that the setup was in part at least correct.

I mention the gateway and the other options becuase I am unsure why the two
cannot see each other and am grasping at straws. In the tutorials I have
read it seems straight-forward and at this point the two should communicate.
But they don't and as you see I don't have a clue why not.

The laptop (W98) shows itself in Network Neigbourhood by the Desktop (XP)
does not even list itself in MSHOME. Although it has done so earlier. I
have altered the IPs to 192.168.0.1
and 192.168.0.2 but without success.

Here are the IPcongif files:

The LAPTOP

Windows 98 IP Configuration
Host Name . . . . . . . . . : LAPTOP
DNS Servers . . . . . . . . :
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No


0 Ethernet adapter :
Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :



1 Ethernet adapter :
Description . . . . . . . . : Realtek 8139-series PCI NIC
Physical Address. . . . . . : 00-50-FC-D7-88-2F
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . :
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :


And the DESKTOP

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : STUDY
Primary DNS suffix . . . . . . . :
Node Type . . . . . . . . . : Unknown
Routing IP enabled. . . . . . . . . : No
Proxy WINS enabled . . . . . . . . : No


Adapter Ethernet LAN:
Suffix DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : NVIDIA nForce MCP Networking
Controller
Physical Address. . . . . . . . . . . : 00-0D-87-91-EF-33
DHCP enabled. . . . . . . . . . . . : No
Address IP. . . . . . . . . . . . . : 192.168.100.1
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over TCPIP. . . . . . : Disabled



Adapter PPP Alice ADSL:
Suffix DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . . . : 00-53-45-00-00-00
DHCP enabled. . . . . . . . . . . . : No
IP Address. . . . . . . . . . . . . : 80.181.112.15
Subnet mask . . . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 80.181.112.15
Server DNS . . . . . . . . . . . . . : 81.74.229.227
151.99.125.1

NetBIOS over TCPIP. . . . . . : Disabled

Hope this can shed some light.

Lee

 

[Lee]

Thanks for the response. I am sorry I was not clear. I am trying simply
to
connect a laptop directly (no router) to a desktop by cable using TPC/IP
as
the only protocol. The desktop is has a DSL connection to internet
through
its own adaptor but being a newbie to networking I was not attempting at
this stage to connect the laptop to the internet through the destop but
merely to share resources. However, if I can use ICS for that, it would
be
a bonus.

By mentioning Fastlynx and Maxivista I meant that the IP connection
between
the computers works with these third party applications, I asume this
confirms
that the setup was in part at least correct.

I mention the gateway and the other options becuase I am unsure why the
two
cannot see each other and am grasping at straws. In the tutorials I have
read it seems straight-forward and at this point the two should
communicate.
But they don't and as you see I don't have a clue why not.

The laptop (W98) shows itself in Network Neigbourhood by the Desktop (XP)
does not even list itself in MSHOME. Although it has done so earlier. I
have altered the IPs to 192.168.0.1
and 192.168.0.2 but without success.

Here are the IPcongif files:

The LAPTOP

Windows 98 IP Configuration
Host Name . . . . . . . . . : LAPTOP
DNS Servers . . . . . . . . :
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No


0 Ethernet adapter :
Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : 44-45-53-54-00-00
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :



1 Ethernet adapter :
Description . . . . . . . . : Realtek 8139-series PCI NIC
Physical Address. . . . . . : 00-50-FC-D7-88-2F
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . :
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :


And the DESKTOP

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : STUDY
Primary DNS suffix . . . . . . . :
Node Type . . . . . . . . . : Unknown
Routing IP enabled. . . . . . . . . : No
Proxy WINS enabled . . . . . . . . : No


Adapter Ethernet LAN:
Suffix DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : NVIDIA nForce MCP
Networking Controller
Physical Address. . . . . . . . . . . : 00-0D-87-91-EF-33
DHCP enabled. . . . . . . . . . . . : No
Address IP. . . . . . . . . . . . . : 192.168.100.1
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
NetBIOS over TCPIP. . . . . . : Disabled



Adapter PPP Alice ADSL:
Suffix DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . . . : 00-53-45-00-00-00
DHCP enabled. . . . . . . . . . . . : No
IP Address. . . . . . . . . . . . . : 80.181.112.15
Subnet mask . . . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 80.181.112.15
Server DNS . . . . . . . . . . . . . : 81.74.229.227
151.99.125.1

NetBIOS over TCPIP. . . . . . : Disabled

Hope this can shed some light.

Lee

I see these readouts have differing Ip addresses, that is just a momentary
oversight. They communicate okay through IP as I said (when I put the right
IPs in) but still will not "see" each other.

 

[Malke]

"Lee" <[email protected]> ha scritto nel messaggio
news:[email protected]...

See comments inline:

You have to put the desktop in there as the gateway, 192.168.0.1.

Try making the above IP address 192.168.0.1. If it is really the way you
have it there, that would explain the issue.

Other than the above, when it comes to ICS, I'm not the right person.
I'm sure Steve Winograd or another expert will come along. I haven't
used ICS for many years because I never thought it worked very well. If
I were you, I would just go buy a cable/dsl router and use that.
However, if your heart is set on ICS, then use it.

In the meantime, go through MVP Hans-Georg Michna's network
troubleshooter as I suggested earlier. It will help you narrow down the
problems. Here's the link again:

http://www.michna.com/kb/wxnet.htm

Malke

 

[Lee]

See comments inline:


You have to put the desktop in there as the gateway, 192.168.0.1.


Try making the above IP address 192.168.0.1. If it is really the way you
have it there, that would explain the issue.

Other than the above, when it comes to ICS, I'm not the right person.
I'm sure Steve Winograd or another expert will come along. I haven't
used ICS for many years because I never thought it worked very well. If
I were you, I would just go buy a cable/dsl router and use that.
However, if your heart is set on ICS, then use it.

In the meantime, go through MVP Hans-Georg Michna's network
troubleshooter as I suggested earlier. It will help you narrow down the
problems. Here's the link again:

http://www.michna.com/kb/wxnet.htm

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

Thanks, Malke. The incorrect Ip listed was because I had been trying
different IPs and the Iplog hadn't been updated. I do have that angle
covered. I am getting help now from Chuck in this newsgroup, see NetBios
Helper posts.
Thanks again for your help.
Lee

 

[Guest]

Check that both computers are in same workgroup or not.

 

[Lee]

Got it fixed, Phew Thanks to all for help.

Check that both computers are in same workgroup or not.