Re: Routing problem - PCAnywhere, Server2003 & DNS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Sam Mapson (mapson4_at_hotmail.com)
Date: 01/09/05 

Date: Sun, 09 Jan 2005 22:03:57 GMT

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:

> "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.
>
>

Relevant Pages

  • Re: No DC in Active Directory
    ... I still show no computers or DCs in AD Computers and Users on Srvr1 and they ... The primary DC points to itself as the DNS. ... The second server ... the first server now shows no DCs in the Active Directory ...
    (microsoft.public.windows.server.active_directory)
  • Re: Client computer internet connection problems
    ... subnet, Default Gateway, correct DNS entry/ies). ... his TCP/IP Configuration settings then he is not going to be able to join ... O*N*L*Y the internal DNS Server IP Address..... ... join the computers to my server domain. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharing a drive on my computer with others
    ... SBS 2003 needs to manage DNS and really likes to manage DHCP, ... You need to use the wizards on the SBS server to get it all working properly. ... I can't ping any of the computers within the domain. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Replacing Win2000 Domain controllers
    ... Normally you can rename a computer in the domain without any problem, maybe the account did not have the correct rights in AD. ... If you remove it give time for replication and also check that all entries from the DNS management console are deleted and also from the DNS zone properties under the Name server tabs, if it was a DNS server. ... I've tried renaming computers in the domain before and ...
    (microsoft.public.windows.server.migration)
  • Re: Error adding computers to domain
    ... > add Windows 2000 computers to a domain. ... > all because that function isn't necessary on that server. ... While not required by the server, the clients would certainly see a benefit. ... ever use an ISP's DNS server. ...
    (microsoft.public.win2000.advanced_server)