..on the TCP network
We are getting tonnes of these appearing on our FMS server, and Im not sure if this may have something to do with problems the bursar is experiancing with FMS
It says to run nbtstat -n to see which name is in the conflict state but I run that and everything looks fine.
Also the message 'The IP address of the machine who sent the message is in the data' - so how do I work out what the Ip is from the data??
0000: 00 00 04 00 01 00 54 00 ......T.
0008: 00 00 00 00 df 10 00 c0 ....ß..À
0010: 01 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 02 12 14 ac ...¬
Is what is there.
I cant see how it can be a problem on our network as there is blatently not another machine with the same name. The server however is also connected via a second NIC to the LEA WAN, so they can remote in via netop
They are of course saying that the problem we are having with FMS (operations that normally take 20 secs are taking 3 mins+) is nothing to do with them and they have never seen it before
Work your way through all the possibilities listed in KB 315259.
http://support.microsoft.com/kb/315259
Well I got the IP address and its the WAN IP of the main Sims server
And of all the possibilities this is the only one that is relavent
"Conflicting Network Adapters in a Multihomed Computer"
But of course doesnt list any resolution.
Both servers have correct internal and external IP's, the same ones they have always had.
Also getting some weird errors on the same server
Some saying it is attempting to promote itself to the master browser but cannot, and the master browser is the Sims server.
Then also some messages from itself that it believes itself is the master browser but it isnt
I know I dont need the browser service on but Im wondering if these are indicating a bigger underlying problem?
There are currently 1 users browsing this thread. (0 members and 1 guests)