dgilbert
Good Bye My Friend
Premium,MVM
join:2002-06-15
none
clubs:
| reply to fogice
Re: Pinhole setup - "may not be on LAN network" -
you have to forward the ports to the server, then in the proxy software forward them to your machine. sorry i can't be more specific, but i am not familiar with microsoft proxy. i do know that your BEST bet is to have the router forward ALL traffic to the proxy, or to setup the router for bridge and let the proxy server have the public ip on its wan side.
--
If you can read this, thank a teacher..........and since it's in English, thank a soldier. |
|
fogice
join:2004-06-07
New Haven, CT
| reply to dgilbert
Yes, the 3546 is only connected to the server, and a seperate cable goes from the server to the switch. I just researched ICS, and I don't think we are using that; this server was originally set up back when most of my office was on Win95 machines. Although those are gone, we still have some Win98 that aren't Second Edition, and ICS seems to require a minimum of Win98SE.
I believe that the internet sharing is being accomplished through Microsoft Proxy Server/Client 2.0. I don't want to accidentally blow all the other computers off of the internet. How should I deal with Microsoft Proxy?
(And thanks for holding my hand through all of this!) |
|
dgilbert
Good Bye My Friend
Premium,MVM
join:2002-06-15
none
clubs:
| reply to fogice
Re: Pinhole setup - "may not be on LAN network" - ?
do you have 1 cable from the 3546 going to the server, then a second cable from teh server to the switch, or are each directly connected to the 3546?
if both are directly connected, then your 3com IS a router, not a switch, and needs to be setup to be used as a switch. to do this, you would have to reprogram the 3com to turn off the DHCP server, set it's lan ip to something in the 192.168.1.254 range, and moce the cable from the 3546 to a LAN port on the 3com instead of the WAN port.
if it goes to the server first, then on to the switch, you have ICS enabled on the server and do not need it. i feel this is how you are setup currently. your 3546 IS a router, so there is no need for ICS.
--
If you can read this, thank a teacher..........and since it's in English, thank a soldier. |
|
fogice
join:2004-06-07
New Haven, CT
| reply to dgilbert
Re: Pinhole setup - "may not be on LAN network" -
You are correct, the Cayman is at its default of 192.168.1.254. The complete setup appears to be:
DSL phone line
Cayman Netopia 3546
Server (Windows NT 4, SP 6)
3Com Switch
my computer
I believe that my computer is accessing the internet through the WinSock service.
Is the 3Com switch considered the second router? Where would I access that setup?
(I'd ask my sysadmin, but that's me. I'm in a small company, and as the guy who knows computers the best, I got the additional task of running the network. It was all set up by outside professionals, so I'm pretty much guessing at what I need to do. Thanks for understanding and helping.) |
|
dgilbert
Good Bye My Friend
Premium,MVM
join:2002-06-15
none
clubs:
| reply to fogice
what is your internal ip of your cayman? it should be 192.168.1.254 unless you changed it. if it is, yet your pc is 192.168.0.54, then you must have another router between your machine and the cayman. if you do, then you MUST forward the proper ports from the cayman to the second router, and the second router to the pc. or better yet, remove the second router to cut out the double NAT problems.
--
If you can read this, thank a teacher..........and since it's in English, thank a soldier. |
|
fogice
join:2004-06-07
New Haven, CT
| Pinhole setup - "may not be on LAN network" - ?
I am attempting to set up a pinhole for Bittorrent (Azureus) on a Cayman 3546. I believe that I have set all the settings properly, based on what I have read on this site and others.
However, when I complete my setup of the pinhole, it requests that I check the Alert button, which informs me that my internal IP address "may not be on LAN network". Sure enough, after I reboot the Cayman and return to my networked machine, I still get a NAT problem in Azureus.
I have entered my internal IP address as 192.168.0.54 , which I have verified as correct. Anyone know what might be going wrong here? |
|
