hours got trashed
in a server install, an ip scan was done, a free IP address got picked for a hyper-v domain controller / dns server, for some bizare reason that site's wireless access point tp-link is also using that IP, but it didn't showing up in the initial IP scan.
the server 2012 is installed on the network, it didn't complain about IP address duplicates /conflicts like its various previous version.
surprisingly that worked for a few weeks to my shocking brain. the problems after the server install are about 4 PCs having problems connecting with intranet which is hosted on the new DC.
for two w7 PCs, I removed panda anti-virus filter, then seemed better.
for another windows XP, and vista, the error still there, intranet broken, prompting for passwords. co-work indicated the PC tried to access a TP-LINK interface.
went down the wrong road, a number of trojans got cleaned, but the errors persists.
vaguely felt there is an IP address conflict , a co-work points out in the documentation that 192.168.1.15 was assigned to the TP-link access point. the solution is to disconnect the conflicting device for now.
again, when weird thing happens, check from the very basic things, check current documentaion to see what's the current IP lay-out. it payes to design an IP layout even if it's a small company.
the log on the server 2012 side is pretty vague, it only indicates some data transmission issue, something wrong with the network.
in a server install, an ip scan was done, a free IP address got picked for a hyper-v domain controller / dns server, for some bizare reason that site's wireless access point tp-link is also using that IP, but it didn't showing up in the initial IP scan.
the server 2012 is installed on the network, it didn't complain about IP address duplicates /conflicts like its various previous version.
surprisingly that worked for a few weeks to my shocking brain. the problems after the server install are about 4 PCs having problems connecting with intranet which is hosted on the new DC.
for two w7 PCs, I removed panda anti-virus filter, then seemed better.
for another windows XP, and vista, the error still there, intranet broken, prompting for passwords. co-work indicated the PC tried to access a TP-LINK interface.
went down the wrong road, a number of trojans got cleaned, but the errors persists.
vaguely felt there is an IP address conflict , a co-work points out in the documentation that 192.168.1.15 was assigned to the TP-link access point. the solution is to disconnect the conflicting device for now.
again, when weird thing happens, check from the very basic things, check current documentaion to see what's the current IP lay-out. it payes to design an IP layout even if it's a small company.
the log on the server 2012 side is pretty vague, it only indicates some data transmission issue, something wrong with the network.
No comments:
Post a Comment