4 replies
by neutrons
First, I have to ask if you've given the client PC's the static IP addresses needed? Are the subnet masks the same, and is file sharing enabled? Have you configured Wingate correctly? Have you checked the log for CONSeal? That will tell you what network activity has occurred. The rulesets would probably have been generated in Manual Learning mode, either "Checked" or "Unchecked" mode. "Checked" is preferable, as it allows you to accept new rules or not, while "Unchecked" learns as you use it during a trial period and seems somewhat more risky. If all this is ok, then my next question is how are the PC's downline from the Wingate server hooked up? You must have either a hub in there somewhere, or multiple network cards. You shouldn't need the NetBeui protocol installed with TCP/IP and static IP's. Also, have you checked with the @HOME people to be certain that you are authorized to have multiple computers hooked in that can access the net besides the main computer? I know from experience that the @HOME people are a little touchy on this subject, as a friend of mine was requested to remove Windows 2000 Pro from one of his machines so the @HOME people could "see" that no other computers were hooked up downline from it. He eventually purchased 5 static IP's (for $5 per month each) from @HOME, and hooked up a 10baseT hub (8 port) with the "uplink" port hooked to the cable modem and the computers hooked into the 2-6 ports for less hassle than the Wingate option, which he tried for a while. Each computer has equal use of the modem through the hub, and are not constricted by 1 machine. Currently, he has few problems with the service, except occasional unexpected downtime from the @HOME servers, and slower speeds during the dayas you would expect.
neutrons@europa.com
by bean baggins
Yes, the static IP's are set to 192.168.0.X (the server being .1), on the same subnet (255.255.255.0), with file and printer sharing enabled, and Wingate is configured correctly. The default gateway on the client PCs is set to 192.168.0.1 (the IP of the Wingate server). TCP/IP is the default protocol.
Interestingly enough I originally set up the "server" with only TCP/IP; NetBEUI was not installed and the network was operating correctly for about three days. I added NetBEUI only after the problems started cropping up, hoping this would allow me to use "find computer" to view a client . I can ping the other IP's on the network, but I cannot see them in network neighborhood. As a result I cannot map any drives. I've done this set up on several other networks, and have had similar problems on one other setup.
These are licensed installs of Wingate and CONSeal. The "server" PC does indeed have two NICs, one for the ADSL connection which obtains an IP automatically from the ISP, and one for the LAN with a static IP. Please note this is ADSL not cable. Each NIC has a different ruleset but the "external" NIC is in checked learning mode. The network connection is as follows: ADSL Modem -> WAN NIC in server PC -> LAN NIC in server PC -> Hub <- other network clients. This is a conventional LAN in all respects.
I feel confident that the problem is with the "flaky" nature of browsing in Windows 95 networking. I have looked at other possibilities, ie. viruses, bad NIC or hub, damaged network cable, and have taken the appropriate troubleshooting steps to rule these out.
I thank you for your response.
by bean baggins
by bean baggins
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending