Re: Port forwarding

All of the above was true, but I have just managed to fix it. I had
inadvertantly removed the default gateway setting (poiting to the router)
for the w2k3 machine. Whoops!!

Thanks for all the help.


"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:uBswBIqUFHA.2468@xxxxxxxxxxxxxxxxxxxxxxx
> Let's look at this systematically. Here is what I assume:
>
> - The internal IP address of Server1 is 192.168.1.1.
> - The internal IP address of Server2 is 192.168.1.2.
> - The internal IP address of PC1 is 192.168.1.101.
> - Both servers run the Terminal Server service.
> - The RDP port number of Server1 is set to 3391.
> - The RDP port number of Server2 is set to 3392.
> - You type this command on a PC1
> telnet 192.168.1.1 3391
> You get a response.
> - You type this command on a PC1
> telnet 192.168.1.2 3392
> You get a response.
> - Your router is set so that it forwards packets for port 3391 to
> 192.168.1.1.
> - Your router is set so that it forwards packets for port 3392 to
> 192.168.1.2.
> - Your external IP address is aaa.bbb.ccc.ddd.
> - You type this command on an external PC:
> telnet aaa.bbb.ccc.ddd 3391
> You get no response.
> - You type this command on an external PC:
> telnet aaa.bbb.ccc.ddd 3392
> You get a response.
>
> If all of the above are true (after making the appropriate adjustments
> to the IP addresses) then you have a problem with your router.
> Here is what I would do:
> - Examine its log.
> - Put on a sniffer.
> - Try another router.
>
> "Joseph Byrns" <JosephByrns@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:%23ME5L1kUFHA.612@xxxxxxxxxxxxxxxxxxxxxxx
>> Thanks for the reply, but unfortunately still no luck, I tried the higher
>> port as suggested but it still didn't work, if I try a telnet to a port
>> pointing to a different server then it works fine (but there is
>> definately
>> no firewall set up on the w2k3 server). I also checked with the ISP to
> make
>> sure they weren't blocking any ports, they apparently only block port 25.
>> Everything still works from within the LAN.
>>
>> Any other ideas?
>>
>> "Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
>> news:u0RVhmkUFHA.3716@xxxxxxxxxxxxxxxxxxxxxxx
>> > Rather than testing port 80, I suggest you test a port
>> > with a higher number, e.g. 3389 (RDP). Many ISPs
>> > block ports below 1024.
>> >
>> > Use telnet.exe to test your ports. It is far easier and
>> > versatile to use then IIS6.
>> >
>> > Many ADSL routers have an inbuilt logger. Check its
>> > entries both for a successful and a failed test.
>> >
>> >
>> > "Joseph Byrns" <JosephByrns@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> > news:%237M2NdkUFHA.444@xxxxxxxxxxxxxxxxxxxxxxx
>> >> > - What port numbers are you talking about?
>> >> Port 80
>> >>
>> >> > - How do you test port forwarding?
>> >> Trying to access a web page provided by IIS6
>> >>
>> >> > - What happens when you perform the test from inside
>> >> > your network rather than through the router?
>> >> It works fine.
>> >>
>> >> > - If you disconnect the server from the network and
>> >> > connect it via a cross-over cable to a laptop, then
>> >> > access the server port under test from the laptop,
>> >> > what does your network adapter status panel show?
>> >> > Any incoming traffic?
>> >> I've not tried this, but I'd rather not disconnect the server until
> I've
>> >> exhausted all other avenues.
>> >>
>> >> Any ideas appreciated.
>> >>
>> >>
>> >
>> >
>>
>>
>
>


.

Relevant Pages

  • Re: No inbound email from external domains -- please help!
    ... Or as previously stated, it is the ISP actively blocking port 25, which I've seen them do if they thing abuse of terms is happening. ... I don't know how to verify router forwarding all 25 request to wan side. ... Your server is not responding to any telnet requests. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to Mailserver
    ... chance yet to dig into the server and find out why. ... When I telnet to port 25 I should get a response from your exchange ... Are the correct ports open in the router? ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to Mailserver
    ... domain's zone files on the dyndns server, ... I'm presuming it's a simple port forward from WAN to LAN on ... When I telnet to port 25 I should get a response from your ... Are the correct ports open in the router? ...
    (microsoft.public.windows.server.sbs)
  • Re: no incoming email
    ... Disconnect the router from the External NIC and hook a LAPtop up to the NIC ... If you are unfamiliar with sending an email with Telnet ... > external side ip 24.154.1.24, port 43760, was received on our public ip, ... > of my exchange server all the way through. ...
    (microsoft.public.windows.server.sbs)
  • Re: big problem with email
    ... a reason I know of that I might want to come in on port 23 to do what? ... I telnet in to routers, printers and switches on 23 but that is the ... external nic of the SBS is installed on. ... eliminates your router from the test. ...
    (microsoft.public.windows.server.sbs)