Dnet Client & Proxies.

[micron]

I have 2 computers, one has a modem one doesn't. Right now I am using the AnalogX Proxy to get internet access to my second machine. I installed the Dnet client on my second machine but can't figure out how to get it to access the internet . Please Help?

 

[Jator]

That proxy software aonly allows a few ports to go through. Find out what port it uses and I might be able to help. Also, try a port 80 pproxy such proxy80.teamanandtech.com

Jay

P.S. Remember to specify the port number.

 

[Kilowatt]

You didn't say, but are both machines running Winblow$?

There is a buffer sharing FAQ around here somewhere, to show you how to do it.

OR, as most people are doing (I'm guessing) is to use a pproxy on the machine with the internet connection, and have the second machine flush/fetch through that.

<edit - Damn dyslexic keyboard!

 

[micron]

This is what the read-me says:

HTTP (web browsers) (port 6588)
HTTPS (secure web browsers) (port 6588)
SOCKS4 (TCP proxying) (port 1080)
SOCKS4a (TCP proxying w/ DNS lookups) (port 1080)
SOCKS5 (only partial support, no UDP) (port 1080)
NNTP (usenet newsgroups) (port 119)
POP3 (receiving email) (port 110)
SMTP (sending email) (port 25)
FTP (file transfers) (port 21)

 

[micron]

And yes both are windows.

 

[Jator]

Is the one with the dial-up a Win98SE or Win2K machine? If so, you can use the ICS feature and it will make it a seemless connection for your proxy. If not, then try the port80.teamanandtech.com proxy. You might have to mess around with some of the connection types, but it can be done.

Jay

 

[Kilowatt]

Here's the FAQ on Network buffer sharing

 

[Viztech]

Hi Micron-

Another very good alternatve for you is to use 'remote buffers'

Basicaly computer #2 updates with computer #1 using netbios. it works quite well on small LANs.

This archived FAQ is a little dated, but it describes the process pretty well. I might stress that you should use remote buffers, not shared, so look closely at the examples #2 and #3.

Engineer and I have used remote buffers extensively, so we can help if you need further assistance.

Good luck!

viz

 

[Jator]

My only concern with Remote Buffers is if the main machine goes offline, then you eventually will run into randoms. Of course, any scenario you run, if you are disconnected for a long enough period, you run the risk of doing randoms, so i guess this would be as good a soloution as any.

Jay

 

[Viztech]

Any way you look at it, machine #2 is dependent on #1. If you keep a few days supply on #2, this is the best insurance against running out of work.

viz

 

[micron]

Thanks guys! Problem fixed, I decided to share buffers.

 

[Viztech]

Sharing buffers can be bad news.
I strongly suggest &quot;remote buffers&quot; so machine #2 can keep a reserve on hand, and reduce the chances of buffer locking.
Give it a try, I know you will be pleased.

viz

 

[micron]

viztech, what do you mean by &quot;buffer lock&quot;?

 

[Viztech]

Buffer locks will occur when both clients try to access the buffers at the same time.
With shared buffers, the #2 machine will try to access the buffer after every completed packet.
With remote buffers, you will have the choice to flush/fetch after a certain number of packets are completed. This reduces the chances of simultaneous access.
This is probably not too much of an issue with only 2 machines, but it does happen.

I'm just trying to point out a potential pitfall is all.

Best of luck, and keep em cracking!

viz