ADSL Sharing........
This is a discussion about ADSL Sharing........ in the Windows Networking category; I want to share my adsl connection with two other pcs in the network both using win98 1st edition and I myself using w2k. The pcs can see each other in the network but I can't get them to share the connection.
I want to share my adsl connection with two other pcs in the network both using win98 1st edition and I myself using w2k. The pcs can see each other in the network but I can't get them to share the connection. I'm using wingate to do so but no luck any idea??
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Apr 24
Apr 25
0
4 minutes
Responses to this topic
post your network configuration
I have tried lots of sharing programs before i could find one that works perfectly. I'm using sygate home network. YOu can get a trial version at www.sygate.com and get a keygenerator at www.astalavista.box.sk
The programs i tried on my ADSL (PPPoE):
Wingate: never worked, client wouldn't see the server computer
Winroute: worked for a few days, then lost the connection, i reinstalled it, it worked again for a few days, then lost the connection again, really weird
Avirt gateway suite: Worked perfect. But as it shares through a proxy server "ping" is impossible on the clients (same as with wingate).
Sygate: uses NAT to share the connection, has been working great for 2 months now, i love it.
you're using win2k on the server right? cuz i ran into a lot of probs with windows 98, Me, whatever version of 9X (windows wouldn't shutdown anymore, random crashes when 2 network cards were installed)
Since use win2k on the server everything works great. The clients can use whatever os you want.
The programs i tried on my ADSL (PPPoE):
Wingate: never worked, client wouldn't see the server computer
Winroute: worked for a few days, then lost the connection, i reinstalled it, it worked again for a few days, then lost the connection again, really weird
Avirt gateway suite: Worked perfect. But as it shares through a proxy server "ping" is impossible on the clients (same as with wingate).
Sygate: uses NAT to share the connection, has been working great for 2 months now, i love it.
you're using win2k on the server right? cuz i ran into a lot of probs with windows 98, Me, whatever version of 9X (windows wouldn't shutdown anymore, random crashes when 2 network cards were installed)
Since use win2k on the server everything works great. The clients can use whatever os you want.
OP
I've got the same problem here, wingate client just can't detect my wingate server and how should I configure Sygate?? I got it installed but the same problem still occur. Can't find the sygate server
OP
and yet all my configuration is set to automatic for the ip and dns. DHCP is enabled I think.
i don't like DHCP . I configured everything manually. but give me the hardware config of your network and i'll see if i can help you. I can't promise you anything cuz i'm only a rookie too in networking.
How are your computers connected which each other? How many computers do you have in the network? (3 if i'm not mistaken?). So you must be using a hub?
How are your computers connected which each other? How many computers do you have in the network? (3 if i'm not mistaken?). So you must be using a hub?
Sygate was the best I ever used, until I got my Linksys router and it kicks much ***.
You have a few options.
1) Lease 3 static ip's from your isp. They should give you one (unless your isp uses dynamic or your router is a dhcp server, in which case you wouldn't have this problem in the first place). This is the easiest solution. No additional hardware, if your home network is already up and running. You just configure the clients with the ip's and stick the router into the hub and then your off.
2)Use Win2k ICS. This is also easy and only requires one IP. 2 nics in the win2k machine, one nic your public IP. The other nic will automatically have 192.168.0.1. Have your clients either use DHCP or give them statics of 192.168.0.2 and .3.
IP. 192.168.0.2
Subnet Mask 255.255.255.0
Gateway 192.168.0.1 (Server)
3) Use a 3rd party NAT/Proxy like Winproxy or Winroute. I have used Winproxy and winroute at the office.
Winproxy- Easy to setup, but closes tons of ports. Bad for gaming
WinRoute- Awesome software, just a little difficult to setup. But once its running, it runs great.
The 3rd party solutions require one machine to be a server, and 2 nics are required in the server machine.
There are a lot of ways to set it up. If money isn't an issue I would go with #1. If money is #2 as its free.
All but #1 assume you have your home network configured and running.
1) Lease 3 static ip's from your isp. They should give you one (unless your isp uses dynamic or your router is a dhcp server, in which case you wouldn't have this problem in the first place). This is the easiest solution. No additional hardware, if your home network is already up and running. You just configure the clients with the ip's and stick the router into the hub and then your off.
2)Use Win2k ICS. This is also easy and only requires one IP. 2 nics in the win2k machine, one nic your public IP. The other nic will automatically have 192.168.0.1. Have your clients either use DHCP or give them statics of 192.168.0.2 and .3.
IP. 192.168.0.2
Subnet Mask 255.255.255.0
Gateway 192.168.0.1 (Server)
3) Use a 3rd party NAT/Proxy like Winproxy or Winroute. I have used Winproxy and winroute at the office.
Winproxy- Easy to setup, but closes tons of ports. Bad for gaming
WinRoute- Awesome software, just a little difficult to setup. But once its running, it runs great.
The 3rd party solutions require one machine to be a server, and 2 nics are required in the server machine.
There are a lot of ways to set it up. If money isn't an issue I would go with #1. If money is #2 as its free.
All but #1 assume you have your home network configured and running.
