UT300 R (Balck one should be 300 RA)

  • Thread starter Thread starter srrao
  • Start date Start date
  • Replies Replies 2
  • Views Views 2,205

srrao

Regular
Messages
174
Location
NA
I have been provided with UT 300 R CPE. When trying to access my sys from outside using current ip the UT 300R is taking over and asking for username and password for "Webadmin" and not "Viking". How to avoid this.How to find the net stats / synch rates?
 
Hello,
I dont use UT 300 R CPE but I used Hauwai and D-Link CPE.

Based on those there may be some ways to stop such:
1) From your CPE web interface, you can block port 80, so that Internet users can not access that port.
2) From your CPE web interface, you can allow port 80 and redirect it to your computer, this should be the case if you are running any webserver on your pc and want to access it from outside.
3) Change the cpe port to some nonstatndard port like 8181, Now your web admin will be accessible like http://192.168.1.1:8181 and Dont forget to block this port form CPE manager.

I hope any one from these will surely work on UT 300 R CPE
Regards
 
i am pasting this below info from microsoft site
link: http://support.microsoft.com/kb/842242

Identifying and opening ports
If your program still does not seem to work after you add the program to the list of exceptions, or if you cannot locate the program in step 4 of the previous section, you can open a port manually. Before you can add a port or ports manually, you have to identify the ports that are used by the program. A reliable method for identifying the ports that are used by the program is to contact the vendor. If you cannot do this, or if a list of ports that are used by the program is not available, you can use Netstat.exe to identify the ports that are used by the program.
Identify ports by using Netstat.exe
1. Start the program in question and try to use its network features. For a multimedia program, try to start an audio stream. For a Web server, start the service.
2. Click Start, click Run, type cmd in the Open box, and then click OK.
3. Obtain a list of all listening ports. To do this, type the following at a command prompt, and then press ENTER:
netstat –ano > netstat.txt
4. Obtain the process identifiers for the processes that are running. Type the following command at the command prompt, and then press ENTER:
tasklist > tasklist.txt
Note If the program in question is running as a service, add the /svc switch to list the services that are loaded in each process:
tasklist /svc > tasklist.txt
5. Open Tasklist.txt and locate the program that you are troubleshooting. Note the process identifier for the process.
6. Open Netstat.txt and note any entries that are associated with that process identifier. Also note the protocol that is used (TCP or UDP).
The number of ports that the process uses may affect how this issue is resolved: • If the process uses more than 1024 ports, the number of ports probably will not change.
• If the process uses less than 1024 ports, the program may be using a range of ports. Therefore, opening individual ports may not reliably resolve the issue.
 

Top