cpu_trouble
asked on
Networking trouble... PWs and speed...
Hi,
I am currently running one computer on Win2k and the other one on win ME. I am using the Linksys 4port DSL/Cable router. I have good cables because they are new.
When I am going to go browse through my network, It takes really long to load up and it locks up the window and stays at the hourglass pointer for a long time. I had to install NetBEUI in order to get my computer to actually be able to see the other computer on the network. The computer names are unique and they are on the same workgroup.
Also, when the computer from Win ME is trying to access my computer over the network, it asks it for a password. I have never specified a password for network and I have tried the password that I specified for windows and it still wont work, I tried a blank PW and it wouldnt work either.
I will be adding more points as I get them.
thanx for the help
I am currently running one computer on Win2k and the other one on win ME. I am using the Linksys 4port DSL/Cable router. I have good cables because they are new.
When I am going to go browse through my network, It takes really long to load up and it locks up the window and stays at the hourglass pointer for a long time. I had to install NetBEUI in order to get my computer to actually be able to see the other computer on the network. The computer names are unique and they are on the same workgroup.
Also, when the computer from Win ME is trying to access my computer over the network, it asks it for a password. I have never specified a password for network and I have tried the password that I specified for windows and it still wont work, I tried a blank PW and it wouldnt work either.
I will be adding more points as I get them.
thanx for the help
ASKER
So you are saying that I have to log in everytime on the windows ME computer with that user name and password that I created?. If so, is there a way to have it log in automatically using the PW?
All the settings on both the windows 2k and the windows ME computer are set to automatic. (auto IP)
The router uses DHCP so I dont know if I can assign my computers an IP address and have the internet still work. can I?
All the settings on both the windows 2k and the windows ME computer are set to automatic. (auto IP)
The router uses DHCP so I dont know if I can assign my computers an IP address and have the internet still work. can I?
-No you're better off with the dhcp...
-Can you browse the net with both pc's ?
-For the login thing you can either make the password blank & simply press enter on the windows login box (not too much to deal with).. Or try changing the network properties to windows login instead of "client for microsoft networks". As long as the user who is logged in actually matches credentials that exist on the win2k machine it will not give you this IPC$ message & open the shares...
-Can you browse the net with both pc's ?
-For the login thing you can either make the password blank & simply press enter on the windows login box (not too much to deal with).. Or try changing the network properties to windows login instead of "client for microsoft networks". As long as the user who is logged in actually matches credentials that exist on the win2k machine it will not give you this IPC$ message & open the shares...
-No you're better off with the dhcp...
-Can you browse the net with both pc's ?
-For the login thing you can either make the password blank & simply press enter on the windows login box (not too much to deal with).. Or try changing the network properties to windows login instead of "client for microsoft networks". As long as the user who is logged in actually matches credentials that exist on the win2k machine it will not give you this IPC$ message & open the shares...
-Can you browse the net with both pc's ?
-For the login thing you can either make the password blank & simply press enter on the windows login box (not too much to deal with).. Or try changing the network properties to windows login instead of "client for microsoft networks". As long as the user who is logged in actually matches credentials that exist on the win2k machine it will not give you this IPC$ message & open the shares...
ASKER
Ok, one problem down...one more to go
I can now login from the ME machine without being asked for a PW and vise-versa.
But..
I still have the problem that the Win2k computer is taking an extremely long time to open the computers near me folder thing, when I open the other computer it takes a little less, but it still is very slow, then once inside one of the folders on the other computer, it is instant.
On the ME computer it is all instantaneous.
I can now login from the ME machine without being asked for a PW and vise-versa.
But..
I still have the problem that the Win2k computer is taking an extremely long time to open the computers near me folder thing, when I open the other computer it takes a little less, but it still is very slow, then once inside one of the folders on the other computer, it is instant.
On the ME computer it is all instantaneous.
-Its slow because of the node types & no resolution helpers because there is no server... If you type winipcfg on the Me computer & look at the details you'll probably see the NODE=Broadcast & the same for the win2k machine..
-Try this to see if it helps..
-Create shortcuts to the shares on each others desktop.. Not acceptable ?
-Create an lmhosts & or hosts file on each computer. How ?
-Say on the Me computer, you type winipcfg & the computer name is WINME1 with IP 192.168.0.3 .. 2000 is called WIN2KP & ipconfig shows 192.168.0.2
-On the winme computer drop to dos. CD to the windows folder. "cd\windows" .. Type edit lmhosts (enter)
type this in ..
win2kp (tab)192.168.0.2(tab)#PRE
-Save it..exit edit.
Type "nbtstat -R" Then "nbtstat -c"
-You should see the win2kp machine name preloaded for resolution..
-See if accessing the win2k machine is any faster..
-If it seemed to help...Do the same thing with correct info of course on the win2k machine.. On the win2k machine, you'd have to save the lmhosts. file in "c:\winnt\system32\drivers
-Try this to see if it helps..
-Create shortcuts to the shares on each others desktop.. Not acceptable ?
-Create an lmhosts & or hosts file on each computer. How ?
-Say on the Me computer, you type winipcfg & the computer name is WINME1 with IP 192.168.0.3 .. 2000 is called WIN2KP & ipconfig shows 192.168.0.2
-On the winme computer drop to dos. CD to the windows folder. "cd\windows" .. Type edit lmhosts (enter)
type this in ..
win2kp (tab)192.168.0.2(tab)#PRE
-Save it..exit edit.
Type "nbtstat -R" Then "nbtstat -c"
-You should see the win2kp machine name preloaded for resolution..
-See if accessing the win2k machine is any faster..
-If it seemed to help...Do the same thing with correct info of course on the win2k machine.. On the win2k machine, you'd have to save the lmhosts. file in "c:\winnt\system32\drivers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanx very much for the help, It is all working perfectly now.
Thanx again
Thanx again
-On the Win2k computer right click on my computer & choose manage.. Go to local users & groups & create a user that the Me computer will use. Lets say Username=cpu password=trouble.
-On the Me computer login as Username=cpu password=trouble.
-If the option does not come up, go to start & choose the option logoff.. This will allow you to enter the username & password.
-The Netbeiu thing... I assume from your comments that you were trying with tcp/ip & have to revert to netbeui because of the "jamming up etc" ?
-This is probably due to using IP's & subnet masks that do not match... Example... If the win2k machines IP is 192.168.1.2 with a subnet mask of 255.255.255.0, then an acceptable IP address for the Me computer would be 192.168.1.3 with a mask of 255.255.255.0
-Now you did mention that the Linksys is a DSL router.. So an acceptable IP address for it would be say 192.168.1.1 255.255.255.0 for the private or inside network card.. The dsl part uses dhcp I would imagine.