|
PureBytes Links
Trading Reference Links
|
Here are my three suggestions (try them in this order) that helped in
solving this little riddle on my own network:
For the NT machine, from past experience of pulling my hair out: you have to
have Net BUI installed (but don't bind to the internet connection) to get
your NT box to show up on network neighborhood. Silly isn't it?
Make sure that under the identity tabs for your machines, they have
different names. This may be a quick solve to your problem.
Assign a unique IP # to your machines under network settings. Be sure to
make it in a "safe" IP range such as: 192.168.0.1 - 192.168.255.255. Assign
this unique IP # to your LAN cards (not to the internet connection).
Security tips:
Unbind your internet connection from all bindings. This will avoid many of
the security loopholes inherent in many of those protocols.
Question:
What is NShare, and is there a web site where I can learn about it?
Patrick White
----- Original Message -----
From: "sen" <senfl@xxxxxxxxxxxxxxx>
To: <omega-list@xxxxxxxxxx>; <realtraders@xxxxxxxxxxxxxxx>
Sent: Monday, November 22, 1999 11:09 AM
Subject: LAN question with NT workstation and Windows 98 and 3 tips
This weekend I made my first excursion into a home LAN. I purchased a 4 hub
system by Netgear / Baynetworks.
The machine I use to connect to my dial up ISP is a 133 Pentium with 128megs
of RAM and runs NT workstation 4.0 with service pack 5.
I have it connected to a Hewlett Packard 450 mhz. machine with 128 megs of
RAM running windows 98.
When I double click on Network Neighborhood on the NT machine, I only see
the 98 machine listed in the Network.
When I double click on Network Neighborhood on the 98 machine, I only see
the 98 machine listed in the Network.
I can transfer files from the NT machine to the 98 machine.
I can ping the NT machine from the 98 machine.
The service tech at Netgear duplicated my problem exactly, but he said he
couldn't figure it out. Does anyone have any ideas how I can see my NT
machine on the Network ?
Tips:
Per Sentinal Trading's advice, I went into network properties and unbound
Net Bios from TCP IP. It really helped my security score on
http://www.dslreports.com/r3/dsl/secureme
Thanks Sentinal.
I also think it would be a good idea to have the system communicate via Net
Beui, because it is faster. However, I think I have to leave TCP IP on for
Tradestation 2000 to work.
Finally, I am using Nshare as recommended by CNET. It works without a proxy
server and is the easiest thing to use. A tech at Netgear said everyone
there uses Sygate if you want to use a proxy server. They preferred it over
Wingate because of its simplicity and not crashing their networks.
|