I am wondering if this is a DNS issue

  • Thread starter Thread starter Firebrwd
  • Start date Start date
F

Firebrwd

My company is setting up a new system called virtual
service - They are planning on selling cameras with built
in web server to clients so we can view the problem
rather then always haveing to travel for minor issues -
As we are trying to test the equiptment we have one
problem - From inside the company we can obviously type
in the address of the camera and the home page opens -
When we are trying from the outside(as in from home) we
cannot get to the page. My feeling is it is not the
router because we can ping the address of the camera - I
think it is a DNS redirection issue but I am not sure -
Can you tell if I am right and if so how would I setup
this redirection?
Thanks -

Windows 2000 server in case you were not sure -
 
In
Firebrwd said:
My company is setting up a new system called virtual
service - They are planning on selling cameras with built
in web server to clients so we can view the problem
rather then always haveing to travel for minor issues -
As we are trying to test the equiptment we have one
problem - From inside the company we can obviously type
in the address of the camera and the home page opens -
When we are trying from the outside(as in from home) we
cannot get to the page. My feeling is it is not the
router because we can ping the address of the camera - I
think it is a DNS redirection issue but I am not sure -
Can you tell if I am right and if so how would I setup
this redirection?
Thanks -

Windows 2000 server in case you were not sure -

DNS does not redirect that is a web server responsibility.
That being said, does the camera itself have a public IP address?
Or is it kind of VPNed in behind a router?
Is the camera on a standard http port? (80)
Your post kind of confused me because you say you can ping the address of
the camera. How can you ping the address of the camera and still not be able
to connect to it?
What address are you pinging? That won't make sense to me until you can
clarify this as to what you are pinging and trying to connect to. Because
you say you can connect to it from inside the company but not outside.
 
In
Kevin D. Goodknecht said:
In

DNS does not redirect that is a web server responsibility.
That being said, does the camera itself have a public IP address?
Or is it kind of VPNed in behind a router?
Is the camera on a standard http port? (80)
Your post kind of confused me because you say you can ping the
address of the camera. How can you ping the address of the camera and
still not be able to connect to it?
What address are you pinging? That won't make sense to me until you
can clarify this as to what you are pinging and trying to connect to.
Because you say you can connect to it from inside the company but
not outside.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================

Sounds like a port remap issue if the internal network is on a NAT. Need to
port remap 80 to the webserver from the NAT router. THen connect to the
external WAN IP of the router to connect in. How to do a port remap? Consult
the NAT router's documentation.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
To access the camera from outside, you will need to use it's public IP address. As stated in previous posts, this may be a NAT router. The router will need to
have a port mapping for port 80 that redirects to the internal camera on port 80. This isn't a DNS issue.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
Back
Top