Re: Routing problem - PCAnywhere, Server2003 & DNS
From: Herb Martin (news_at_LearnQuick.com)
Date: 01/09/05
- Next message: clyclopedic: "Re: performance pessimization"
- Previous message: Kevin D. Goodknecht Sr. [MVP]: "Re: Cannot create STUB zone"
- In reply to: Sam Mapson: "Re: Routing problem - PCAnywhere, Server2003 & DNS"
- Next in thread: Sam Mapson: "Re: Routing problem - PCAnywhere, Server2003 & DNS"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 9 Jan 2005 17:02:00 -0600
"Sam Mapson" <mapson4@hotmail.com> wrote in message
news:hThEd.2714$Ii4.177@newsread3.news.pas.earthlink.net...
> OK, I will try to give more info.
>
> The firewall has NAT enabled. There are multiple PCAnywhere users. The
> remote PCAnywhere computers are set to connect to the external ip
> address of the firewall with the assigned port numbers (udp, tcp).
> Only
> username and password settings are used in PCAnywhere. Rules have been
> created on the firewall to forward PCAnywhere requests (according to the
> assigned port number) to static IP addresses on the LAN (on a
> 192.168.1.xxx network).
> Before, on the XP computers, a static ip was set and dns was set to the
> dns ip address given to up by our isp.
That would be on the NAT machine, right?
Stick with one terminology -- I don't know whether
the "XP computers" are the pcAnywhere clients or
servers.
> Under NT server, PCAnywhere worked fine.
Can you use it RIGHT there, avoiding all the issues
of routing, NAT, firewall etc.
If you can use it there then it is not an OS or pcAnywhere
problem but a Routing/NAT/Mapping problem.
> Now under Server 2003 - on computers running XP, I had to change their
> DNS setting to the 2003 server's ip address (our local DNS server)
Of course (i.e., GOOD) you must do it that way.
You forward (usually) from the Internal DNS server to
that address given you for DNS by your ISP.
> Users trying to access their XP computers using PCAnywhere can no longer
> do so. They can not connect and PCAnywhere remote times out.
So it never even puts up the screen as if it is trying?
Can pcAnywhere (these days) show the Logon screen
-- instead of building in the password etc? IF so
you can see whether it connects at all which would
then be an AUTHENTICATION problem.
> Symantec mentioned to diagnose the problem, try to telnet to the host -
> telnet router_ip port_number - if it connects then you should get
> "press enter to continue".
Good method. I was going to suggest that.
We want to SIMPLIFY and get rid of as many
black boxes as possible -- we cannot use Ping
or usually techniques because that won't test the
correct protocol, ports, mappings etc.
> I can not telnet to the xp computer that
> have dns set to the 2003 server.
What about if you use the IP instead (this eliminates
or convicts DNS):
telnet router_ip port_number
If this above fails it is NOT a DNS problem because
you have no DNS involved.
> I can telnet to other PCAnywhere
> win2000 computers that have their dns set to our isp dns servers.
>
> Sorry I did not cross post instead of posting separate message in
> differnt groups.
Don't be sorry or worry about that -- I gave you the
advice so you can get better results next time and so
you would look in the other (this) newsgroup for the
answers.
- Next message: clyclopedic: "Re: performance pessimization"
- Previous message: Kevin D. Goodknecht Sr. [MVP]: "Re: Cannot create STUB zone"
- In reply to: Sam Mapson: "Re: Routing problem - PCAnywhere, Server2003 & DNS"
- Next in thread: Sam Mapson: "Re: Routing problem - PCAnywhere, Server2003 & DNS"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
