A 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
The service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones). click here to download the app (for users in the US for now) and get all the help you need. Good luck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
This is an excerpt from a MS Technet page for error 53:
Resolutions:1) if it is domain environment, check your WINS; 2) if it is peer-to-peer workgroup, enable NetBIOS over TCP/IP; 3) make sure the machine is running; 4) make sure file and Printer Share enabled on remote computer; 5) make sure client for ms networks is enabled on local computer; 6) make sure you type the correct name. 7) Make sure no firewall running or any security setting.
Pay close attention to #s 4 and 5 - I suspect XP pro might not be open enough.
Does this mean anything to you
Remote Login Names and Passwords
During a remote login, the device prompts you for a login name and password. You
can display the login name when logged in to the device from a remote console by
using a device status command.
Logging in Remotely or Locally
Logging in to a local console is the same as logging in to a remote console except
that you must connect to the device by starting Telnet on your host system. To log
in remotely, begin at step 1. To log in locally, begin at step 3.
To log in from a remote console:
1. Connect to the device by starting Telnet on your host system. Your host system
is the system to which remote terminals are connected.
2. Supply the device?s name or Internet Protocol (IP) address.
To use device names, your network must have a name server. Issue either the
device name or the IP address as shown in the following example:
% telnet brandenburg
% telnet 126.96.36.199
At this point, it makes no difference whether you have logged in remotely or
3. If you are prompted, enter your login name and password.
It is possible that there is a login and no password. The password controls
access to the device. If a password has not been set, press the Enter key at
the Password: prompt. Logins are not set automatically. For security, you can set
up user names and passwords using the add user command in the CONFIG
process. For additional information, see the add user configuration command,
on 56. Remember to reload or restart to activate any changes.
Note: If you do not enter a login name and valid password within 1 minute of
the initial prompt, or if you enter an incorrect password three times in
succession, the device drops the Telnet connection.
4. Press the Enter key to display the asterisk (*) prompt.
You may have to press the Enter key more than once or press Ctrl-P to obtain
the * prompt.
Once at this level, you can begin to enter commands from the keyboard. Press
the Backspace key to delete the last character typed in on the command line.
Press the Delete key or Ctrl-U to delete the whole command line entry so that
you can reenter a command. See ?Command Completion? on page 20 and
?Command History? on page 23 for more information.
You can also use local Telnet commands on your Telnet client to close the
NAT traversal refers to the common problem in TCP/IP networking of establishing connections between hosts in private TCP/IP networks which use NAT devices
Client-based IPsec VPN connections often do not work when passing through a NAT device as the IKE and IPsec protocols were not designed to work through NAT. NAT Traversal is an add-on to the IKE and IPsec protocols that allows them to work when being NATed.
NAT traversal is only used if both endpoints support it. D-Link products that currently support NAT traversal include the DFL-200, DFL-700 and DFL-1100.
Note: The DFL-80 and DFL-300 do not support NAT traversal.