• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 385
  • Last Modified:

No internet connection on a server running Windows Server 2003

Experts,
This is a very bizare case i have. Basically i have a server which is running Windows server 2003 standard in a domain environment. This server itself is not a DNS or AD server it's just as member server of the domain. It hosts our bespoke applciation. For some reason the server has just stopped being able to contact the internet. The server is configured with 10.0.0.21 static IP DNS entries are correct and default gateway is correct. I cannot ping an IP address on the internet via IP or FQDN
We also have some remote software called Logmein and this is also saying the computer does not seem to be on the internet. We have uninstalled the Network cards and Windows reinstalled them.
Used winsock fix no joy. I thne told it to get a DHCP address and bingo internet started to work.
Changing it back to static and we lost the Internet again. Internal LAN is fine and the server is accessible via RDP. We also tried telling DHCP to always assign the IP 10.0.0.21 but we had problems with that to. The switches look fine and all other servers are fine. Dns has entries for this server in it;s forward lookup zone.

Any ideas would be greatly appreciated
0
flowit
Asked:
flowit
  • 5
  • 4
  • 2
  • +3
1 Solution
 
k_romychCommented:
have you tried reseting routing table (route /f )?
did you set correct default gateway?
0
 
k_romychCommented:
Also try running
  netsh winsock reset
  netsh int ip reset
and reboot the server
0
 
OP_ZaharinCommented:
the static IP adress you used might be duplicate/being used by other workstation in the network.
- reset back the server IP to DHCP and ping the static IP address (or Ping the static IP adderss on a different machine): Ping -a <IP address>
- if there is a reply definitely there is another workstation is using the same static IP address
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
AlanConsultantCommented:
Is there an IP conflict perhaps?

Go back to DHCP and allow it to assign whatever it likes to that server (presumably not 10.0.0.21?), then try pinging 10.0.0.21 and see if something answers?

Alan.

0
 
Glen KnightCommented:
Have you checked the firewall? There isn't anything blocking that specific address?

If there was an IP conflict then you wouldn't be able to use RDP.

0
 
AlanConsultantCommented:

Can you ping the gateway with the static IP set to 10.0.0.21?

If so, what is the next step outside the default gateway?  Is that a modem / router connected to your ISP, or is there another router?

If the latter, can you ping that too?

Keep going until you are pinging the most exterior device on your network.

If that works, can you ping your ISPs DNS Server (for example)?

Alan.
0
 
flowitAuthor Commented:
none of your suggestions work. there is not conflict
DHCP IP address 10.0.0.31 worked for internet but static 21 wont
route print screen shows 0.0.0.0. 0.0.0.0 10.10.10.10 (gateway)
i can ping inside interface of firewall/gateway
0
 
Glen KnightCommented:
Have you checked the firewall logs? Sounds like it's being blocked.
0
 
flowitAuthor Commented:
the firewall is off
how could it be blocking
0
 
Glen KnightCommented:
not your server firewall the network firewall.
0
 
ghemstromCommented:
If it works with dhcp but not with static address - are the static settings of your server the same as the ones you obtain from the dhcp server? Check that thoroughly!
0
 
flowitAuthor Commented:
yes they are identical could lmhosts or hosts files play apart when on a static IP
the hosts file was renamed to hosts.bak
0
 
flowitAuthor Commented:
not sure how the firewall could be blocking only this server
0
 
Glen KnightCommented:
it could quiter easily be blocking on that server if it has a rule to do so!
0
 
flowitAuthor Commented:
We previously used this server for exchange and it had a static NAT rule to block other htts traffic
when i looked on the cisco firewall logs i noticed this.
thanks
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 5
  • 4
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now