?
Solved

Issues with migrated SBS 03 Server not able to browse to web

Posted on 2011-03-02
4
Medium Priority
?
427 Views
Last Modified: 2012-05-11
HI there,

Recently I converted a Physical SBS 03 Server into a Virtual Machine now running on ESXi. It's on a completely different network at a completely different location.

The issue now is that its not resolving to the web. It receives connections. I can RDP into the server just fine.

I've attempted to replicate the network & DNS settings.

In the network card, I have:

IP: 10.1.0.24
Subnet: 255.255.255.0
Gateway: 10.1.0.1
DNS: 10.1.0.24, 208.67.220.220, 208.67.222.222

I have also made sure the DNS server is running. I've changed the A Record of this machine name and services running on the machine under DNS Server.
I've also reset and cleared all cache etc I could find. A Restart etc. No Luck.

It's worth noting that at one point I managed to browse to a few sites before that stopped working.

Any ideas, let me know
0
Comment
Question by:lemonville
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 9

Expert Comment

by:Aeriden
ID: 35022904
First, only use 10.1.0.24 for the DNS.  That is because AD relies on DNS and I am presuming 208.67.220.220 and 208.67.222.222 don't know anything about your SBS 2003 AD?

Okay...  From there...  How about your forwards on your DNS server on the SBS 2003 box?  Right-click on the DNS server via the DNS MMC and select Properties.
0
 
LVL 1

Author Comment

by:lemonville
ID: 35022934
Forward = 208.67.220.220

I'll adjust DNS. I did try the above, but it wasn't working.
0
 
LVL 9

Accepted Solution

by:
Aeriden earned 2000 total points
ID: 35022973
Are you sure the DNS 208.67.220.220 is operating and responding correctly?

Is the firewall enabled on the SBS 2003 box?  Any other firewalls along the way that could be blocking DNS (TCP/UDP 53)?  As a test, you can issue from a command line prompt "telnet 208.67.220.220 53" and see if it hangs (so a connection is made) rather than instant disconnect or rejection.
0
 
LVL 1

Author Closing Comment

by:lemonville
ID: 35023016
Bingo!

The hosting company the server is now wiht actually have a local DNS server. I entered that and it worked. I'll get them to open the firewall ports and we should be on our way.

Thanks a million!
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How many times a day do you open, acknowledge, or close an IT incident? What’s your process? Do you have a process depending on the incident, systems involved, and other factors? New Relic Alerts gives you options for how you interact with notifica…
OnPage enhanced its integration with ConnectWise Manage to offer incident responders more control over the ticket and Incident Resolution Lifecycle.
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…
Suggested Courses

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question