General discussion
| Thread display: Collapse - |
All Comments
Back to IT Employment Forum
1 total post
(Page 1 of 1)
Start or search
Create a new discussion
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Related Discussions
-
16
-
4
-
7
-
0
-
19
website access inside company
I have a company website that was being hosted by a webhost company and I switched to another webhost company. From outside the company the website, is accessable, but inside the company I have to use the website IP address of to access the website.
When I go to it on the W2000 Server I get the following when a tracert is used:
Tracing route to www.ourwebsite.com, Old Webhosting IP Address, and it never finishes, I receive Request timed out and cannot access the website inside the company on this server, this is the AD server.
When I use the Win NT 4.0 and do a tracert on WWW.ourwebsite.COM, it gives the following message:
Tracing route to www.ourwebsite.com, New Webhosting IP Address, and it finishes the trace, I can also access the website inside the company on this server only.
Can you think of any reason why the W2000 Server cannot connect to the new WebHosting IP address or how to clear it out? This is important and internally I need it to access our company website.
I have gone to the W2000 server and ran the following:
nbtstat -RR
ipconfig /flushdns
Rebooted the W2000 Server
and still get the address of the old Webhosting IP.
Is there something else I'm not doing to flush this IP address?
Any help on this is appreciated, thanks
Note www.ourwebsite.com is not the actual website name!!!!!!!!!!
This conversation is currently closed to new comments.