If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#41
|
|||
|
|||
Windows 98 network not working
"Steve Winograd [MVP]" wrote: In article , "Fatso" wrote: Sorry Steve, maybe I shouldn't have cleaned up the post a bit, I'll try again with all the other bits This is as I put it before "I have file and printer sharing already enabled on both, I have been playing with the browse master settings as well. At the moment I can see machine 1 from machine 2 but can't access it either through network neighbourhood or through the run command. To give a little background to the problem, I have had them working before in a peer to peer network with ICS, whcih was okay if a little unstable at times, we changed plans with our ISP and my Father had troubles when that changed over so called their helpdesk (when I wasn't around) who managed to promptly detonate the network settings {aren't ISP helpdesks helpful }. After fighting with that for a day I figured I'd install a switch (8 port 10/100 skymaster) to make a more stable network and do away with the peer to peer ICS problems, but so far I have been fighting with the network for about a week with no luck. Thanks for the info on WINS, also thanks to everyone trying to help, I do appreciate it. " The DHCP comes from the d-link dsl 302-g modem/router. The strange part is that I keep seeming to get different symptoms using the same settings, for instance before I went to lunch: machine 1 had full access to machine 2, machine 2 could see machine one but could not access it (giving error that the network name couldn't be found). When I came back from lunch, neither computer could see/access the other so I rebooted both, now machine 1 can access & see machine 2 again but machine 2 has nothing in the network nighbourhood, not even itself or an entire network icon. (it can still ping them using run - ping 10.x.x.x), no-one touched the network or the settings, or even the computers in that time. The only thing that has changed is that I ate curried sausages for lunch but I fail to see why that took what little network I had down. The sausages obviously gave your network indigestion. :-) Thanks for the details of the network setup and the D-Link modem/router. Please run these tests, substituting the actual IP addresses and computer names, and report the results: 1. Ping each computer from the other using both IP address and computer name: ping 10.0.0.2 ping computerA ping 10.0.0.3 ping computerB 2. Access each computer's shared resources directly, without using My Network Places, by both IP address and computer name, by typing these commands in the Start | Run box: \\10.0.0.2 \\computerA \\10.0.0.3 \\computerB Ok, after a nights sleep I'm ready to fight with it again.... Pointing at machine 1 from machine 2 step 1. pinging the ip - ok pinging the name - ok Step 2. \\ip address - "The network name cannot be found" \\name - "The network name cannot be found" From machine 1 to machine 2 Step 1. All ok Step 2. All ok This is where the problem lies, the symptoms vary a bit, sometimes I can see the network on machine 2, I've even seen the other computer, but I haven't been able to access it. Thanks for doing those tests. Here's what they show: A. Both computers can ping each other by IP address and by computer name. The TCP/IP protocol and name resolution (using NetBIOS, not WINS) are working on both of them. B. Machine 1 can access machine 2's shared resources by IP address and computer name. "Client for Microsoft Networks" is working on machine 1, and "File and Printer Sharing" is working on machine 2. C. Machine 2 can't access machine 1's shared resources by IP address or by computer name. One or both of these could cause the problem: "Client for Microsoft Networks" isn't working on machine 2 "File and Printer Sharing" isn't working on machine 1. Possible solution: 1. Go to Control Panel | Network on machine 1. 2. If "File and Printer Sharing for Microsoft Networks" is installed, un-install it, reboot, and go back to Control Panel | Network. 3. Install "File and Printer Sharing for Microsoft Networks". 4. Reboot. 5. Share the desired disks and folders. 6. Try network access again. If that doesn't solve the problem: 1. Go to Control Panel | Network on machine 2. 2. If "Client for Microsoft Networks" is installed, un-install it, reboot, and go back to Control Panel | Network. 3. Install "Client for Microsoft Networks". 4. Reboot and try network access again. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm I have tried that now, to no avail, unfortunately, no change from before. for some reason I haven't been able to reply here before now to let you know. Chris |
#42
|
|||
|
|||
OMG I have finally sorted it out.
I thought I had uninstalled Zonealarm off machine 1 a while ago, now I find that it was still installed and even though it wasn't running, I had disabled it to stop it interferring, the darned thing was still blocking connections. I have uninstalled it and the network is now working Thanks to all the guys who tried to help -- Chris "Fatso" wrote: "Steve Winograd [MVP]" wrote: In article , "Fatso" wrote: Sorry Steve, maybe I shouldn't have cleaned up the post a bit, I'll try again with all the other bits This is as I put it before "I have file and printer sharing already enabled on both, I have been playing with the browse master settings as well. At the moment I can see machine 1 from machine 2 but can't access it either through network neighbourhood or through the run command. To give a little background to the problem, I have had them working before in a peer to peer network with ICS, whcih was okay if a little unstable at times, we changed plans with our ISP and my Father had troubles when that changed over so called their helpdesk (when I wasn't around) who managed to promptly detonate the network settings {aren't ISP helpdesks helpful }. After fighting with that for a day I figured I'd install a switch (8 port 10/100 skymaster) to make a more stable network and do away with the peer to peer ICS problems, but so far I have been fighting with the network for about a week with no luck. Thanks for the info on WINS, also thanks to everyone trying to help, I do appreciate it. " The DHCP comes from the d-link dsl 302-g modem/router. The strange part is that I keep seeming to get different symptoms using the same settings, for instance before I went to lunch: machine 1 had full access to machine 2, machine 2 could see machine one but could not access it (giving error that the network name couldn't be found). When I came back from lunch, neither computer could see/access the other so I rebooted both, now machine 1 can access & see machine 2 again but machine 2 has nothing in the network nighbourhood, not even itself or an entire network icon. (it can still ping them using run - ping 10.x.x.x), no-one touched the network or the settings, or even the computers in that time. The only thing that has changed is that I ate curried sausages for lunch but I fail to see why that took what little network I had down. The sausages obviously gave your network indigestion. :-) Thanks for the details of the network setup and the D-Link modem/router. Please run these tests, substituting the actual IP addresses and computer names, and report the results: 1. Ping each computer from the other using both IP address and computer name: ping 10.0.0.2 ping computerA ping 10.0.0.3 ping computerB 2. Access each computer's shared resources directly, without using My Network Places, by both IP address and computer name, by typing these commands in the Start | Run box: \\10.0.0.2 \\computerA \\10.0.0.3 \\computerB Ok, after a nights sleep I'm ready to fight with it again.... Pointing at machine 1 from machine 2 step 1. pinging the ip - ok pinging the name - ok Step 2. \\ip address - "The network name cannot be found" \\name - "The network name cannot be found" From machine 1 to machine 2 Step 1. All ok Step 2. All ok This is where the problem lies, the symptoms vary a bit, sometimes I can see the network on machine 2, I've even seen the other computer, but I haven't been able to access it. Thanks for doing those tests. Here's what they show: A. Both computers can ping each other by IP address and by computer name. The TCP/IP protocol and name resolution (using NetBIOS, not WINS) are working on both of them. B. Machine 1 can access machine 2's shared resources by IP address and computer name. "Client for Microsoft Networks" is working on machine 1, and "File and Printer Sharing" is working on machine 2. C. Machine 2 can't access machine 1's shared resources by IP address or by computer name. One or both of these could cause the problem: "Client for Microsoft Networks" isn't working on machine 2 "File and Printer Sharing" isn't working on machine 1. Possible solution: 1. Go to Control Panel | Network on machine 1. 2. If "File and Printer Sharing for Microsoft Networks" is installed, un-install it, reboot, and go back to Control Panel | Network. 3. Install "File and Printer Sharing for Microsoft Networks". 4. Reboot. 5. Share the desired disks and folders. 6. Try network access again. If that doesn't solve the problem: 1. Go to Control Panel | Network on machine 2. 2. If "Client for Microsoft Networks" is installed, un-install it, reboot, and go back to Control Panel | Network. 3. Install "Client for Microsoft Networks". 4. Reboot and try network access again. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm I have tried that now, to no avail, unfortunately, no change from before. for some reason I haven't been able to reply here before now to let you know. Chris |
#43
|
|||
|
|||
Windows 98 network not working
OMG I have finally sorted it out.
I thought I had uninstalled Zonealarm off machine 1 a while ago, now I find that it was still installed and even though it wasn't running, I had disabled it to stop it interferring, the darned thing was still blocking connections. I have uninstalled it and the network is now working Thanks to all the guys who tried to help -- Chris "Fatso" wrote: "Steve Winograd [MVP]" wrote: In article , "Fatso" wrote: Sorry Steve, maybe I shouldn't have cleaned up the post a bit, I'll try again with all the other bits This is as I put it before "I have file and printer sharing already enabled on both, I have been playing with the browse master settings as well. At the moment I can see machine 1 from machine 2 but can't access it either through network neighbourhood or through the run command. To give a little background to the problem, I have had them working before in a peer to peer network with ICS, whcih was okay if a little unstable at times, we changed plans with our ISP and my Father had troubles when that changed over so called their helpdesk (when I wasn't around) who managed to promptly detonate the network settings {aren't ISP helpdesks helpful }. After fighting with that for a day I figured I'd install a switch (8 port 10/100 skymaster) to make a more stable network and do away with the peer to peer ICS problems, but so far I have been fighting with the network for about a week with no luck. Thanks for the info on WINS, also thanks to everyone trying to help, I do appreciate it. " The DHCP comes from the d-link dsl 302-g modem/router. The strange part is that I keep seeming to get different symptoms using the same settings, for instance before I went to lunch: machine 1 had full access to machine 2, machine 2 could see machine one but could not access it (giving error that the network name couldn't be found). When I came back from lunch, neither computer could see/access the other so I rebooted both, now machine 1 can access & see machine 2 again but machine 2 has nothing in the network nighbourhood, not even itself or an entire network icon. (it can still ping them using run - ping 10.x.x.x), no-one touched the network or the settings, or even the computers in that time. The only thing that has changed is that I ate curried sausages for lunch but I fail to see why that took what little network I had down. The sausages obviously gave your network indigestion. :-) Thanks for the details of the network setup and the D-Link modem/router. Please run these tests, substituting the actual IP addresses and computer names, and report the results: 1. Ping each computer from the other using both IP address and computer name: ping 10.0.0.2 ping computerA ping 10.0.0.3 ping computerB 2. Access each computer's shared resources directly, without using My Network Places, by both IP address and computer name, by typing these commands in the Start | Run box: \\10.0.0.2 \\computerA \\10.0.0.3 \\computerB Ok, after a nights sleep I'm ready to fight with it again.... Pointing at machine 1 from machine 2 step 1. pinging the ip - ok pinging the name - ok Step 2. \\ip address - "The network name cannot be found" \\name - "The network name cannot be found" From machine 1 to machine 2 Step 1. All ok Step 2. All ok This is where the problem lies, the symptoms vary a bit, sometimes I can see the network on machine 2, I've even seen the other computer, but I haven't been able to access it. Thanks for doing those tests. Here's what they show: A. Both computers can ping each other by IP address and by computer name. The TCP/IP protocol and name resolution (using NetBIOS, not WINS) are working on both of them. B. Machine 1 can access machine 2's shared resources by IP address and computer name. "Client for Microsoft Networks" is working on machine 1, and "File and Printer Sharing" is working on machine 2. C. Machine 2 can't access machine 1's shared resources by IP address or by computer name. One or both of these could cause the problem: "Client for Microsoft Networks" isn't working on machine 2 "File and Printer Sharing" isn't working on machine 1. Possible solution: 1. Go to Control Panel | Network on machine 1. 2. If "File and Printer Sharing for Microsoft Networks" is installed, un-install it, reboot, and go back to Control Panel | Network. 3. Install "File and Printer Sharing for Microsoft Networks". 4. Reboot. 5. Share the desired disks and folders. 6. Try network access again. If that doesn't solve the problem: 1. Go to Control Panel | Network on machine 2. 2. If "Client for Microsoft Networks" is installed, un-install it, reboot, and go back to Control Panel | Network. 3. Install "Client for Microsoft Networks". 4. Reboot and try network access again. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm I have tried that now, to no avail, unfortunately, no change from before. for some reason I haven't been able to reply here before now to let you know. Chris |
#44
|
|||
|
|||
In article ,
"Fatso" wrote: OMG I have finally sorted it out. I thought I had uninstalled Zonealarm off machine 1 a while ago, now I find that it was still installed and even though it wasn't running, I had disabled it to stop it interferring, the darned thing was still blocking connections. I have uninstalled it and the network is now working Thanks to all the guys who tried to help You're welcome. Nice going to find the problem, and thanks for posting the solution. I'm sure that it will help other people. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
#45
|
|||
|
|||
Windows 98 network not working
In article ,
"Fatso" wrote: OMG I have finally sorted it out. I thought I had uninstalled Zonealarm off machine 1 a while ago, now I find that it was still installed and even though it wasn't running, I had disabled it to stop it interferring, the darned thing was still blocking connections. I have uninstalled it and the network is now working Thanks to all the guys who tried to help You're welcome. Nice going to find the problem, and thanks for posting the solution. I'm sure that it will help other people. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Shenan Stanley vies for longest Master Post title! | PA Bear | General | 5 | May 21st 05 05:27 PM |
Smart Portable Shortcuts | ForestSpirit | General | 5 | February 28th 05 03:50 AM |
Unwanted password to open Windows 98 | Jack Greenfield | General | 2 | July 20th 04 05:35 PM |
Microsoft Security Bulletin MS04-024 - Vulnerability in Windows Shell Could Allow Remote Code Execution (839645) | Gary S. Terhune | General | 2 | July 14th 04 05:06 AM |
Microsoft Security Bulletin MS04-024 - Vulnerability in Windows Shell Could Allow Remote Code Execution (839645) | Gary S. Terhune | General | 2 | July 14th 04 05:06 AM |