My network completely collapsed for no good reason after taking the client machine apart and putting it back together exactly the same way. It worked perfectly before that.
In trying to set it back up, nothing worked, and I found it easier to uninstall ALL protocols and services, (apart from TCP/IP), and network adapters from both machines, and re-installing them to give myself a clean slate to work from.
OK, with that done, the folowing protocols are installed...
Client for MS networks
QOS packet scheduler
File and printer sharing for MS networks
Internet Protocol (TCP/IP)
NetBios
IPX/SPX/Netbios compatible transport protocol.
The last two are installed purely to support a game or two that seems to prefer networking with them but otherwise aren't there for anything.
Windows firewall was then turned OFF on both machines, and the remaining firewall on "Server" (Sygate personal pro) was set to allow all, rendering it harmless.
OK, First the network setup wizard was run on the internet machine ("Server"). It was then run on the client machine ("client")
Both machines can ping each other on the network with no problems. A portscan of client helped me find out I could telnet succesfully to port 17 (qotd) of client, which I did because I was bored. No problems there then!
The network MSHOME, on both machines, shows that both "Client" - and "Server" - are connected
"Client" has an internet connection using "server" as the gateway, and can access both it's own shares, and "server"'s shares.
"server" can access it's own shares, but CAN'T access the shares on "client"
the attached file contains the IPCONFIG/ALL readouts of both machines. It also contains a network connection on "server" that I set up as an experiment, but now reappears each time the computer is booted, nomatter how many times I delete it.
Any help to resolve this issue would be greatly appreciated.
In trying to set it back up, nothing worked, and I found it easier to uninstall ALL protocols and services, (apart from TCP/IP), and network adapters from both machines, and re-installing them to give myself a clean slate to work from.
OK, with that done, the folowing protocols are installed...
Client for MS networks
QOS packet scheduler
File and printer sharing for MS networks
Internet Protocol (TCP/IP)
NetBios
IPX/SPX/Netbios compatible transport protocol.
The last two are installed purely to support a game or two that seems to prefer networking with them but otherwise aren't there for anything.
Windows firewall was then turned OFF on both machines, and the remaining firewall on "Server" (Sygate personal pro) was set to allow all, rendering it harmless.
OK, First the network setup wizard was run on the internet machine ("Server"). It was then run on the client machine ("client")
Both machines can ping each other on the network with no problems. A portscan of client helped me find out I could telnet succesfully to port 17 (qotd) of client, which I did because I was bored. No problems there then!
The network MSHOME, on both machines, shows that both "Client" - and "Server" - are connected
"Client" has an internet connection using "server" as the gateway, and can access both it's own shares, and "server"'s shares.
"server" can access it's own shares, but CAN'T access the shares on "client"
the attached file contains the IPCONFIG/ALL readouts of both machines. It also contains a network connection on "server" that I set up as an experiment, but now reappears each time the computer is booted, nomatter how many times I delete it.
Any help to resolve this issue would be greatly appreciated.