Re: Open Ports
From: Perquiaga (perquiaga_at_itcsa.net)
Date: 02/10/04
- Next message: I dont get this!: "Connection Problems"
- Previous message: Max André Bündchen: "Re: DSClient for Win98 do not work with Win2003 DC"
- In reply to: Perquiaga: "Re: Open Ports"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Feb 2004 07:16:12 -0300
I did it, now it's working...
try this sofware, is free...
it does the por forwarding thath Microsoft Servers is supposed to do...
http://www.skylarktechnology.com
"Perquiaga" <perquiaga@itcsa.net> wrote in message
news:#T8L6HO7DHA.1040@TK2MSFTNGP10.phx.gbl...
> I'm using portqry, the one included in the support tools.
> And i can't make it work yet.
>
> "Mickey" <anonymous@discussions.microsoft.com> wrote in message
> news:c0cd01c3ece1$8c659490$a501280a@phx.gbl...
> > I guess what Sharad was saying was that your Internet
> > client trying to connect to the application hosted behind
> > the NAT will make a request to open these ports on your
> > NAT server. If they are mapped correctly they should open
> > upon request.
> >
> > I mapped my ports correctly on the NAT. But sill couldn't
> > get my VPN client to go through the NAT.
> > Perquiaga, what portqry tool are you using to see if the
> > port is listening? I am troubleshooting my ports but could
> > find a good tool to test these ports. Please advise.
> >
> > Thank You.
> > >-----Original Message-----
> > >HI!
> > >I've set up the port/service in NAT settings to forward
> > an incoming request
> > >in an special port used by an application witch i need to
> > be accessed from
> > >the internet, being installed on an internal workstation.
> > >Everything is done, but it dows not open the port on the
> > server. The
> > >settings in NAT indicates everything is OK. Incoming and
> > uotgoing port are
> > >the same, the protocol is the same the application uses
> > UDP, and the private
> > >ip the workstation has.
> > >Please, how do i open the port ?
> > >The portqry keeps saying NOT LISTENENING and I'm getting
> > mad.
> > >How do i get it to start listening ?
> > >Sharad told that a service must request the por to open ?
> > >but if the software is in an internal workstation, how do
> > i run a service on
> > >the W2K3 server to open the port ? can you explain me a
> > little ? i can't get
> > >it...
> > >thanks
> > >
> > >"sharad" <sharad@anonymous.com> wrote in message
> > >news:ubrDNFx6DHA.1368@TK2MSFTNGP10.phx.gbl...
> > >> Do you have a mail server on your server?
> > >> If not then get the free version from www.argosoft.com
> > and install it.
> > >> Change the SMTP port of the mail server, from default
> > 25, to 500, then
> > >from
> > >> internet telent to your server by its ip address
> > followed by space
> > >followed
> > >> by 500
> > >> (e.g. telnet 64.91.10.101 500)
> > >> If it gets connected and says Welcome to xyz mail server
> > >> then port 500 is correctly enabled and can be opened
> > >> when requested.
> > >> Repeat above by changing the SMTP port of the mail
> > server to other ports
> > >you
> > >> want to check.
> > >>
> > >> Sharad
> > >> "Mickey" <anonymous@discussions.microsoft.com> wrote in
> > message
> > >> news:91f701c3ea29$89d14d60$a501280a@phx.gbl...
> > >> > Thank you, Sharad, for your quick response. I very
> > much
> > >> > appreciate that. Now I understand...
> > >> >
> > >> > Is there a utility to test requesting to open a port
> > >> > through the internet? The reason I am asking is that
> > I am
> > >> > trying to connect to my company's VPN server using
> > AT&T 's
> > >> > VPN network client from home's NATed environment. I
> > keep
> > >> > getting a IPSEC error...
> > >> >
> > >> > AT&T requested certain open ports. My problem is that
> > any
> > >> > client behind the NAT server are not able to connect
> > to a
> > >> > VPN server across the internet. If I bypass the NAT,
> > it is
> > >> > working fine. I got an 'IPSEC communication error...'
> > >> > AT&T stated that they are using l2tp and that I need
> > to
> > >> > open those ports: UDP 500, TCP 50, 5080, 379... on
> > the NAT
> > >> > Server/Router. Since I am using broadband connection,
> > >> > IPSEC drivers are needed and loaded by the AT&T client
> > >> > software at the client workstation to initiate the
> > >> > tunneling. But for some reason, the tuneneling can't
> > be
> > >> > established through the NAT. Any suggestions?
> > >> >
> > >> > Thanks again for your assistance.
> > >> >
> > >> > >-----Original Message-----
> > >> > >What you did is, gave access to the port from
> > internet.
> > >> > >You are asked open ports for connecting through
> > internet,
> > >> > which most
> > >> > >propably means, "Do not
> > >> > >block them, give access to them."
> > >> > >
> > >> > >It is not required to keep the port actually open.
> > >> > >
> > >> > >So you have given access now, through NAT. Now
> > >> > >a process should make a request to open the port,
> > then
> > >> > >it will communicate, after it is done the port will
> > be
> > >> > closed again.
> > >> > >Sharad
> > >> > >
> > >> > >"Mickey" <anonymous@discussions.microsoft.com> wrote
> > in
> > >> > message
> > >> > >news:8eed01c3ea1e$c3ddb030$a001280a@phx.gbl...
> > >> > >> Thank you, guys, for the input. I tried Service and
> > >> > Ports
> > >> > >> setup in IP Routing. I used the same ports for both
> > >> > >> incoming and outgoing (such as 1731) and put in the
> > >> > >> internal private IP. But when I do a port scan
> > from a
> > >> > web
> > >> > >> port scan tool site, it still shows that the port
> > is not
> > >> > >> open. Did I do something wrong? When I scan other
> > port
> > >> > >> like 1720, it shows that the port is open. Please
> > help!
> > >> > >> Thanks!
> > >> > >>
> > >> > >> >-----Original Message-----
> > >> > >> >Start - Administrative Tools->Routing and Remote
> > >> > Access.
> > >> > >> >
> > >> > >> >When it opens, expand "IP Routing" and under it
> > >> > >> >find NAT/Firewall and click on it. On the right
> > side
> > >> > then
> > >> > >> >you will find the adapters listed. Right click on
> > the
> > >> > >> adapter which is used
> > >> > >> >for internect connection, and
> > >> > >> >select properties.
> > >> > >> >When the property window opens click on Service
> > and
> > >> > >> Ports Tab.
> > >> > >> >There is already a list of standard ports which
> > are
> > >> > most
> > >> > >> >commonly used, and these can be opened by
> > checking the
> > >> > >> coresspoinding check
> > >> > >> >box. If the required port is not in the common
> > list,
> > >> > you
> > >> > >> can click on "Add"
> > >> > >> >give a description you like, and enter the
> > required
> > >> > >> incoming and outgoing
> > >> > >> >port.
> > >> > >> >Sharad
> > >> > >> >"Mickey" <anonymous@discussions.microsoft.com>
> > wrote in
> > >> > >> message
> > >> > >> >news:6dff01c3e6ad$c3bb7980$a501280a@phx.gbl...
> > >> > >> >> I am using Windows Server 2003 NAT and am
> > requested
> > >> > to
> > >> > >> >> open certain ports for a software to connect
> > over the
> > >> > >> >> Internet. I wonder if someone could tell me how
> > to
> > >> > open
> > >> > >> >> and/or close certain ports in Windows Server
> > 2003 and
> > >> > >> how
> > >> > >> >> to configure port forwarding in NAT. Also, is
> > there a
> > >> > >> tool
> > >> > >> >> to list all open or closed ports?
> > >> > >> >>
> > >> > >> >> Thank you very much in advance!
> > >> > >> >
> > >> > >> >
> > >> > >> >.
> > >> > >> >
> > >> > >
> > >> > >
> > >> > >.
> > >> > >
> > >>
> > >>
> > >
> > >
> > >.
> > >
>
>
- Next message: I dont get this!: "Connection Problems"
- Previous message: Max André Bündchen: "Re: DSClient for Win98 do not work with Win2003 DC"
- In reply to: Perquiaga: "Re: Open Ports"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
