Unbrowsable Network...sometimes

This is a discussion about Unbrowsable Network...sometimes in the Windows Hardware category; Hi all, I'm running a simple 3 computer TCP/IP network at home with my machine being the only one using Win2K. After installing and configuring the OS for my network (workgroup name, etc. ) I was able to browse the network freely.

Windows Hardware 9627 This topic was started by , . Last reply by ,


data/avatar/default/avatar38.webp

3 Posts
Location -
Joined 2000-03-03
Hi all,
 
I'm running a simple 3 computer TCP/IP network at home with my machine being the only one using Win2K. After installing and configuring the OS for my network (workgroup name, etc.) I was able to browse the network freely. Now, after a week or so, I can't even see the network, much less browse it. I haven't messed with any settings during this period. I'm using a Linksys Ether16 Lan card, and have tried using the NE2000 compat. drivers, and the vendor drivers packaged with Win2K. Internet connectivity is great, but I still can't see or be seen by the network. Any ideas?
 
Thanks,
Incubus

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This subject has been archived. New comments and votes cannot be submitted.
Mar 3
Created
Mar 5
Last Response
0
Likes
3 minutes
Read Time
User User User User User
Users

Responses to this topic


data/avatar/default/avatar18.webp

397 Posts
Location -
Joined 1999-08-31
I've got the same problem.
 
I believe its a Win2k network security issue, as although Net neighbourhood always says the network is not browsable, the modem sharing which is enabled in win2k works!

data/avatar/default/avatar14.webp

6 Posts
Location -
Joined 2000-03-03
If you want other versions of windows (like 98 or 95) to see you, you have to install the netbeui protocol on your win2k machine. Also, if you manually assigned IP-numbers and a subnet mask, it has to be in the same range on all of the computers (if your subnet mask is 255.255.255.0 the IP's may only differ in the last number.
 
If you haven't specified any IP's on any of the computers and you don't have a server or an ISDN Router, you've found youre problem. Then you definetely don't have the same IP's on your computers.
 
[This message has been edited by The Viper (edited 03 March 2000).]

data/avatar/default/avatar11.webp

8 Posts
Location -
Joined 2000-03-02
Go to the TCP/IP settings -> advanced -> DNS and disable "Register this connection's addresses in DNS". Then it should work.

data/avatar/default/avatar07.webp

49 Posts
Location -
Joined 2000-02-23
One thing you can try is create an LMHOST file. To do this go start>run> and type cmd. Then a command prompt will come up. Type "edit LMHOST", then you will be in a dos style editor. From here you need to type in the ip and corisponding computer name of each box on your network, here is the syntax "192.168.1.1 <computer name> #PRE" The #PRE will make it pre cache the ip's when you boot up. Also make sure that the first bound protocal is the same on all the boxes, i.e. if TCP/IP is first on your 2000 box make it the first on your 9.x boxes.

data/avatar/default/avatar38.webp

3 Posts
Location -
Joined 2000-03-03
OP
Thanks DennisJ, after unchecking the register with DNS box and rebooting, the network came up perfectly Now I think my setup is in full working order now and I can sleep peacefully without thoughts of networking invading my dreams
 
Thanks again for all the advice given here as noone would help me on the official newsgroups.
 
Incubus