I have two computers connected through coax, and am attempting to share the modem in one machine with the other. I only have tcp/ip installed for both cards, which is what they communicate with. I have all the options set, ip's, DNS, gateway, all set up as WinGate described me to do. Now, I can get ping replies, play quake2 over the LAN, set up one machine as an ftp server and connect through the LAN, but the only thing I cannot do is share this **** modem I have wingate installed, server on one, client on the other, everything filled in exactly as the directions say. I then try to connect using IE5 to my wingate server (changes made for LAN connect in IE5 were made) and I see the connection made in gatekeeper on the server, but the machine cannot use the internet services, it just sits there and does nothing. Now I know the computers are seeing each other and are doing everything great together, but it just will not work with wingate and I was wondering if anyone had any tips. I tried every single tip on the wingate page. Thanks.
I have yet to try Wingate 3, but I had no such problems with earlier versions. If you can see IE make a connection in Gatekeeper, it should be working. What IP addys are you using for your LAN and DNS and what kind of error does IE return if you let it error out?
Im using 188.8.131.52 as my server, the dns ip's are from my isp, and what happens is the wingate dialer will come up on the client and connect, but no traffic will go through, it says bytes sent: 0 bytes recieved: 0 and just sits still as if you arent connected to the net.
Try this. For the server's network card:
Subnet Mask: 255.255.255.0
For the client, there are a couple options. Do you recall if Wingate turned on its DHCP service? You should see it as a service under gatekeeper if it is there. If it is, set the client machine to automatically get its IP address. Disable DNS, remove any gateways. If you don't have a DHCP service on your server, use these settings for the client:
DNS: enable, add 192.168.0.1
Now, go through any other configurations you made where the IP address may be different such as the wingate client install, or IE settings for proxy server. Change those to match 192.168.0.1 for the server. Just to eliminate the Wingate dialer as the problem, make sure your server is dialed up to your ISP. Then hop on the client and see if it is working. The numbers I give you above are virtually the same as what I've used for a long time with Wingate and worked fine. It could just be the IPs you are choosing that are causing the problem. It also could be a dialer problem and Wingate is just not dialing out when it should be. If you make sure you are connected and then try the client machine, you'll be able to tell if it is a problem with the dialer, or your other settings. Let me know how it goes.
This is just horrible. I've done what you said, still nothing. I've also had this problem of whenever I dial-up with my server, as soon as it logs onto the internet, the second it does, the machine will reboot, or will have about 10 blue screen errors, then crash completely. I'm trying to figure out what causes that, because I know its not a heat problem with the system, and I just reformatted so I don't understand what could cause that other than something in the network settings. Any ideas?
This may not be very helpful since you already have WinGate. The reviews I have read on Wingate say it is hard to set up. I recently down loaded a trial version of WinProxy Lite from Ositis Software and had it up and running in about 10 min. It is very easy to use.
From the sounds of things, I think the problem lies in the machine and not Wingate in this case. Also, I would recommend SyGate as the client configuration is almost nil. Its not quite as easy as Wingate to customize for advanced users, but it starts out more powerful out of the box.
I would have to agree w/800XL. Sygate is the way to go for a new user to networking.Easy install and it virtually sets itself up on the client pc. Down load the 6 page "SyGate 3.0 Quick-Start Guide", then the trial demo...I was up and running in less than 10 minutes.
That's weird, I stuck in Wingate on a whim and it worked correctly the first time. I'm a total newbie to networking too. Check the wingate website for their FAQ.
[This message has been edited by a Bill (edited 06-23-99).]
Try setting the client machine (the machine wingate is NOT installed on) to use the DNS server of your ISP.
I have IP masq set up through linux to share my connection, and unless I use my own DNS for it, the other machines on my LAN have to have my cable modem providor's DNS in their network settings. Works like a charm for me.
Thanks for all your help guys, I really appreciate it. I worked and worked and could NOT get there to be a proper connection between the two machines. I figure one of the two problems was this:
1) I had 95A on one machine, and 95B on the other, this could have done something
2) The client computers NIC wasnt working properly.
I installed Win98SE on both machines, after formatting since I was fed up hehe Then, I bought another NIC for the client machine, and tried again (using Winproxy, not wingate). It works like a charm now, so I figure one of the two numbers above was a reason why. Anyways, thanks again!
Just out of curiosity, why did you use WinProxy? Since you installed Win98SE you can use the shared internet connection built into this release. Since it is made by Microsoft it "should" work pretty well with the OS.
[This message has been edited by Shawn (edited 06-29-99).]
I had already bought a license for Winproxy so I didn't wanna waste it
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke