ataylor Posted June 10, 2015 Posted June 10, 2015 (edited) Hi, I am Having an issue with one of our virtualised file servers,The server is refusing to connect to our proxy server (The Proxy server isn't responding) and thus can't access the internet, It is also it is refusing to pull updates from our internal AV server or use our AV server for remote administration. From the file server I am able to to ping the AV server, Proxy server and 8.8.8.8 I can even successfully RDP into my server at home. I am also unable to connect to any of our internal websites from this server. I have checked the network settings on our Hyper-V host and they are no different to other servers using identical settings. Its IP, DNS and default gateway are all correct. (I can successfully ping dns names) Clients are also successfully able to connect to the file server. I'm a bit stumped what might be causing this, the only other possibility is that It was caused by Windows updates that I did a couple of weeks ago? Have you heard of anything like this before? I also ran the same updates on our other file server (under a different host but they are both pretty much identical) Thanks in advance. Edited June 10, 2015 by ataylor
edutech4schools Posted June 10, 2015 Posted June 10, 2015 not near a server so not 100% sure of the name but is share this NIC with OS ticked or not in hyper-V network settings?
ataylor Posted June 10, 2015 Author Posted June 10, 2015 I have tried both un-ticking that and ticking that box - makes no difference "Allow management operating to share this network adapter". Does it matter if the Host is sharing the adapter or not? - - - Updated - - - Also, other VM's are using the same NIC and are working.
ITGuyWestMidlands Posted June 11, 2015 Posted June 11, 2015 (edited) Duplicate ip address? Correct subnet mask? Edited June 11, 2015 by ITGuyWestMidlands
ataylor Posted June 12, 2015 Author Posted June 12, 2015 Is the HyperV network adaptor setup as External? Yes Duplicate ip address? Correct subnet mask? No Duplicate and the Subnet is correct.
TheRobins Posted June 22, 2015 Posted June 22, 2015 I would look at DNS myself. Do you use IP to connect to the proxy server or a DNS entry Obviously try some internal DNS lookups on the affected server
ataylor Posted June 22, 2015 Author Posted June 22, 2015 Direct IP Access didn't work either. I gave up trying to figure it out and just nuked it instead. Faster to re-build it than to figure out why it is not working!
TheRobins Posted June 22, 2015 Posted June 22, 2015 Windows corruption as you mention probably an iffy update. Glad you sorted it
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now