issue with seeing internal website
Hi, We have setup an internal ticketing site a few years ago on a pc.
we have always been able to access it remotely and internally using ticket.mydomain.com.
one of the users accessed it over the weekend remotely and can now not access the site internally using ticket.mydomain.com. but can see it by going \\ticketpc
I'd assumed this was a DNS issue. I have flushed DNS and cleared the internet temp files and cleared cookies/history.
We have a windows 2003 DNS server. is it worth me adding ticket.mydomain.com to point to 192.168.1.35 (internal IP)
If so, how do i do this. the ticket site is on a windows XP machine
we have always been able to access it remotely and internally using ticket.mydomain.com.
one of the users accessed it over the weekend remotely and can now not access the site internally using ticket.mydomain.com. but can see it by going \\ticketpc
I'd assumed this was a DNS issue. I have flushed DNS and cleared the internet temp files and cleared cookies/history.
We have a windows 2003 DNS server. is it worth me adding ticket.mydomain.com to point to 192.168.1.35 (internal IP)
If so, how do i do this. the ticket site is on a windows XP machine
ASKER
I get the external IP address as I should
if i ping the ticket.mydomain.com on this pc, I don't get a reply from the external IP.
but if i do it from any one else, I do get 4 replies from the external IP
if i ping the ticket.mydomain.com on this pc, I don't get a reply from the external IP.
but if i do it from any one else, I do get 4 replies from the external IP
ticket.mydomain.com > it's an internal website? With LAN IP? Put here the output of the command:
cmd > "nslookup ticket.mydomain.com"
Verify the "hosts" file (C:\Windows\System32\Drive
cmd > "nslookup ticket.mydomain.com"
Verify the "hosts" file (C:\Windows\System32\Drive
ASKER
it is an internal website, which we can also access externally.
on the laptops we have. we left it so that the shortcut was ticket.mydomain.com.
this has also always workjed internally. Until now on one laptop
on the laptops we have. we left it so that the shortcut was ticket.mydomain.com.
this has also always workjed internally. Until now on one laptop
ASKER
all i have is in the host file
127.0.0.1 localhost
127.0.0.1 localhost
Put here the output of the command:
cmd > "nslookup ticket.mydomain.com"
Verify if the dns server used is your internal DNS. If not, verify if the TPC/IP (of the network adapter) is not set to manually with an external DNS server or wrong server ip.
-smgoncalves
cmd > "nslookup ticket.mydomain.com"
Verify if the dns server used is your internal DNS. If not, verify if the TPC/IP (of the network adapter) is not set to manually with an external DNS server or wrong server ip.
-smgoncalves
ASKER
Server: e2007.domain.local
Address: 192.168.1.183
Non-authoritative answer:
Name: mail.mydomain.com
Address: external IP
192.168.1.183 is the internal DNS
Address: 192.168.1.183
Non-authoritative answer:
Name: mail.mydomain.com
Address: external IP
192.168.1.183 is the internal DNS
You are using and external DNS and not your internal DNS. Verify the TPC/IP (of the network adapter).
and show me the output of:
cmd > "ipconfig /all"
-smgoncalves
and show me the output of:
cmd > "ipconfig /all"
-smgoncalves
ASKER
Only dns entry is the internal
192.168.1.183
192.168.1.183
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
worked a treat, thank you
cmd > "nslookup ticket.mydomain.com"
Is it the name/ip correct?
-smgoncalves