| Author |
Message |
Sam Mapson
Guest
|
 Posted:
Sun Jan 09, 2005 11:27 am Post subject:
Routing problem - PCAnywhere, Server2003 & DNS |
|
|
Just upgraded from NT server to Server 2003. We have several remote users
accessing their office computers using PCAnywhere. We have a Sonicwall
Firewall and it forwards the appropriate remote to the host via port
forwarding. We are using the Sonicwalls DHCP server and it is the main
gateway. It worked well under NT Server.
Inorder to resolve slow login and directory browsing, I changed the DNS
settings on all of our XP computers to point to the 2003 server. Now
PCAnywhere does not work. Any ideas on how to make PCAnywhere work? |
|
| Back to top |
|
 |
Herb Martin
Guest
|
| Posted:
Sun Jan 09, 2005 6:10 pm Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
"Sam Mapson" <mapson4@hotmail.com> wrote in message
news:Rg3Ed.2074$Ii4.561@newsread3.news.pas.earthlink.net...
| Quote: | Just upgraded from NT server to Server 2003. We have several remote users
accessing their office computers using PCAnywhere. We have a Sonicwall
Firewall and it forwards the appropriate remote to the host via port
forwarding. We are using the Sonicwalls DHCP server and it is the main
gateway. It worked well under NT Server.
Inorder to resolve slow login and directory browsing, I changed the DNS
settings on all of our XP computers to point to the 2003 server. Now
PCAnywhere does not work. Any ideas on how to make PCAnywhere work?
|
That's not (nearly) enough information unless someone
just happens to have had your problem or hit on it with
a luck guess.
Generally: you have an Authnetication and/or a Name
resolution problem if this is all that changes unless
pcAnywhere has collapsed completely (it did on Win2000
upgrades in a previous version but that was obvious
because the servers wouldn't even boot.)
You changed DNS, and Win2003 domains depend on
DNS for not just name resolution but that also is a
prerequisite for authentication.
Did you (at the same time) change anything about NetBIOS
or WINS server? (Many people think they don't need NetBIOS
in Win2000+ but that is almost always wrong, and even
WINS server remains important if you have IP on more than
one subnet and Win2000+ domains require IP).
Also you say "does not work" rather than giving us
specific symptoms, and error messages, and telling
us what standard (simple) tests like ping, nslookup,
etc. if they apply.
Does the pcAnywhere work at all? Locally or from
SOME clients?
Does it seem to connect initially? And then give
an authentication failure or does it not even find
the server?
etc.
--
Herb Martin |
|
| Back to top |
|
|
Sam Mapson
Guest
|
| Posted:
Mon Jan 10, 2005 4:03 am Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
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.
Under NT server, PCAnywhere worked fine.
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)
Users trying to access their XP computers using PCAnywhere can no longer
do so. They can not connect and PCAnywhere remote times out.
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". I can not telnet to the xp computer that
have dns set to the 2003 server. 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.
Sam
"Herb Martin" <news@LearnQuick.com> wrote in
news:uIikOSk9EHA.2568@TK2MSFTNGP10.phx.gbl:
| Quote: | "Sam Mapson" <mapson4@hotmail.com> wrote in message
news:Rg3Ed.2074$Ii4.561@newsread3.news.pas.earthlink.net...
Just upgraded from NT server to Server 2003. We have several remote
users accessing their office computers using PCAnywhere. We have a
Sonicwall Firewall and it forwards the appropriate remote to the host
via port forwarding. We are using the Sonicwalls DHCP server and it
is the main gateway. It worked well under NT Server.
Inorder to resolve slow login and directory browsing, I changed the
DNS settings on all of our XP computers to point to the 2003 server.
Now PCAnywhere does not work. Any ideas on how to make PCAnywhere
work?
That's not (nearly) enough information unless someone
just happens to have had your problem or hit on it with
a luck guess.
Generally: you have an Authnetication and/or a Name
resolution problem if this is all that changes unless
pcAnywhere has collapsed completely (it did on Win2000
upgrades in a previous version but that was obvious
because the servers wouldn't even boot.)
You changed DNS, and Win2003 domains depend on
DNS for not just name resolution but that also is a
prerequisite for authentication.
Did you (at the same time) change anything about NetBIOS
or WINS server? (Many people think they don't need NetBIOS
in Win2000+ but that is almost always wrong, and even
WINS server remains important if you have IP on more than
one subnet and Win2000+ domains require IP).
Also you say "does not work" rather than giving us
specific symptoms, and error messages, and telling
us what standard (simple) tests like ping, nslookup,
etc. if they apply.
Does the pcAnywhere work at all? Locally or from
SOME clients?
Does it seem to connect initially? And then give
an authentication failure or does it not even find
the server?
etc.
|
|
|
| Back to top |
|
|
Sam Mapson
Guest
|
| Posted:
Mon Jan 10, 2005 4:16 am Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
Did not have a WINS server. I will try enabling Netbios over IP when I
get into the office.
"Herb Martin" <news@LearnQuick.com> wrote in
news:uIikOSk9EHA.2568@TK2MSFTNGP10.phx.gbl:
| Quote: | "Sam Mapson" <mapson4@hotmail.com> wrote in message
news:Rg3Ed.2074$Ii4.561@newsread3.news.pas.earthlink.net...
Just upgraded from NT server to Server 2003. We have several remote
users accessing their office computers using PCAnywhere. We have a
Sonicwall Firewall and it forwards the appropriate remote to the host
via port forwarding. We are using the Sonicwalls DHCP server and it
is the main gateway. It worked well under NT Server.
Inorder to resolve slow login and directory browsing, I changed the
DNS settings on all of our XP computers to point to the 2003 server.
Now PCAnywhere does not work. Any ideas on how to make PCAnywhere
work?
That's not (nearly) enough information unless someone
just happens to have had your problem or hit on it with
a luck guess.
Generally: you have an Authnetication and/or a Name
resolution problem if this is all that changes unless
pcAnywhere has collapsed completely (it did on Win2000
upgrades in a previous version but that was obvious
because the servers wouldn't even boot.)
You changed DNS, and Win2003 domains depend on
DNS for not just name resolution but that also is a
prerequisite for authentication.
Did you (at the same time) change anything about NetBIOS
or WINS server? (Many people think they don't need NetBIOS
in Win2000+ but that is almost always wrong, and even
WINS server remains important if you have IP on more than
one subnet and Win2000+ domains require IP).
Also you say "does not work" rather than giving us
specific symptoms, and error messages, and telling
us what standard (simple) tests like ping, nslookup,
etc. if they apply.
Does the pcAnywhere work at all? Locally or from
SOME clients?
Does it seem to connect initially? And then give
an authentication failure or does it not even find
the server?
etc.
|
|
|
| Back to top |
|
|
Sam Mapson
Guest
|
| Posted:
Mon Jan 10, 2005 4:27 am Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
Are there any settings in DNS would help solve the problem. It was
setup for only a forward lookup zone. It forwards to the DNS IP
addresses the ISP gave us. I am not too knowledgeable about DNS.
"Herb Martin" <news@LearnQuick.com> wrote in
news:uIikOSk9EHA.2568@TK2MSFTNGP10.phx.gbl:
| Quote: | "Sam Mapson" <mapson4@hotmail.com> wrote in message
news:Rg3Ed.2074$Ii4.561@newsread3.news.pas.earthlink.net...
Just upgraded from NT server to Server 2003. We have several remote
users accessing their office computers using PCAnywhere. We have a
Sonicwall Firewall and it forwards the appropriate remote to the host
via port forwarding. We are using the Sonicwalls DHCP server and it
is the main gateway. It worked well under NT Server.
Inorder to resolve slow login and directory browsing, I changed the
DNS settings on all of our XP computers to point to the 2003 server.
Now PCAnywhere does not work. Any ideas on how to make PCAnywhere
work?
That's not (nearly) enough information unless someone
just happens to have had your problem or hit on it with
a luck guess.
Generally: you have an Authnetication and/or a Name
resolution problem if this is all that changes unless
pcAnywhere has collapsed completely (it did on Win2000
upgrades in a previous version but that was obvious
because the servers wouldn't even boot.)
You changed DNS, and Win2003 domains depend on
DNS for not just name resolution but that also is a
prerequisite for authentication.
Did you (at the same time) change anything about NetBIOS
or WINS server? (Many people think they don't need NetBIOS
in Win2000+ but that is almost always wrong, and even
WINS server remains important if you have IP on more than
one subnet and Win2000+ domains require IP).
Also you say "does not work" rather than giving us
specific symptoms, and error messages, and telling
us what standard (simple) tests like ping, nslookup,
etc. if they apply.
Does the pcAnywhere work at all? Locally or from
SOME clients?
Does it seem to connect initially? And then give
an authentication failure or does it not even find
the server?
etc.
|
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Mon Jan 10, 2005 4:50 am Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
"Sam Mapson" <mapson4@hotmail.com> wrote in message
news:I2iEd.2725$Ii4.1892@newsread3.news.pas.earthlink.net...
| Quote: | Did not have a WINS server. I will try enabling Netbios over IP when I
get into the office.
|
You pretty much cannot turn off NetBIOS
over IP on any production Windows network
no matter what the press releases say.
--
Herb Martin
| Quote: |
"Herb Martin" <news@LearnQuick.com> wrote in
news:uIikOSk9EHA.2568@TK2MSFTNGP10.phx.gbl:
"Sam Mapson" <mapson4@hotmail.com> wrote in message
news:Rg3Ed.2074$Ii4.561@newsread3.news.pas.earthlink.net...
Just upgraded from NT server to Server 2003. We have several remote
users accessing their office computers using PCAnywhere. We have a
Sonicwall Firewall and it forwards the appropriate remote to the host
via port forwarding. We are using the Sonicwalls DHCP server and it
is the main gateway. It worked well under NT Server.
Inorder to resolve slow login and directory browsing, I changed the
DNS settings on all of our XP computers to point to the 2003 server.
Now PCAnywhere does not work. Any ideas on how to make PCAnywhere
work?
That's not (nearly) enough information unless someone
just happens to have had your problem or hit on it with
a luck guess.
Generally: you have an Authnetication and/or a Name
resolution problem if this is all that changes unless
pcAnywhere has collapsed completely (it did on Win2000
upgrades in a previous version but that was obvious
because the servers wouldn't even boot.)
You changed DNS, and Win2003 domains depend on
DNS for not just name resolution but that also is a
prerequisite for authentication.
Did you (at the same time) change anything about NetBIOS
or WINS server? (Many people think they don't need NetBIOS
in Win2000+ but that is almost always wrong, and even
WINS server remains important if you have IP on more than
one subnet and Win2000+ domains require IP).
Also you say "does not work" rather than giving us
specific symptoms, and error messages, and telling
us what standard (simple) tests like ping, nslookup,
etc. if they apply.
Does the pcAnywhere work at all? Locally or from
SOME clients?
Does it seem to connect initially? And then give
an authentication failure or does it not even find
the server?
etc.
|
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Mon Jan 10, 2005 4:52 am Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
"Sam Mapson" <mapson4@hotmail.com> wrote in message
news:IdiEd.2795$pZ4.2503@newsread1.news.pas.earthlink.net...
| Quote: | Are there any settings in DNS would help solve the problem. It was
setup for only a forward lookup zone. It forwards to the DNS IP
addresses the ISP gave us. I am not too knowledgeable about DNS.
|
I can help you with DNS if that is part of the
problem or still giving you other trouble but
you had NT before and it was working, and
NT is likely to have been using NetBIOS
resolution and people forget that for Win2000+
when they upgrade frequently.
We first need to know WHY it is broken so I
am going back to read your long response --for
some silly reason I answered these backwards.
Actually I picked off the short ones first.
--
Herb Martin
| Quote: |
"Herb Martin" <news@LearnQuick.com> wrote in
news:uIikOSk9EHA.2568@TK2MSFTNGP10.phx.gbl:
"Sam Mapson" <mapson4@hotmail.com> wrote in message
news:Rg3Ed.2074$Ii4.561@newsread3.news.pas.earthlink.net...
Just upgraded from NT server to Server 2003. We have several remote
users accessing their office computers using PCAnywhere. We have a
Sonicwall Firewall and it forwards the appropriate remote to the host
via port forwarding. We are using the Sonicwalls DHCP server and it
is the main gateway. It worked well under NT Server.
Inorder to resolve slow login and directory browsing, I changed the
DNS settings on all of our XP computers to point to the 2003 server.
Now PCAnywhere does not work. Any ideas on how to make PCAnywhere
work?
That's not (nearly) enough information unless someone
just happens to have had your problem or hit on it with
a luck guess.
Generally: you have an Authnetication and/or a Name
resolution problem if this is all that changes unless
pcAnywhere has collapsed completely (it did on Win2000
upgrades in a previous version but that was obvious
because the servers wouldn't even boot.)
You changed DNS, and Win2003 domains depend on
DNS for not just name resolution but that also is a
prerequisite for authentication.
Did you (at the same time) change anything about NetBIOS
or WINS server? (Many people think they don't need NetBIOS
in Win2000+ but that is almost always wrong, and even
WINS server remains important if you have IP on more than
one subnet and Win2000+ domains require IP).
Also you say "does not work" rather than giving us
specific symptoms, and error messages, and telling
us what standard (simple) tests like ping, nslookup,
etc. if they apply.
Does the pcAnywhere work at all? Locally or from
SOME clients?
Does it seem to connect initially? And then give
an authentication failure or does it not even find
the server?
etc.
|
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Mon Jan 10, 2005 5:02 am Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
"Sam Mapson" <mapson4@hotmail.com> wrote in message
news:hThEd.2714$Ii4.177@newsread3.news.pas.earthlink.net...
| Quote: | 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).
|
| Quote: | 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).
|
| Quote: | 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.
| Quote: | 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.
| Quote: | 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.
| Quote: | 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.
| Quote: | 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.
| Quote: | 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.
| Quote: | 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. |
|
| Back to top |
|
|
Sam Mapson
Guest
|
| Posted:
Mon Jan 10, 2005 1:13 pm Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
Problem solved!!! I just came back from the office. It was something
very simple - the Windows XP firewall. I added the custom assigned
ports to the exclusion list - although PCAnywhere was in the list.
Thank you very much Herb Martin - if it wasn't for you, I would be still
looking for a fix in DNS. It threw me because the only thing that
changed was the DNS IP settings on the XP computers.
"Herb Martin" <news@LearnQuick.com> wrote in news:uMx6f7p9EHA.3756
@TK2MSFTNGP14.phx.gbl:
| Quote: | "Sam Mapson" <mapson4@hotmail.com> wrote in message
news:IdiEd.2795$pZ4.2503@newsread1.news.pas.earthlink.net...
Are there any settings in DNS would help solve the problem. It was
setup for only a forward lookup zone. It forwards to the DNS IP
addresses the ISP gave us. I am not too knowledgeable about DNS.
I can help you with DNS if that is part of the
problem or still giving you other trouble but
you had NT before and it was working, and
NT is likely to have been using NetBIOS
resolution and people forget that for Win2000+
when they upgrade frequently.
We first need to know WHY it is broken so I
am going back to read your long response --for
some silly reason I answered these backwards.
Actually I picked off the short ones first.
|
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Mon Jan 10, 2005 4:19 pm Post subject:
Re: Routing problem - PCAnywhere, Server2003 & DNS |
|
|
"Sam Mapson" <mapson4@hotmail.com> wrote in message
news:4WpEd.3116$Ii4.2926@newsread3.news.pas.earthlink.net...
| Quote: | Problem solved!!! I just came back from the office. It was something
very simple - the Windows XP firewall. I added the custom assigned
ports to the exclusion list - although PCAnywhere was in the list.
Thank you very much Herb Martin - if it wasn't for you, I would be still
|
You are welcome.
| Quote: | looking for a fix in DNS. It threw me because the only thing that
changed was the DNS IP settings on the XP computers.
|
Actually most problems are trivial to "fix" -- it is finding
them which is difficult sometimes.
The key when troubleshooting is to become (tediously)
explicit, simplify, and isolate the problem.
This method only works directly about 97% of the time,
but that is good enough to get you close, so you can work
on the other 3% which are complex and/or intermittant
problems that cannot be easily isolated, or which turn
out to be true bugs which cannot be fixed (directly) anyway. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in